My mobile game unexpectedly quits on load. Happens on a every older iOS device I can find, but not on the latest generation. Breaks on iPhone 7 plus, 6S and some version of the iPad Mini.
Works fine on XS Max and 2018 iPad Pro. All of the devices were tested on an earlier version of iOS 12 and then on 12.2.
I don’t have any ambient sounds in the game, but it seems to be asserting on that. If I run the same console filter on the working devices I get no error output, period.
I am now fairly certain that this is the cause of the stoppage:
error 17:28:19.357965 +1200 PoppyAndBuddy419 Execution of the command buffer was aborted due to an error during execution. <private>
I have undone as many changes since the last working build as I can think of. Does anyone know what might be causing it, or how to debug it?
I’m having a problem with debugging too. When I try to build in XCode a lot of settings aren’t set up properly. I did eventually get it building but it says that the application name is invalid and must be set, but it IS set up. I’m unable to manually or automatically select a provisioning profile for iOS either, the project thinks its for making a MacOS app. Any help in getting the debugger working with a running mobile app, or even a simulator, would be appreciated.
This is the build error:
These are the build settings:
And here is the General tab showing MacOS as the only deployment target:
FWIW, if you’re using git for version control, you can use “git bisect” to go backwards through the history to find what change broke it. might be incredibly time consuming, considering you’ll have to rebuild for each step but it is a good way to figure out when something broke, if you don’t have a faster way to do it.
and if you are making large changes in your repo, or not using version control, well, commit smaller changes, and use version control if you’re not.
I am using Git, that was going to be my next step. Obviously before that it’s worth trying to solve some other problems along the way.
I had a closer look at the console output and it seems like Metal is failing on older devices. This has never happened in the past, so perhaps it’s due to a tool update somewhere along the way. I have confirmed that the old version still works fine.