I don't want to keep and support watchOS 1, instead, I want to upgrade my existing watchOS 1 project to watchOS 2 without recreating an Interface.Storyboard and etc.
Apple Doc isn't very specific to resolve this case:
This post below implies I should keep two separate targets, watchOS 1 and watchOS 2 (redo the storyboard and etc), respectively.
Xcode 7 supporting watch OS1 and OS2
Tried to adjusting watchOS 1 build settings to follow the patterns of watchOS 2, but encountered numerous errors, such as
"Deployment target equal to iOS 8.2 (was 9.0)",
Setting the deployment target to iOS 8.2 will enable the program to run on the Watch running watchOS 2, but it keeps and supports the code features of watchOS 1 instead watchOS 2. If a brand new watchOS 2 target created in Xcode 7, the deployment target for the WatchKit Extension and WatchKit App is iOS 9.0 and the base SDK is watchOS 2 as oppose to deployment target iOS 8.2 and base SDK watchOS 1 in the build settings.
The setup can't support WKExtension and other new libraries in watchOS 2. Commentor suggests to create a new watchOS 2 project to resolve this.
Running Environment: Xcode 7.0 beta, watchOS 2. Installed watchOS 2 on my Apple Watch and iOS 9 on my iPhone.
... Is this the expected patterns for this migration/transition/upgrade process?
Version 1 Update: Duplicate Storyboard and reuse the files from watchOS 1 for a new watchOS 2 project isn't hard. You need to create at least one provisional profile and App ID for the watchOS 2 App, works on the simulator. The app is installed properly on the Apple Watch, but failed to boot up by running the debug device scheme in Xcode. The Watch App can be booted up manually (without debugging messages). This finding is consistent with Sample Code watchOS 2 project on Github.