Build and Run - builds, but not running

Hi,

Everytime I hit "build and run" in Unity for iOS, it's building and opening Xcode (in which I had previously selected my build device) but it's simply not doing the "Run" part of "build and run".

this is really annoying as I have to wait for builds to finish in Xcode, then hit play in Xcode and wait again

iteration time extremely slow

please help! Anybody know how I can get this working again?

 

Build and run support has been super spotty over the years, I treat it as if it doesn't exist these days. I understand this isn't the answer you are looking for.

 

Unity 2020.2.1f1 (but it's happening in any Unity version I believe, it seems that updating the OS to Catalina is when it started for me)
Xcode 12.4 (but was happening with previous versions of Xcode as well)
only one version of Xcode installed and yes It is detected by unity

I have no idea what else could be causing this

 

Is there any news on this? I was so desperate to get this working I reinstalled osx from scratch, no luck. Somebody help!

 

In the meantime, you can certainly just Build, then open in Xcode and deploy. Granted not the best solution, but will allow you to build and test your game. This is how I develop for iOS personally.

 

Wow most unhelpful reply of the year award.

I am already doing this! Do you think if I was willing to reinstall my OS to try to fix this, that I was happy with that as a solution? As a Unity employee, why would you have a feature in Unity that you are simply willing to put up with not working?

The issue is that when I hit Build and Run, it should do both those things, but right now, it only does one of them, Build. It then opens Xcode, but it doesn’t run.

The reason this is soul crushing, is that it wastes a ton of time. I have to stare at the screen for a few minutes while Unity builds, wait for it, then open that in Xcode, select the device, press play in there, wait, and then finally it’s on my phone (I make AR apps so testing on the phone is often irreplaceable, and yes I use the AR Foundation Remote plugin but it doesn’t cover all test cases, nothing is as good as a build on the real device for certain tests/tasks)

This little ritual can cost far more than the build time, waiting etc... what often happens is I’ll try to start doing something else during the first step, read documentation or code, and then got lost in that, and forget what I was even building the phone version for. Repeat this 20 or 50 times a day and it results in incredible inefficiency. It feels like a miracle when I finally get a build on the phone and remember what I was testing.

Android builds pretty much always work perfectly with Build and Run (I realize that it’s easier because they don’t have to go through Xcode, but still, build and run used to work fine on iOS, my feeling is that the latest MacOS probably messed it up with all its permissions needing)

Is there no way to debug Build and Run? Can I somehow see under the hood when Unity has its little blue bar up? Can you have an engineer at Unity actually try to fix this?

 

Is there any movement on this?!!

 

I believe you missed or misunderstood my comment "In the meantime..."

 

I feel your pain.
I ran into the same issue with my android build. At first, it built and ran, then it didn't then it did and so on.

I looked at the Android device and saw it only had about 700 MB of storage space available.

I removed the 3.6 gig Go pro app to free up some space and now it is building and running okay.

I really hope your issue was/is this easy.