0

Symptoms: after successful upload, the build is made unavailable in Itunes Connect, and an email is sent with the message in title.

Similar errors: ITMS-90542, but this is different in that no ITMS error is specified. Also, the key mentioned has the correct value, so that there is nothing to fix.

Result: an app that uploaded fine before Sep 22 can no longer be updated.

What have you tried: Up-/downgrading XCode and Application Loader, modified the mentioned key, uploaded many versions of a simple test application to pinpoint the cause.

Henrik Erlandsson
  • 3,797
  • 5
  • 43
  • 63

1 Answers1

0

Cause: one or both of CFBundleExecutable and CFBundleName keys contain a correctly encoded character 'å'. Likely, other correctly encoded non-ASCII characters cause the same misleading message.

Solution: Set one or both of the keys to contain only ASCII characters, until the problem is addressed by Apple. The CFBundleDisplayName key is handled correctly, so that you can keep your app's original display name.

Discussion: The new Itunes Connect processing module's parser breaks on non-ASCII characters in one or both of these keys, leading it to reject updates to a validated and previously approved app with identical info.plist content, and e-mail an incorrect message stating that the CFBundleSupportedPlatforms key is in error, when it is not. It may be productive to suspect a similar cause for other rejections/e-mails when the ITMS error number is not specified, rather than spend time trouble-shooting the cited error.

Henrik Erlandsson
  • 3,797
  • 5
  • 43
  • 63
  • It's interesting to see my thorough investigation rewarded with downvotes with no comment from users who did not do this work. This was the case, and I posted the results to help others encountering the broken parser. Q&A style doesn't work, does it. – Henrik Erlandsson Apr 13 '17 at 19:53
  • Forgot to add: And no answers. I'm quite prepared to have a Q&A session end with my answer being incorrect and me selecting the correct one. This site is about correct answers. – Henrik Erlandsson Apr 13 '17 at 20:02
  • 1
    Thanks for that, it saved my day! I was scratching my head why I'm getting this mysterious error for no reason. Looks like it's a bug in air sdk. – Makalele Aug 23 '17 at 08:43
  • Yes, this post was just documenting it, using the Q&A style in FAQ. Glad it helped you! – Henrik Erlandsson Nov 01 '17 at 19:25