IOS UCBs no longer download to IPhones

Hello,

We have been making IOS UCBs for our app for months now, and haven’t had any issues downloading & play the app on our phone. As of last week, however, we have been experiencing an issue where the app will no longer download.

The profile downloads just fine, you press the install button, it says it was a success and that the game will be downloading on the home screen, but it never appears. We have tested this on both an IOS 11 device with the latest IOS update, and an older IOS (7) with an older OS. Same issue on both.

I tried resetting device UDID to no avail.

Is there any solution to fixing this?

Cheers

Unity support said that the issue is related to new feature called ** Customizable Executable Name **
and having white spaces in the configuration name. I was not able to fix the issue by removing white spaces so I’m also waiting for other solution.

Same problem here as already mentioned in the other thread . I’d like to add that, in a desperate attempt, I also tried to rename the build target to “build” so UCB would basically generate the same ipa-filename as before, but that didn’t solve the problem either. For now we might resolve to ipa-file-download & iTunes which nobody is really happy with.

Hi folks,

We are aware of the issue as @Dasp mentioned above, and unfortunately, as @Grazer2 noted, changing the build target name (which should normally work) also does not change the build artifact name.

You can, however, create a new build target without blank spaces that will solve the issue as a workaround for now. If this doesn’t work for any reason, feel free to open a support ticket and we can change the build artifact name for you manually.

Thank you and apologies for any inconvenience.

1 Like

Have created a new build target called “DeviOS”. It’s still not installing using the UCB-share link. I have created the build-target by cloning the previous one.

Hi @Grazer2 , could you please open a Support Ticket (Cloud Build > Help and Support > File a Ticket) so I could take a closer look (definitely at this specific build target you just created) to see what might be different and to get it working for you?

Thank you,

Peter D
Unity Service Support

I was able to get it to work by creating a new build from scratch and not using spaces. I didn’t try cloning myself, but I know others who said that cloning and renaming didn’t work for them. So maybe it has to be a fresh build. I also used “build” as the name so that it would use “build.ipa” as the executable name. Not sure if that matters or if any no-space name would have worked.

@cabbyU , thank you! That’s correct, the clone takes the original build artifact name so it does need to be a fresh build target.

For everyone following this thread, the underlying issue does seem to be fixed now as per this thread.

Thank you for your patience.

Thank you guys, our builds work fine now.