I am using Flutter to release the Android app. I have some updates and I am trying to release the one. However, there is an error saying that You can't rollout this release because it doesn't allow any existing users to upgrade to the newly added app bundles. I am quite lost what I have to do in this case. Play Console doesn't explicitly say anything about it.
What have I done wrong, and how can I fix this error?
The version code for the app bundle that you're uploading is probably lower (or lesser) than the current app bundle on your play store. Check the version code of the app bundle on play store and increase it. Than try again to rollout with higher version code
Related
I'm trying to create interval test for my flutter app.
But Google Console is not publishes the new version of the app for testers.
I'm NOT publishing the app for the first time.
I have a previous version of the app that was approved.
However this is my first test for the app.
I strictly followed the instructions provided by Google.
What I did:
made a new release that I want to test
created internal test
added list of internal testers (all of them are approved now).
published the new version to internal test
copied the link and tried to get the test version of the app as an internal tester.
However I've downloaded the old version of the app.
I've also tried to create alpha and beta testing after that and provided them with new version.
But still got this problem.
What's more, I did some extra step to solve this problem:
cleaned Play Market cache on the device
downloaded another simulator to test the app
changed the version of the app and downloaded it again
deleted and added again tester list in Google play console
Screenshots:
https://github.com/asg1997/qu/blob/main/Screenshot_1639590890.png
https://github.com/asg1997/qu/blob/main/Screenshot_1639591139.png,
https://github.com/asg1997/qu/blob/main/Screenshot_1639591150.png,
https://github.com/asg1997/qu/blob/main/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202021-12-15%20%D0%B2%2020.53.20.png,
https://github.com/asg1997/qu/blob/main/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202021-12-15%20%D0%B2%2020.54.18.png
I have released 4.4.2 -v ,4.5.0-v and 4.5.1-v apk versions
I want to change the app signature ,while submitting new version I am getting error like - The keystore used by your App is inconsistent with the version on the shelf please refer the rule 8.6 of "App Gallery Review Guidelines"
How to submit the apk with different app signature?
I would like to remove 4.5.0 too.
Once a signature key is generated in AppGallery Connect or uploaded by you, it cannot be modified.
For details,check the following documents:
https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agc-appsigning-introduction-0000001051379577
Yes. For this You need to remove the application from App Gallery Connect, then after only it is possible to delete the application.
After the application is submitted successfully for removing, the app status changes to Pending removal. Huawei operations personnel will handle your application in 1 to 2 working days.
Note: Removing an app will not release the package name used by the app. A package name can be released only after you delete the app.
For details, check the following documents:
Remove the app: https://developer.huawei.com/consumer/en/doc/distribution/app/agc-remove_app
Delete the app: https://developer.huawei.com/consumer/en/doc/distribution/app/agc-delete_app
Note: For released app, changing signature is not recommended.
I'm testing a Trigger.IO app built with Forge v1.4 on an iPod running iOS 6. I've been installing the .ipa through a distribution provision profile.
Occasionally, after installing an updated version, the app would launch but not run correctly. I traced this behaviour to the window.forge being absent, presumably due to a bad initialization. I would then make sure to kill the app process before installing updates and my recollection is that this seemed to make the problem go away.
Now, I've added the Facebook and Splash modules and my app now consistently won't go past the splash screen after I install an upgraded version unless I forcibly uninstall the old version first. Presumably, it dies before creating the webview. Any idea why I would need to uninstall my app first before upgrading? Is this a known behaviour?
I want to make sure that my users don't experience this when upgrading.
My app runs happily without Forge, and doesn't have any particular dependencies on localStorage data. I don't have a Mac and have been installing via iTunes in Windows, so I don't think I can access logging information.
You should have a look at this post:
How application get update from apple store?
The quick answer is when you update an app, you install the new bundle but you keep the user data stored previously such as a local DB. If you changed the local DB in the new app (or anything else) your app can crash when updated but is fine when downloaded from scratch.
I am trying to simulate an upgrade from version 2.0 to 2.1. I have version 2.0 hosted in testflight, so I did install it in my device. Then I tried running the app from xcode. However what happened is that the app did not get overlapped, instead it created two apps with the same name. How can I make it such that when I run the app from xcode it overlays the old version?
I've made sure that the bundle identifier is the same.
Well the info you can get while updating can be found # this link here.
when user updates an app, Documents folder is stored as is, including
NSUserDefaults (but, sometimes user download app via iTunes and
replace the whole application, crying 'OMG! update killed all my
levels progress!'); Application bundle is erased and replaced by new
one (anyway, it is readonly for user); Re-deployment of new build
version will be enough;
You can't access the appstore inside the simulator because: # link here
It's a simulator not an emulator. Even if there was an App Store in
the Simulator, none of the apps in the store would work since they are
compiled for ARM CPUs while the Simulator runs x86 code.
Another stack overflow # link here states:
Build and install your old version, generate some data, and then
install the new version on top of it.
For testing before submitting to the Appstore I generally download
from the AppStore again the old version, and then install with Xcode
the newer version - for your next update... ;-)
And another stack overflow (that I lost the link for) states:
No, the simulator runs i386 binaries and iPhone appstore apps are ARM
binaries apps.
iOS apps are compiled to machine code, Android apps are run in a
Virtual Machine using byte code and are translated to machine code at
the time they are run.
So no, I don't believe you can run it in the simulator, how ever you can have older projects saved on the iPhone and test both out. And the apple documentation is # this link here.
Read this: https://developer.apple.com/library/ios/technotes/tn2285/_index.html
You cannot simulate update in XCode (neither in simulator or connected device). You have to create IPA file and simulate update process via iTunes.
I have an app approved by app store that is version 1.0, and I want to update the app to version 2.0. I changed version to 2.0 in iTunes. It's in the "waitin for upload" state. I have made some code modification in my version 1.0 and changed the bundle version as 2.0. When I am about to upload the appbinary using xcode, it still shows the version as 1.0. If I m to click the validate button, it gives a message that it's already uploaded. Should I change the bundle identifier? I'd be so grateful if you guys could help me out.
You should update the BundleVersion in your Info.plist file prior to compiling your final release build.
Is the iTunes state "Waiting for Upload"? If not, then you have not yet told itunesconnect that you are ready to upload binary.
Delete your build folder and/or check your target to make sure you are building your release target and not trying to send an old release build.