I just updated my app in BETA state to Firebase 12.0.0 and when I was going to upload a new version to the Play Store I recieved an error because my app is asking for the permission PHONE_STATE and I need to add a privacy policy to the application to upload the new APK.
After check different changes I saw that this permission is being ask by the last version of Firebase(12.0.0) in Android. Which doesn't allow me to continue my beta testing phase without add a privacy policy.
Why is this permission need it since the last version? Is a bug? any suggestion to continue updating my application without add a Privacy Policy( I will add it in the future, but now now).
This was a mistake in the packaging for 12.0.0 and will be resolved in 12.0.1. You should revert to whatever version of Play services you were using before, or wait for 12.0.1 to be released.
They say fix this with 12.0.1 You can check Release Notes.
It was just fixed in 12.0.1 release.
Please, check the release notes:
https://developers.google.com/android/guides/releases
Related
Google not allowed to roll out new build. Giving error sensitive permission issue.
In my flutter app, 'android.permission.REQUEST_INSTALL_PACKAGES' sensitive permission was added by 'open_file' plugin. Earlier i can upload build, but as per google current policy need to declare sensitive permission.
So I removed sensitive permissions which are not required in my app and tried to publish again. Still google didn`t allow to publish the latest build because this permission has been found in my previous testing build. I tried to change the testing build but didn't succeed. When i tried to change testing build that time google show sensitive permission issue in my previous production & previous testing build.
Please suggest me, how can i publish the new build.
Use open_filex package, Remove 'android.permission.REQUEST_INSTALL_PACKAGES' permission from android manifest and upload latest build in app console.
Open filex package has Removed REQUEST_INSTALL_PACKAGES permission in Android to comply with GooglePlay publish policies.
I tried updating the app. However, it was rejected by Google. The reason was that the “REQUEST_INSTALL_PACKAGES” permission was used. Surprisingly, the version I tried to update doesn't use that permission.
I investigated where those permissions are being used. That permission was used in a version a year ago. When I looked through the app bundle explorer, the Release Status of the old version of the app was active. Even after updating the version, it strangely survived.
Is there any way to delete the app bundle whose Release Status is Active?
You cannot delete an artifact that has been already released in a track. However you can publish another version on top of it with a higher versionCode to replace it.
Once I have put an APK for the beta version can I rollback the APK if it contains any changes or errors in the same version?
You can't rebuild a new version of an apk from the apk itself.
Have the app developer do the following:
Rebuild project in its previous state with higher version number (must be higher than all previously submitted versions)
Resubmit
From Google's Android "Developer Console" page:
Note that rollbacks aren’t supported due to the app versioning
requirements of the Android platform. If you need to rollback,
consider launching a previous APK with a new version number. However,
this practice should be used only as a last resort, as users will lose
access to new features and your old app may not be forward-compatible
with your server changes or data formats, so be sure to run alpha and
beta tests of your updates.
You can not Rollback your previous APK you need to upload new version with bugs fixed..
The user can use the OPT-IN url to opt-out of the testing track, this works for both open and closed tracks :)
I have published new version of Android application to play store. But I do not have 'update' button for updating from previous version. I have only 2 options 'Open' and 'Uninstall'.
For new version I need to uninstall existing and then download new version. I am generating signed APK and using the same key. I have also changed the version code and version name.
Is there anything I need to add in code for autoupdate? I need to avoid uninstalling everytime I have new version of application published to play store. Please give me any solution if you have.
When did you push the app? It may take several hours before it's live. The Play Developer Console should provide some info on when the rollout is available. It may be possible to specify a rollout time when the update will be live.
If you have been debugging the app on your phone, and the version code is the same as on your phone or your app is the debug signature, you won't be asked to update.
you should change the version code and version name in your gradle file of app module
I think you changed version code in manifest file instead of gradle file.or you changed version in wrong gradle file
We have followed the instructions at http://developer.android.com/google/play/billing/billing_testing.html#billing-testing-real to introduce in-app billing to our application, and now want to add our live product IDs.
As per the instructions, we build our APK with the necessary permissions and sign the APK. Once the upload is complete, we get the following error :
"This configuration cannot be published for the following reasons : All devices that might receive version 3001 would receive version 3002."
We do NOT want to publish this APK, but only upload it as a Draft APK, in order to complete testing of IAP.
Does anyone have a workaround to this?
I was able to work around this problem by switching back to the old version of the Developer Console and then deactivating my one older version, after which I deleted that older version and saved the app. Upon returning the the new version of the Console, the problem was resolved.
However, I believe the old version of the console will soon become unavailable, so this approach may not be available much longer.
Deactivate the old version first and then you should be able to publish the new version of the app.
Switch to the old version and update the new apk...
It works for me.
Thanks Carl