I have updated my app to 64-bit just fine. Everything is according to Apple's standards. I pushed the new version to the store and it got accepted on the 1st of July 2015.
Now, here is the problem, some customers are reporting that the app is not being updated automatically from the store. In other words, they still have the old app on their devices. And when you go to the store to manually update it, it installs a new version of the app next to the old one and they end up with 2 apps (same app) with the old and new version. Also some other customers are reporting that they are seeing mixed data when they lunch the new app (like data from the old one still shows up on the new one)
FYI, the bundle ID and the app ID are the same, nothing has changed except the app version and build number!
I have been publishing app for few years now and I have not seen such a problem. Any idea why this is happening?
Thanks in advance!
Related
I think this is not required, at my personal experience only new iOS specific features in my application will require a new release, but a personal client is asking me to confirm this.
With every new XCode release, do I have to rebuild and publish my application in order to make it available at the AppStore of new iOS Release?
If there is any official documentation that proves this will be appreciated!
You do not need to re-publish. Apps remain in the App Store until the developer pulls it (or very rarely, Apple pulls it due to policy violations).
There is likely not any documentation that explicitly states this, but consider a scenario where somebody gets the new iPhone 13 and opts to restore it from iCloud. Data is pulled from iCloud, but apps are restored by re-installing them from the App Store. If apps disappeared from the App Store because they haven't been re-compiled, then anybody who upgraded their phone would discover that a large number of their apps had disappeared.
Anecdotally, my company has apps in the App Store that haven't seen a new submission in over 2 years (since iOS 12). Those apps are still in the store.
You can test your iOS app using the new Xcode 13 and if you got some bug using the new iOS SDK, you can fix it and submit a new version to App Store using the new Xcode.
Its prudent to test your apps on each new OS (preferably before the public release) but in most cases no new release is necessary. Over time you may want to update your app to take advantage of new features or to better support new devices. No app will never last forever but you will likely be able to go some time before having to update.
I have a React Native app in the Apple App Store and recently released a new version. I'm getting reports from existing users who already had the previous version of the app installed that their new install is either partially upgrading or not upgrading at all, even though the app store is showing that the new version is installed.
In the app store they are seeing the new version number. They do the upgrade and then see the Open button, indicating that the upgrade is complete.
Some users are reporting that they see the old versions splash screen and then the new version of the app is there. Others are reporting that the old app hasn't changed at all even though, as I mentioned, the app store is showing the new one is installed. If the user deletes the app and installs it clean then it is always properly installing the new version.
Any idea why this may be happening? I would think that an upgrade scenario would be simply keeping the app data around while removing the old binary and replacing with the new binary.
I did switch the splash screen loading method from Launch Screen in the old version to Launch Images in the new one. And I have had many javascript changes and new native libraries installed. And my redux store has some different data structures. But I don't know why any of these things would result in a partial upgrade.
All,
We have an app in Appstore which is functional, Now we have build the app for new Version with complete new architecture, Design. Every thing is changed. Now we have given a update for out existing app in the Appstore. App went live and we updated the current app in Phone, We got the new version as expected.
But the problem starts here. In the Updated app we are not able to login and some other services are not working.
But if we download as new app (I mean deleting the old app and download it again). Every thing is working as expected, like login, and all the services.
We are not understanding what went wrong. What may the issue, Can any one help us.
I'm fairly new to app development, and I just recently put my first app in the App Store. I noticed some bugs after it was released, and when I tried to test it, it overwrote the version I had downloaded from the app store. I have the app connected to Game Center, so I want to avoid setting a high score while I am testing. Normally, in the test version I am logged out, and it has my ID saved for the App Store version, so it auto logs in for that version. However now that the new version has been overwritten, I can't login at all.
How do I keep them separate?
Change the bundle id like com.company.game to com.company.game2 or so
I've recently released a significant update to an iOS application, lets call the new version 2.0 and the previously uploaded 1.0. The v2.0 update became ready for sale and was released to the store on September 20, 2012 09:35 (~6 days ago). Since then I've been seeing some extremely strange behaviour when a user updates or installs my app for the first time. Several users (and myself) have downloaded the update only to see the previously uploaded v1.0 binary installed even though the app store meta data accurately reflects the new version. Uninstalling the app and re-downloading it then results in the correct v2.0 app being installed. This behaviour has been seen as recently as 12 hours ago. I'm also seeing several users complaining about crashes in the update which I'm positive only arise in the old version. Is it somehow possible that I've caused this issue to arise through project settings? I'm thinking not but I'd really like to get to the bottom of this as it's negatively impacting the apps ratings.
The following steps solved my problem.
In itunes connect click on the app icon.
Select 'Rights and Pricing'
Select 'Manage iCloud settings for this app'
Now check the versions that you don't want the users to download from iCloud.