I see a Detect Device message and when I click it it reloads the same page instead of downloading the profile.
It used to work with the Old UI.
Thanks,
Ash
I see a Detect Device message and when I click it it reloads the same page instead of downloading the profile.
It used to work with the Old UI.
Thanks,
Ash
We have replicated this and are urgently investigating.
As a workaround it looks like this still works if you use a share link. Just generate a share link and open the link in a new window and you should be able to get a working install.
Thanks Victor.
I tried the Share Link on the iPad using Safari. It shows a message Creating Share Link which disappears in a second and I don’t see the created shared link.
I did notice that the Build History screen had dimmed to light grey but could not see the link generated. Any other workarounds?
Thanks,
Ash
That’s pretty strange, it should show a popup which gives you the share link. That said you can still retrieve the share link by selecting the build you are interested in and looking for the link in the bottom right of the build details panel. I had a quick look at your projects and I think I was able to find the one you are working on - and there was a share link available on one of your recent iOS builds.
Thanks Victor. That worked. Got it from the build details panel.
Hi Victor,
The share link stopped working now and I am see the Detect Device message. Clicking on it reloads the page.
I checked my iOS settings → General → Profiles and the Unity profile which was installed earlier is not there. I am on iOS 13.4.1 on an iPad Pro 12.9 (2 Gen).
The previous Cloud build site was working fine yesterday morning before the redirect went into effect.
Thanks,
Ash
Share links definitely should still be working and I’ve seen reports from people saying that they’re still able to workaround the issue by using share links. We’re currently working on getting all the iOS links working properly and I’ve asked a QA to verify that share links are still working.
We have a fix for this now, currently working to test and release it ASAP.
Thanks Victor.
Will wait for the fix and then test.
The fix has been released, let me know if you’re still encountering issues.
Thanks Victor. Here is what’s happening now…
Refreshing the dashboard page, it still does not let me download the profile after clicking on Detect profile.
So, I cleared the Safari website data and it told be to go to settings to install the profile. Clicking on the Install Profile button and then on the install button again, opens up the dashboard page - this time without the detect device message. Clicking on the Install link for the build does NOT popup the iOS message box - Do you want to install this app.
I checked the profile and it seemed to be signed by *.cloud.unity.com and the new developer dashboard is dashboard.unity.com. Is it a certificate problem?
Regards,
Ash
Argh yeah I think you’re right, we’re looking at fixing that issue now.
Does installing from a share link work currently? I think that should be working now.
Yes Looks url to the share path is developer.cloud.unity.com which works.
Hi. Since today i have the same problem. Landing on the Detect Device Page. When pressing the button a message pops up: “We need to detect your iOS UDID before you can install apps”.
Pressing OK simply reloads the page. Do you can tell when this will be fixed?
@victorw still having this issue as well. Pressing the Detect Device just refreshes the page over and over. Definitely not fixed
I addressed this in another thread, so far it seems that everyone who has encountered this was able to resolve it by deleting their cookies (via Settings → Safari → Advanced → Website data → search & delete unity3d.com)
We were having the same Detect Device issue and now this worked for us too. Would be nice if this kind of thing is added to an error message on that page
We do have some work in progress to improve the functionality of device detection, unfortunately it’s a very complex system (thanks, Apple!). This breakage requiring a cookie deletion should never happen again though and was just an unfortunate issue introduced by switching over to the structure of the new dashboard.