I do not want to support and support watchOS 1, instead, I want to upgrade my existing watchOS 1 project to watchOS 2 without re-creating the interface. Repository etc.
Apple Doc is not very specific for solving this case:
watchOS 2 Transition Guide
This post below means that I have to keep two separate targets: watchOS 1 and watchOS 2 (redo the storyboard, etc.) respectively.
Xcode 7 supporting OS1 and OS2 clock
Tried to adjust watchOS 1 settings to follow watchOS 2 patterns, but ran into numerous errors like
"Deployment target equal to iOS 8.2 (was 9.0)",
Setting the deployment target in iOS 8.2 will allow the program to work in Watch watch watchOS 2, but it supports and supports watchOS 1 code functions instead of watchOS 2. If the new watchOS 2 target is created in Xcode 7, the deployment target for WatchKit Extension and WatchKit App is iOS 9.0 and the base SDK is watchOS 2 as opposed to the goal of deploying iOS 8.2 and the base watchOS 1 SDK in build settings.
The setup cannot support WKExtension and other new libraries in watchOS 2. Comment suggests creating a new watchOS 2. project to solve this problem.
Running environment: Xcode 7.0 beta, watchOS 2. Installed watchOS 2 on my Apple Watch and iOS 9 on my iPhone.
... Are these the expected patterns for this migration / migration / upgrade process?
Version 1 Update: Duplicate Storyboard and reusing files from watchOS 1 for the new watchOS 2 project is not difficult. You need to create at least one preliminary profile and application identifier for the watchOS 2 application, it works on the simulator. The application is installed correctly on the Apple Watch, but could not be downloaded using the debug device circuit in Xcode. The Watch application can be downloaded manually (without debug messages). This conclusion is consistent with the project WatchOS 2 code sample on Github.
watch-os watch-os-2 apple-watch xcode7-beta2
Kevin
source share