I've uploaded an app that got approved with an apple watch version. But in the latest version, I want to upload it without the apple watch version. Does anyone have any information on this?
V1 = iOS + Watchkit
V2 = iOS only
Does anyone know if Apple would allow this? I've tried contacting them, no response yet.
iTunes Connect does not allow uploading an updated version of an app when the update runs on fewer devices than the version of the app currently in the App Store. This is by design.
An update to an app must work for every customer who has already
purchased the app, and is running a current version of iOS.
Developers who wish to issue updates, but remove device support, have three choices:
Fix their app so that it can work on the devices they originally set out to support.
Target a newer version of iOS that requires a newer device.
Remove their app from the store, and upload the new app with a different bundle ID.
↳ https://developer.apple.com/library/ios/qa/qa1623/_index.html
Related
Is it possible to release the iOS app as an open beta in App Store?
Use case: anyone can download the app through the Apps Store without having any registration ( same as play store beta release)
Unfortunately your question is self-contradictory in the context of the App Store.
An app can either be released to the App Store or it can be in test/beta but it can't be both.
You can provide open beta access via a TestFlight link, but you need to find your own way of sharing this link (via your web site, for example).
Only fully functional apps will be approved for App Store release to ensure that users have a good experience with App Store apps. Any mention of "beta" or "test" will result in rejection.
The app is in the App Store. The phone companion app installs on the phone just fine, but for some users it (randomly) fails to appear/install on the watch. The app does not show up in the "My Watch" listing in the iPhone Watch app either.
I saw a variety of advice sites saying this can be resolved by doing things like resetting / re-pairing the watch. Also, the app has always been approved pretty swiftly when submitting to the App Store.
So my question is: can it be something code/setup related that can be fixed at the dev level? Or is this just a pesky Apple bug?
Most users are on latest iOS/watchOS versions (11.4/4.3.1)
OK, so problem was a mismatch between OS version on the device and the target version for the watch extension in XCode. If the target version is greater then the watchOS version on Apple Watch, the app will not show up in the Watch app listing and will not install, when auto-install is on. Unfortunately, all this will happen silently, with no warning or cue in the UI.
I have an existing project. I also have a basic version of the app approved for beta testing.
How can I install this "TestFlight" beta version as a separate app to my device? So that I still have the version that I'm developing?
I read through some articles, they're saying you need to have different App ID's. But I'm not sure if that's what I need (could be, I don't know)
Example article: nilsou.com - How to have two versions of the same app on your device
There, I have to create a new APP ID for the beta version (though in my case I think I have to add 2 ID's, one for XCode versions and one for beta versions).
But does that mean I have to create a new app inside of iTunes Connect?
I thought iTunes Connect works with these APP IDs. What if I now have multiple APP ID's for my app?
Thanks in advance!
I have my application in apple app store supporting, iPhone,iPad and iPod (Universal), Now I want to have my app compatible with only iPhone, How to achieve that.(In xcode device family I can check only iPhone and sumbit app sotre, will this make my app only supporting iphone ) Please help
It is not possible with the original Bundle ID.
Citing from the doc below:
https://developer.apple.com/library/content/qa/qa1623/_index.html
Bundles must continue to support any devices previously supported.
The only option for you is to create a new bundle ID and submit your app with it.
Removing your app from the store, and uploading the update with a
different bundle ID, will allow you to narrow the range of devices
your update supports. However the update will be listed on the store
as a separate app.
Trivial question I know, but I need to figure out this before I actually try it on iTunes Connect.
I have an application on the App Store, I would like that next version of the app is only available to users of iOS7 or greater.
I wonder if simply updating my app info.plist to support > iOS7 is enough to leave existing users running iOS6 with the latest version I released (1.9) before changing info.plist, and instead have iOS7 users prompted (or automatically updated) to the new 2.0 iOS7-only version?
Or maybe there is something else I have to specify under iTunes Connect?
I can't see anything actually there...
Yes, this is how it works. If you update your app's Deployment Target to iOS 7 then existing iOS 6 users will not be told of an update (and won't be able to update). iOS 7 users will be able to update.