The Apple App Store rejected my app for an error that I'm having trouble reproducing (a button was unresponsive). I'm updating an existing app, and their suggestion to reproduce the issue is "For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue".
How do you install the app as an update to an existing version from Xcode? Is there a way to do this through ITunes or ITunes Conect?
Delete any version of the app from your device then install the current version from the App Store just like any user would.
Then use Xcode to install your development build of your update. This will overwrite the App Store version in a matter very similar to a user performing a normal update of an app. Then figure out why your updated app isn't working in this situation.
Related
Some background of the issue:
I have a Xcode project named A. It has a bundle ID com.abc.tung. It was on AppStore already and had few app version updates with no issues.
Later we decided to re-write the app and create a new project in Xcode named B. We also gave it the same bundle ID com.abc.tung. We uploaded a new build to AppStore Connect, everything was fine, it went to correct app in the AppStore Connect. Then we released it to AppStore.
The problem:
Some of the users reported an issue that even after the update to the newest version (the version that came from project B), it would still open them an old app with old functionality.
Please help me to understand how is it possible? Or even if you had similar issues, please also comment since it might also be some issues with AppStore?
Since bundle ID hasn't changed, it might be a build version question.
Need to find out what app build version was submitted to AppStore as B, and what build version was installed on the device.
The version on iOS is the release version (like 1.2.3) + a build number (can be just a single number like 4), so the full build version looks like 1.2.3(4).
It is a good idea to display the full version inside the app UI to make it easier for the end users to report it to you.
My testers have problem with an app I had uploaded to Fabric Beta. During normal testing they uninstall already installed app from their devices and they download new version from Fabric. In that case everything works fine. App will download and launch properly.
Problems begins when they want to test situation when future app's users update my app from AppStore. My testers want to check if updated app will not crash.
Test case is easy:
List item
Download app from AppStore.
Launch it.
Download new version from Fabric (new version should override old)
Launch it.
App should not crash.
Problem appears in (4), Fabric shows error "download problem detected". (Note that everything works if there is no old app on device.).
Fabric has problems with overriding apps?
Fabric (1.7.7)
iOS 11
iPhone 6s Plus
PS. This test is important. Crash will appears when I change database model without migration for example.
Paul from Fabric here. Did you uninstall the App Store version of your app first? Since iOS 9, Apple changed its policy to prevent apps from being installed over the existing App Store version by 3rd parties, so you need to delete the original app before installing the Beta version. For more information, see our docs here: https://docs.fabric.io/apple/beta/tester-experience.html.
And the other reason could be if any other app is installing or updating parallelly, Fabric will not be able to install. Just faced the issue :)
We integrated crashlytics in on of our apps and are using fabric beta to distribute the app to testers.
On iOS I remember that there was in the past an alert on startup if somebody installed an old version of an app. Currently this alert does not appear anymore.
Is this feature still available? I couldn't see any documentation about it.
Mike from Fabric here and yes the functionality still exists. The check for a new version of your app happens every two hours. If you update and install a new version of the app before the check completes, then there won't be an update notification. Also, as mentioned here if you've explicitly installed an older version of the app from the Beta app that shows older versions, we won't prompt for an update. The most common cause of this though is updating your app and then installing it right away as you know the build finished.
I currently have my app on the AppStore, and current version is 1.4.
The last version was 1.3, and when users are updating from 1.3 -> 1.4 they have a crash when they use it, however I notice that if they uninstalled then reinstall it from scratch the bug disappear.
Is there anyway to simulate this behavior ?
I already try to checkout the 1.3 version, install it from Xcode on my device then update my App to 1.4 but I was not able to reproduce the crash.
Do you know any way to simulate the update of my app ?
Also, if I publish the 1.5 version on testFlight and then update my app from 1.4 Appstore to 1.5 testFlight, is my app deleted then reinstall or does it update it like it does when I did 1.3 Appstore -> 1.4 Appstore ?
Thanks for your help.
To handle this situation, first check for Sqlite and Coredata changes. If you have changed or altered any tables then you need to provide data migration.
In your case where you have not used it, check for crashlogs from iTunes portal. Symbolication of Crashlog will explain the crash in much better way.
To simulate the same, install the application of version 1.3 from store. Now sign the version 1.4 with distribution certificate and ad-hoc profile. Load it on test flight. Install this new version to upgrade from 1.3 to 1.4. This will create the same steps and you will be able to re-produce the issue.
My app has been live in the app store for a while. It saves data locally using NSUserDefaults. Some of the saved data needs to be automatically updated when users install the app update I'm working on.
To test, I install the old app, do a few things to save the data locally, then install the updated app over the old app, and make sure the data updates correctly. This has worked on devices running iOS 7.
I'm having trouble installing the updated app over the old app on a device or simuator running iOS 6. I've received a few different error messages, looked them up, and didn't really find any answers that worked.
Will users running iOS 6 have trouble installing the updated app on their devices?
I'm wondering if the issue has something to do with Xcode 5.1 debug builds. Maybe the issue goes away when users install a release build distributed by Apple.
Edit: I tried the advice in this answer and nothing seemed to work.