I am trying to create a new release with no sensitive permissions asked. but when i go to app releases it shows :`
Previously declared permissions (2 permissions)
android.permission.READ_SMS
android.permission.RECEIVE_SMS`
I deleted all artifact libraries apks drafts .
What is the procedure to get rid of it?
I solved it.
Go to your artifact Library and check if there is any active artifact which contains these permissions. Now create a build and overwrite those active artifacts with your new build. When every other release track like beta , internal do not contain any sensitive permission, just create a build for production and you will see it gone.
Related
I build flutter application and i tried to publish application in Google Play Store but application reject many time for same reason maintioned in below image
I use open_file package and this package contain REQUEST_INSTALL_PACKAGES permission so i tried with remove permission for this package .xml file and also to remove package and upload but still application get rejected.
All permission use in application are below any body tell me for which permission it will reject every time.
Below screenshot for rejected status with detail notes
One of your dependency contains that dangerous permission
delete the dependency which contains that permission
if your yaml file contains
open_file:
remove that dependency it contains that permission
I want to disable android.permission.ACCESS_BACKGROUND_LOCATION in my Xamarin app because I dont need it anymore but when I uncheck the checkbox in the Properties tab:
And delete the permission request in the android.manifest file itself:
The permission request still seems to be there according to the manifest file from the archived .aab file and also according to the google play dev console.
I also searched my entire solution and dident find any other references.
Is there anything that causes this request or anything I forgot to delete?
Check the merged AndroidManifest.xml in obj\Release\nnn\.
If it is there, then something in your build process has added it.
If it is not there, then add to your question more details about how you build and launch to google play dev console - what you are seeing at dev console should match what is in the obj version of that file.
It was defined in the AssemblyInfo.cs and after removing it there everything was fixed.
When Uploaded App in Google play getting privacy issue in pre-launch report, how to get resolve this issue.
this is as a result of automatic comparison with similar apps, if you are sure that you are using IAP correctly do not worry about it and continue and way.
Clean and Rebuild your project and Add this line in your Manifest
file.
<uses-permission
android:name="com.android.vending.BILLING"
tools:node="remove" />
Furthermore,
Delete and Clear all the Caches from the Users Profile folders located in your system .android and .gradle Located: C:\Users\DELL\.android
Update and Download the latest SDK from the SDK Manager and delete the older, unused ones.
Update Gradle Wrapper.
distributionUrl=https\://services.gradle.org/distributions/gradle-7.3-all.zip
I've fixed this by researching merged manifest, text file which located in app\build\intermediates\manifest_merge_blame_file\{flavorBuildType}\manifest-merger-blame-{flavor}-{buildType}-report.txt
In this file we can see all permissions which are available in our compiled build + library which is bring this permission to merged permission list.
You can easily find which library brings permission which invoke the warning from play market:
In my case it was unused library, so as a result I've just removed unused library.
Also anouther solution - check newest version of the library and try to update (and check permissions with new library), for example in oldest version of dji sdk there is a lot of system permissions, but in new version the list was cleanuped.
Also you can remove the permission from thrird party libraries like:
<uses-permission
android:name="com.android.vending.BILLING"
tools:node="remove" />
But in this case ^ some part of functionality can be restricted.
I pushed a beta version to Google Play that accidentally added more permissions compared to the version that's current in production.
Before pushing the final new version to production via a staged rollout, I removed those permissions, but despite that, users are still complaining about the new permissions when they received the update on the Play Store.
Why are the new permissions still visible? I removed the APK from the beta channel, neither of the production APKs (both the old one, and the new one in staged rollout) have the new permissions. I even see those new permissions in the Play Store listing.
By using a newer SDK but not changing the targetSdkVersion of all my imported modules, I automatically inherited some implicit permissions.
For one, there is one library with a targetSdkVersion of 3 - that will automatically add READ_PHONE_STATE, as already documented in this answer, and the official docs.
This can be easily seen by looking at the manifest merger log in build/output/logs/manifest-merger-release-report.txt:
android:uses-permission#android.permission.READ_PHONE_STATE
IMPLIED from AndroidManifest.xml:2:1 reason: com.foo.library has a targetSdkVersion < 4
The other problem was having READ_CONTACTS set, but at least one library used both minSdkVersion and targetSdkVersion < 15. That automatically added READ_CALL_LOG. See the documentation about this. Curiously enough I didn't see a mention of that in the merger log, but I may have missed it.
The final APK permissions can be checked with aapt:
aapt dump badging build\outputs\apk\foo-release.apk
That prints out the list of permissions.
Full credit to CommonsWare for leading me to this. Thanks Mark!
I am trying to publish an upgrade to my app in Android Market. I am using the same key and alias as before (I have only one key and a single alias). But I get the error "The apk must be signed with the same certificates as the previous version.". This is not the first time I am uploading upgrades. Never had problems before.
The only difference I have this time is I added a new sub-package to the project. My base package is "in.vasanth.android.droidsave". I added a package "in.vasanth.android.droidsave.db". Does adding a package affect the upgrade? Or did I some how mess up my key?
Make sure that you are uploading an exported .apk file, not the one that is normally built in the project's bin directory. Adding a sub-package won't affect anything as long as you haven't changed the package name for the overall application in the manifest file.