Updating an existing Watchkit app for WatchOS2

Question

Yesterday I saw this message and made me realize that I had a problem.

I created the WatchOS2 app after the WatchOS1 app in the store. When I tried to run the application, it forced me to update the host ID name , and now I have no idea if I can send the WatchOS2 application with a different bundle identifier. Does the store application support two different package identifiers for viewing applications?

EDIT

With watchOS1, I had the following packages:

|App | my.app.com | |Watch | my.app.com.watchkit | |Watch Extension | my.app.com.extension | 

And now, with watchOS2, I need to have the following:

 |App | my.app.com | |Watch | my.app.com.watchkit | |Watch Extension | my.app.com.watchkit.extension | <- The difference 

Can I imagine this difference?

Answer 1

From watchOS 2 Transition Guide :

The base binding id of all your targets should be identical to the bundle id of your iOS app. This behavior applies even if you have separate targets for both watchOS 1 and watchOS 2. The only differences between the bundle identifiers for any of the goals are the extensions that Xcode adds to identify the Watch and WatchKit applications. iOS does not install the Watch application whose package identifier does not match the package identifier of the iOS application.

You can also check the Lister app to see everything that Apple has implemented for Watch, including backward compatibility with watchOS 1.

Update for clarity: Here are the package identifiers for the watch application and the watch extension, respectively, from the Lister application:

watchOS 1:

• com.example.apple-samplecode.Lister.watchkitapp
• com.example.apple-samplecode.Lister.watchkitextension

watchOS 2:

• com.example.apple-samplecode.Lister.watchkitapp
• com.example.apple-samplecode.Lister.watchkitapp.watchkitextension

Conclusion: as far as you can see, your package identifier identifiers are absolutely correct and you can submit your application.