Re: ITMS-90682: can't contain 16-bit or P3 assets if the app supports iOS 8 or earlier

I'm having the same issue? We need help over here 

I'm having the same issue.

For sanitys sake I took all the stickers + iMessage icons and put them in my project without the iMessage extension and the build validates fine so it seems like the issue is not with my raw assets atleast.

I am running into the same issue.

I solved it this way.

1. in the Project Navigator, go to your iMessage Extension and select all the app icons that are included in the Assets.xcassets file.
2. On the Utilities panel (the one on the right) change the Type of the asset to Icon. Just like in this pic:
   https://dl.dropboxusercontent.com/u/7870516/Screen%20Shot%202016-08-26%20at%204.30.43%20PM.png

In my case, it seems like I had problems with the extension icons.

Could we get a response from iTC engineers? I've already went through all images and all of them have 8-bit color depth or less and are using RGB/sRGB/Gray color space.

We are running into this as well. As far as I know everything is setup correctly in the Assets.xcassets, and I've even tried the setting to "Icon" suggestion.

We could use some anwsers, in the dark on this one!

I'm also having this issue after submitting a build with an iMessage extension. Would appreciate some answers as well.

The Icon setting didn't help with my build (xcode 8 beta 6). Still have targetting ios 9 as my only option.

Yes, an Apple response here would be great.

Having the same issue In xcode8 beta6, removed all sticker assests from app and still having the issue, would be great to get a response from Apple.

This appears to be a new issue/bug introduced in ITC in the last 10 days.  We submitted a beta app 10 days ago and all was fine, then today we get the error.

ERROR ITMS-90682: “Invalid Bundle. The asset catalog at “Payload/MYAPP.app/Watch/MYAPPWatchApp2.app/Assets.car’ can’t contain 16-bit or P3 assets if the app supports iOS 8 or earlier.

The assets that the error is complaining about are in our watchOS app.  These assets have been shipping in our app since watchOS 1 without issue.  Since they're in watchOS, it doesn't make any sense that restricting to iOS 9 or later would help.

BTW, my colleague found this tool for inspecting .car archives.

https://github.com/steventroughtonsmith/cartool

Time to submit a bug.

Steve

Some slight variation here:
I do have a Universal App building for iOS 7 but I do have a Today Widget that is only targeting iOS 9 and newer.

Here, I'm having the same issue with Xcode 8 beta6.

I suspect the problem is having a target building for iOS 9 and newer only, Xcode probably creates a resource for this target which is not compatible with iOS 8 and older and thus invalidates the whole bundle.

This started happening for me too (no extensions).

What's interesting is that it started when I selected iOS 8.3 (instead of 8.1) as my target in XCode 8 (Beta 6). It does indeed work switching back to 8.1.

I also tried 8.4 which has the same bug.

Chiming in that this has also happened to me when trying to test an iMessage extension.  I had to raise all deployment targets to iOS 9 in order for iTunes Connect to accept the build.

I/we also ran into this problem with Assets.car in our watch app.  We were perplexed because the images in the Asset Catalog haven't changed in more than a year, since we first built our watch OS 1.0 support.  It turns out we have several variants of our app and one of our apps was rejected while the others were accepted bythe  submission process.  I tried to find info on the Assets.car (BOM file) format.  I found some tools on GitHub that didn't really help but the one thing I noticed is that Assets.car in the reject app (watch app) was much larger than in the other variants of our app.  After a lot of poking around I found that for the rejected app, I had forgotten I had bump the minimum deployment target for our watch extension and our watch app up to watchOS 3.0 while in the other variants the minmum deployment target was watchOS 2.0.  I lowered the minimum deployment target back to watchOS 2.0 and our app submission was accepted.  I came to the conclusion that there is something in compatible with iOS 8, in compiled asset files whose miminum deployment target is  watch OS 3 and ultimately the problem I encountered was that watchOS 3 only apps are not compabile with iOS 8.  I guess if you want to deploy on iOS 8, you have to continue to support watchOS 2.