Skip to content

Tag: google-play-console

Google Play Console: ‘Your app signing key’s encryption strength does not meet Google Play’s recommended minimum standard’

I enrolled my apps in ‘Google Play Signing’. Now I see in the console the following message: I thought that it is due the fact that all my apps were initially signed with the same release key (that I uploaded to Google Play Console during the enrolling procedure to Google Play Signing). So I thought that Google Play sees that

Google Play store continuous rejection due to NOT compliant with the All Files Access Permissions policy [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. This question does not appear to be about programming within the scope defined in the help center. Closed 2 months ago. Improve this question Google’s review team keeps rejecting our App after Target SDK API level to 30 migration. The rejection reason is that your

ARCore: How to make my app available on GPlay only to devices that support Depth API?

I have an app that uses Depth API. As mentioned here: Depth API is not supported by all devices that support ARCore. How can I specify in my Manifest (or elsewhere) that my app requires a device compatible with Depth API ? Indeed, I don’t want to see my app to be downloaded by users who can’t use it!