Warning about a watch extension replaced by a WatchOS 2 app

App Store Distribution & Marketing App Review
once OP
Created Nov ’15
Replies 8
Boosts 0
Views 3.2k
Participants 9

When I did submit my application to iTunes Connect via Xcode 7.1 I received the WARNING ITMS-90573: "WatchKit 1.0. Your previous version used an extension for Apple Watch but your current version doesn't..."
I also received this email:


Dear developer,

We have discovered one or more issues with your recent delivery for "Once - One match per day". Your delivery was successful, but you may wish to correct the following issues in your next delivery: WatchKit 1.0 - Your previous version used an extension for Apple Watch but your current version doesn’t. Users who haven’t updated their Apple Watch to watchOS 2 or later may lose access to their Apple Watch extension. After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.

Regards,

The App Store team


My binary is still in the Waiting for Review state.
Is there anybody with some feedbacks about this new warning? Should I expect my binary to be rejected?

Replies  8
Boosts  0
Views  3.2k
Participants  9
M_Bischof OP
Nov ’15

Just got the same warning.

A few days ago I submitted an update of the very same app also without a watch extension. There was no error shown and the update is already on sale. I think its just a warning that some users might be unpleased. The warning is now shown although my most recent version on the app store has no watch extension either and only provides a watchOS 2 app.


I wouldn't be worried that my app might get rejected.

But hey, lets find out and wait 😀

0
RLKingSoftware OP
Nov ’15

once,

Knew this kind of thing would be coming. You can't remove device support arbitrarily.

Believe me, I understand the possible need to drop Watch support, I need to update

one of my apps that also supported the Watch but, with the loss of UIKit in WatchKit

2.0 my app no longer functions so, the Watch app has to go. Unfortunately, users

are going to be disappointed and Apple doesn't want that.


M_Bischof, it will likely make it to the app store this time. Such warnings are informational

usually and not necessarily deal breakers. BUT, next time, it will likely be rejected. Been

there myself.

0
tomkincaid OP
Nov ’15

I got this too. I don't want to have two targets to support OS 1 and 2. If people don't upgrade then I'm fine if they don't use the watch app. I hope this doesn't cause rejection though.

0
linguoisdead OP
Nov ’15

Got it too. But there's nothing I can do.

0
chuckc192000 OP
Nov ’15

You don't have to drop Watch OS 1 support. I recently updated an app with a Watch OS 1 extension and it runs fine on Watch OS 2.

0
testing.vc OP
Nov ’15

Same thing here - I drop the support for WatchOS1 and only support WatchOS2 as I would assume people will eventually upgrade to WatchOS2. I would hope Apple won't reject app because of this reason.

0
Brian A. OP
Nov ’15

This is a fallout of Apple tying Watch apps to iPhone apps, and it seems untenable in the long run. What happens when Apple inevitably creates WatchOS 3.0 next year? Will we be expected to ship 3 versions of our Watch apps?


I'm curious if anyone who has submitted with this warning has gotten their app approved yet.

0
acegreen1989 OP
Nov ’15

Decided to try my luck after receiving the warning.


I can confirm that the app has been APPROVED without any issues.

0
Warning about a watch extension replaced by a WatchOS 2 app
First post date Last post date
 
 
Q