Publishing on anywhere

[Tetrimino]

Hi!
My app (a board game) is ready to be published. I’m a Google Play developer, but I can’t publish the game because I always get an error message:
“Your APK or Android App Bundle Package uses permissions (android.permission.GET_ACCOUNTS) that require privacy policies.”
I do not manage an account or collect personal information. This is a simple board game. What should I do to get it on Google Play? Or anywhere? (where?)
Joseph

[SteveJG]

@Tetrimino

android.permission.GET_ACCOUNTS

A guess is you use an extension that asks for Contact information See GetACCOUNTS or asks for payments.

Is that true? If not, tell us more about your app.

[Tetrimino]

I do not use an extension in the program. There is only one world record on a remote server (Firebase consol). It is requesting permission for images on your phone only. But now I have reinstalled and denied file access and it still works.
About the program: I developed it for 2 years and now there are 14,561 blocks.

[yusufcihan]

You need to add a privacy policy link to your Google Play listing which explains what data you collect from your users.

Can you show which components you use?

[Anke]

@Tetrimino

But now I have reinstalled and denied file access and it still works.

If the permission isn't needed in your app, try to remove it from the Manifest.

[Tetrimino]

@Anke

If the permission isn’t needed in your app, try to remove it from the Manifest.

How can I do it?

[Tetrimino]

@yusufcihan

You need to add a privacy policy link to your Google Play listing which explains what data you collect from your users.
OK. How?
Can you show which components you use?

I use FireBase component to store worldrecordlist on a server what every player can get if hit the record.
I don't collect data from users or account only player type name to save worldrecord.

[Anke]

@Tetrimino

How can I do it

Almost the same steps as shown here:

How to build a big app → APK max. 100 MB or → AAB 150 MB

Steps to build a big app for APK → max. 100 MB or AAB → max. 150 MB (new, added on Aug 31, 2021) 1. APK (Note: apps that were released before Aug 1, 2021 can still use APKs !) You can use e.g. APK Editor Studio for that. First download the keystore "android.keystore" from your AI2 account and rename it to: "android.ks" remove some big files (png, jpg, mp3,…) from the assets (AIA < 10 MB, better < 5 MB) build APK decompile APK (re)insert the missing files to the assets recompile your …

1. build APK
2. decompile APK (APK Editor Studio)
3. edit the Manifest
4. sign APK
5. save / recompile

[Tetrimino]

Why does App Inventor by default make it a manifest that I want to access accounts?
This is very annoying and unnecessary.

How can this be disabled?

[Anke]

@Tetrimino

Why does App Inventor by default make it a manifest that I want to access accounts?

As @yusufcihan said, show all components (& extensions) used in your app.

[yusufcihan]

@Tetrimino

Why does App Inventor by default make it a manifest that I want to access accounts?

In a empty app, there will be no GET_ACCOUNTS permission in the app, (you can check it by compiling a blank app) when you use a component or/and extension which requires a specific permission, then it will be added to manifest directly.

That's why we are asking which components and extensions you use in app. Without this information, we can't help about your question.

[Tetrimino]

OK. I say:
No extension at all.
Components:
Timers (lot of)
TinyDB (for local storage)
FireBaseDB (for world record storage)
Notifiers (for pop up notification)
Canvas
Balls
ImageSprites
Labels
This is a simple board game.