Xcode 8 Build Crash on iOS 9.2 and Below

Xcode 8 build crash on iOS 9.2 and below

See the accepted answer https://forums.developer.apple.com/thread/60919

You can save 16-bit assets as 8-bit ones with Preview.app

How to resolve "ERROR ITMS-90682: Invalid Bundle - The asset catalog
at 'Payload/XXXXX/Assets.car' can't contain 16-bit or P3 assets if the
app supports iOS 8 or earlier."

With Xcode 8 GM, this error will occur if you include 16-bit or P3
assets in an app submission targeting iOS releases earlier then iOS
9.3. If your app requires wide color functionality you must change your Deployment Target to iOS 9.3 or later. If your app does not
require wide color functionality and you wish to deploy it to older
iOS versions then you should replace all 16-bit or P3 assets with
8-bit sRGB assets. You can find 16-bit or P3 assets by running
“assetutil” on the asset catalog named in the error message from
iTunes Connect. The following steps outline the process:

1. Create an Inspectable .ipa file. In the Xcode Organizer (Xcode->Window->Organizer), select an archive to inspect, click
   “Export...", and choose "Export for Enterprise or Ad-Hoc Deployment".
   This will create a local copy of the .ipa file for your app.

2. Locate that .ipa file and change its the extension to .zip.

3. Expand the .zip file. This will produce a Payload folder containing your .app bundle.

4. Open a terminal and change the working directory to the top level of your .app bundle cd path/to/Payload/your.app

5. Use the find tool to locate Assets.car files in your .app bundle as shown below: find . -name 'Assets.car'

6. Use the assetutil tool to find any 16-bit or P3 assets, in each Assets.car your application has as shown below. : sudo xcrun --sdk iphoneos assetutil --info /path/to/a/Assets.car > /tmp/Assets.json

7. Examine the resulting /tmp/Assets.json and look for any contents containing “DisplayGamut": “P3” and its associated “Name". This will
   be the name of your imageset containing one or more 16-bit or P3
   assets.

8. Replace those assets with 8-bit / sRGB assets, then rebuild your app.

Update: If your Deployment Target is set to either 8.3 or 8.4 and you have an
asset catalog then you will receive this same error message, even if you do not
actually have 16-bit or P3 assets. In this case you will either need to lower
your Deployment Target to 8.2, or move it up to 9.x.

The app crashes some seconds after launching on iOS 9.2.1 via Testflight

It is very interesting bug. I use a image which is "Screen Shot 2017-05-12 at 03.03.24.png" on xcassets. So this image causes random crashes on iOS 9.2.1 and lower iOS 9

I should not have use image name which is contain point.
I lost my weekend :(

iOS app crashes at launch on Testflight for iOS 14 and below but not iOS 15+

We've ended up finding a solution for our issue:

• we're using the new Xcode 13.2RC (not ideal since it's not a final release yet, but no luck without it) - you'll need the latest MacOS to run it
• we've removed support for iOS 12 from our build (which thankfully we could afford to do since only a tiny fraction of our users were still using that version)
  These 2 things are both required on our end, trying to do one without the other would still show us the crashes.

I don't know if this is going to be the solution for everybody, so here are a couple of links we've used to get some ideas:

• https://developer.apple.com/forums/thread/696197
• https://developer.apple.com/forums/thread/696463 (that's our own Apple forum thread, but it has other ideas)

Also wanted to add to the things we've tested while debugging:

• From Xcode Organizer, distributing as Dev or Ad Hoc an archive that presents the issue on Testflight does NOT present the issue when installing directly to device, which reinforces the idea this is not a code/archive issue
• We've switched automated app signing to manual using all sorts of provisioning profiles (ad hoc, dev & distribution, using either iOS-only or Apple certificates), and the issue only presents itself when distributing to Testflight/Store using the distribution profiles

At the end of the day, it does look like an Apple issue and we would expect to see a fix soon - especially since more and more people have been faced with a similar problem.

---

Related Topics