Permission GET_ACCOUNTS - Google Play Developer policy violation

760 views
Skip to first unread message
Assigned to ewpa...@gmail.com by taifu...@gmail.com

Attila Farago

unread,
Feb 15, 2017, 11:55:00 AM2/15/17
to MIT App Inventor Forum

Hi!

I am helping a few kids to create an application.
They have created it and uploaded it to Google Play Store.
(Sorry, app is currently in Hungarian - kids are just translating it)

Recently we have received a warning that app is accessing private/sensitive data. (Warning of Google Play Developer policy violation)
With a chat I have received the answer that the app is accessing android.permission.GET_ACCOUNTS.

I have no idea where this is accessed, how the kids can eliminate this.
Any hints?

Thanks,
Attila

Hossein Amerkashi

unread,
Feb 15, 2017, 12:02:24 PM2/15/17
to MIT App Inventor Forum
I believe this would happen when you are using FUSIONTABLES or an extension where it requires account management.

Attila Farago

unread,
Feb 15, 2017, 12:10:31 PM2/15/17
to MIT App Inventor Forum
Hi Hossein,

Wow, I would have never imagined that FusionTables is the root cause.
We are using service account auth.
Checked it in the code (Fusiontables.java) and I suspect that this is there by mistake.


Any hints on how I can suggest a check a a possible improvement to AppInventor developers on this issue?

-Attila

SteveJG

unread,
Feb 15, 2017, 9:30:06 PM2/15/17
to mitappinv...@googlegroups.com
You have several options to stay within Googles policies

1) Provide a Privacy Statement ... https://groups.google.com/forum/#!searchin/mitappinventortest/policy$20violation%7Csort:relevance     All Google wants is a statement that the app collects no personal data and that it uses a public database that requires an access code.

2) Modify the Project's Manifest to remove the android.permission.GET_ACCOUNTS ...this could result in crippling the function of the app.

If you do not remove the permissions that Google is concerned with or provide a Privacy Policy, Google will/may terminate the Google account associated with the project.  This link may or may not help you  http://www.iubenda.com/blog/privacy-policy-for-android-app/   draft a policy.  

You can avoid this issue by posting the app on the MIT Gallery (where you have to post the aia)  or  possibly Amazon which may not require a policy (you need to check).   However, if you do not address the issue, posts in the forum indicates Google may lock your account.  Either provide a policy , modify the manifest and hope the app still works as intended or REMOVE the app from Google Play or do something else to conform with Google's Google Play conditions.   Just something Android developers (even young ones) must deal with to post their app's on Google Play.

Regards,
Steve
Reply all
Reply to author
Forward
0 new messages