I'm getting this email below everytime I try to upload my Mac app. Version 1.0 for this happ but I've submitted hundreds of updates/apps before with no issue. My CFBundleIdentifier = com.nuclearnova.mac.birdiegolf , any ideas ass to what could be wrong? I feel like I'm missing something silly here as this is so simple, but I waited a day and looked at it again and still can't figure it out. Also, this happens both before and after the WWDC system upgrades today
Dear developer,
We have discovered one or more issues with your recent delivery for "Birdie Golf". To process your delivery, the following issues must be corrected:
Invalid Bundle Identifier Format - The bundle identifier, as specified via the key CFBundleIdentifier in the bundle's Info.plist file, must consist only of characters that are uppercase or lowercase Roman letters (A-Z, a-z), the digits 0 through 9, dot ("."), or hyphen ("-"). For more information about bundle identifiers, the CFBundleIdentifier key, and the Info.plist file, see the Mac Developer Library at https://developer.apple.com/library/mac/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/TP40009249-102070-TPXREF105
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team
Finally solved the issue, here was the problem if anyone is interested
My app has a helper executable, which I precompile and presign beforehand. For some reason three years ago I included an info.plist in the helper and compiled like this
gcc -Wall -arch i386 -arch x86_64 -Os -framework AppKit -o NNRelaunch NNRelaunch.m -sectcreate __TEXT __info_plist Info.plist
<plist version="1.0">
<dict>
<key>CFBundleIdentifier</key>
<string>com.nuclearnova.mac.birdiegolf</string>
<key>CFBundleName</key>
<string>Birdie Golf</string>
</dict>
</plist>
After removing "-sectcreate __TEXT __info_plist Info.plist" everything uploads and processes fine.
Is this a bug or did/am I doing something wrong? As long as my app gets approved I guess I don't really care, strange how updates worked fine for 3 years on my last app doing this and suddenly stopped working.