The new bundle ID rules enforced by the iTunes Connect validator appear to make it impossible to submit an app with both original WatchKit and watchOS 2 extensions...
I just attempted to upload an app to iTunes Connect for internal testing, but it was rejected with the following message:
Error ITMS-90347: "Bad bundle identifier. The bundle identifier 'com.abc.myapp.watchkitapp.watchkitextension' of the application extension MyApp.app/Plugins/MyApp WatchKit Extension' should start with the application's bunle identifier 'com.abc.myapp' and not contain more than one period "." after the application's bundle ID."
The app contains both a watchOS 2 extension and an original WatchKit extension. The bad bundle identifier is reported only for he original WatchKit extension. The bundle identifiers are:
Main app: com.abc.myapp
WatchKit app (original and watchOS 2): com.abc.myapp.watchkitapp
WatchKit extension (original and watchOS 2): com.abc.myapp.watchkitapp.watchkitextension
This was working a week ago. My understanding is that both WatchKit extensions need to share the same bundle ID. However, the extra period in this bundle ID for the original WatchKit app seems to run afoul of the new bundle ID rule. Can anyone tell what bundle identifiers I should be using now? Are the current rules in fact contradictory?
—Chris