![]() ![]() Unlike Apple’s approval process, Android’s approval process is less stringent and more time-consuming, as it utilizes both experts and automated tools. Thank you Google Play Support, you are everything but support to developers.It can be a hassle to submit your app on Google Play Store, especially if your app gets rejected without you knowing why or how to fix the problem. This migration and support process was completely a failure. They've always rejected my uploads with the same e-mail which is impossible to decode for a human being. I couldn't find any help from Google's official docs. I've found this solution referencing from this answer. Hereby, I would like to congratulate Google Play Support as they've shared all these details within their documentation, within their rejection e-mails, and within their super fast response to the appeal. Sent these uploads to review at once and voila, Google accepts your uploads!. ![]() Went to "Publishing Overview" page, activated Managed Publishing in order to manually publish my uploads to Production and other tracks as they got accepted.Uploaded 2.24.1 (build 3) to the Production Track.Created another build 2.24.1 (build 3) which was completely the same as build 3.Uploaded 2.24.1 (build 2) to the Internal Testing Track.Created another build 2.24.1 (build 2) which was completely the same as build 1.(I've paused them as I won't use them actively, you may not want to pause it) Activated our inactive tracks (Open, Closed Alpha, and Beta Testing Tracks), uploaded the same build 2.24.1 (build 1) to these tracks, and then paused those tracks.upgrading targetSdkVersion to 30, removing MANAGE_EXTERNAL_STORAGE permission, etc.) Created a new build 2.24.1 (build 1) with all necessary changes.(Before my countless update trials, our latest version on Production was 2.23.5 (build 1), our active tracks were Internal Testing Track and Production, and I was trying to upload my updates to Internal Testing Track.) I had the same error for a month but finally, Google Play Store accepted my uploads.īriefly, what I did was to create new builds for each track, and -interestingly- it worked! Is the issue with Storage Policy, or something else? ![]() I also removed READ_EXTERNAL_STORAGE permission from the app, but still got the rejection with same reason from Google Play. Note: I am saving all my media files in app-specific internal storage.Īlso, I have the permission of READ_EXTERNAL_STORAGE in my SDK as we have chat feature in our app to get images and videos of device to sent it.Īccording to Use of All files access (MANAGE_EXTERNAL_STORAGE) permission READ_EXTERNAL_STORAGE permission has not impact. This is the email received from Google Play for the rejection reason. Previously, there was a permission of MANAGE_EXTERNAL_STORAGE in one of the SDK Manifest.Īfter removing MANAGE_EXTERNAL_STORAGE permission and storage permission ( WRITE_EXTERNAL_STORAGE) completely from my app, uploading the app on store, app update gets rejected again. I have an application on play store to whom the targetSdkVersion is update to 30 from 29, which is getting rejected again and again by Google Play after an update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |