Both watchOS 1 and watchOS 2 in the same iOS app bundle

has anyone tried to have both watchOS 1 and watchOS 2 in the same iOS app bundle? How easy / difficult is it? what are the steps to follow ?

I did it without any difficulty. I simply added a OS2 target to my existing OS1 watch app.


However, trying to run anything on the watch using OS2 is difficult. Even a simple OS2 only app will only run 5% of the time.


Use the simulator until Apple fixes the problem.

Yeah I'm seeing running OS2 is difficult right now. Hopefully still can get some answers to get a clear picture in my mind.


So if we need to support 1.0, 1.0.1 and 2.0 for some time, there will be the below FOUR targets.

1. I'm assuming that when the user installs the App via the Appstore, then the appropriate target will get installed on his device?

2. Distribution will now mean having the below number of bundle ids

Target ecosystem will look like below:

1. The iPhone app Target = iPhone App Bundle Id


For prior verisons of Watch

2. Watch extension Target = extension's bundle id as per the parent iPhone App Bundle Id

3. Watch App Target that works for 1.0, 1.0.1 = Watch App's bundle id as per the parent iPhone App Bundle Id


For 2.0

4. Watch App Target for 2.0 = Assuming that the bundle Id for this will be based on the parent iPhone App Bundle Id but will follow different naming conventions and will need to be created ?

how exactly do you get the sdk for watch 1.x to be an optoon? I only have Latest watchos 2.0 and watchos 2.0 and there is nothing in my downloads for other sdks...

I need to build test apps to give to testers runing iOS 8.3 and watch 1.x

I have tried for days and never been successful. I can only guess that once the bugs are worked out, we'll get WK1.x when we add a WatchKit 1.x extension and app. Perhaps manually copy it?


I cannot get WK2.0 to respond to menu presses... tried several times (clean projects, re-install Xcode) and no such luck. There are so few posts here that I'm reluctant to file a defect, since no one else talks about it. Is anyone actually using Xcode 7 beta 2 and have 1.0 and 2.0 watch targets that work (for some reasonable definition of work)? Just wondering...

Haven't heard anything for a while; just wondering if anyone had success with Xcode 7 (b2, b3) and having WatchKit 1.x being an option for the SDK for 1.x targets?

Have an existing Watchkit 1.x app and added 2.0 targets as mentioned by others. To use simulator of b3, we set project deployment target to 9.0, app deplyoment target to 7.0. Don't see a way to change deployment targets for 1.x watch app and extension, so guessing they stay as they were (8.2). Fo Watch 2, don't see where to specify deployment target either, so guessing since they are 'new' they will inherit deployment target from overall project (9.0). This allows us to build/run in the Simulators to test new Watch 2 targets.

Since we are aiming to deploy one app to the store (not one for each ios version), we have Base SDK set as follows:

Main app, 1.x watch app and extension set to Latest IOS (IOS9). 2 watch app and extension set to Latest Watch OS (watch OS2).

We have not tried to build/run for earlier versions (1.x) using this beta. Really using this setup to test watch 2 but with all code/targets together.

To target watchOS 1.x you have to set the target architecture to iOS since the extension will be running on the iPhone.

Both watchOS 1 and watchOS 2 in the same iOS app bundle
 
 
Q