IssueTracker

Feedback form affected user: he created many Google account (to do some tests).
Could this be related to a too big amount of Google accounts created, accounts that are 'linked' to his initial email address (using the same initial account for recovery)?

adding links afor

"I also found out that the error code in AccountManager.convertErrorToException was code ERROR_CODE_INVALID_RESPONSE"

https://android.googlesource.com/platform/frameworks/base/+/98199ae/core/java/android/accounts/AccountManager.java#2194
https://android.googlesource.com/platform/frameworks/base/+/98199ae/core/java/android/accounts/AccountManager.java#157

Adding some "com.google.android.gms.persistent" logs that could help.

2019-03-06 08:48:47.948 12564-12564/com.google.android.gms.persistent W/ChimeraUtils: Non Chimera context
2019-03-06 08:48:47.948 12564-12564/com.google.android.gms.persistent W/ChimeraUtils: Non Chimera context
...
2019-03-06 08:48:48.151 12564-12580/com.google.android.gms.persistent W/Auth: [GetToken] GetToken failed with status code: ServiceDisabled
2019-03-06 08:48:48.151 12564-12580/com.google.android.gms.persistent W/GLSActivity: gwn: ServiceDisabled
        at gwr.a(:com.google.android.gms@15090017@15.0.90 (040306-231259764):11)
        at gwq.a(:com.google.android.gms@15090017@15.0.90 (040306-231259764):2)
        at gwq.c(:com.google.android.gms@15090017@15.0.90 (040306-231259764):6)
        at gwp.a(:com.google.android.gms@15090017@15.0.90 (040306-231259764):1)
        at gyn.getAuthToken(:com.google.android.gms@15090017@15.0.90 (040306-231259764):9)
        at android.accounts.AbstractAccountAuthenticator$Transport.getAuthToken(AbstractAccountAuthenticator.java:244)
        at android.accounts.IAccountAuthenticator$Stub.onTransact(IAccountAuthenticator.java:113)
        at android.os.Binder.transact(Binder.java:627)
        at dvm.onTransact(:com.google.android.gms@15090017@15.0.90 (040306-231259764):3)
        at android.os.Binder.execTransact(Binder.java:697)

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build
Which Android build are you using? (e.g. OPP1.170223.012)

Device used
Which device did you use to reproduce this issue?

Steps to reproduce
What steps are needed to reproduce this issue?

Please provide sample project or apk to reproduce the issue.  Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Expected output
What is the expected output?

Current output
What is the current output?

Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report  file to this issue.

Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”.  Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.

Screen record of the issue, for clarity
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

Hi,

I think my problem is related to this:

https://wordpress.org/support/topic/be-careful-everybody-who-is-using-oauth-2-0-to-access-gmail-google-gsuite-apis/

I am using "oauth2:https://mail.google.com/"

I do not understand how I must ask for my app to be allowed to use this.

https://console.developers.google.com/apis/credentials/consent?project=elementiqueapp&folder&organizationId

Can you please help? My app is com.elementique.messages
https://play.google.com/store/apps/details?id=com.elementique.messages

Thanks

We have passed this to the development team and will update this issue with more information as it becomes available.

Hi,

Some (important?) feedback from my side:

Summary:
 - I created a new "Client ID for Android" on https://console.developers.google.com/apis/credentials  and now I am not able to reproduce the bug anymore.
 - I have to check with affected customers to see if the issue is solved on there side: to be confirmed
 - Is this really fixing the issue? Was it just a configuration issue?
 - Why is my android app affected by that? It used to work fine since 2012. Has this something to do https://wordpress.org/support/topic/be-careful-everybody-who-is-using-oauth-2-0-to-access-gmail-google-gsuite-apis/ ? even if it's just for  "Gmail/Google/Gsuite APIs" and **not** for Android

Detailed explanations + questions / remarks:

In the meantime, I investigated on my side and, in the frame of this investigation, I followed the procedure described into this guide:

    https://developers.google.com/identity/sign-in/android/start

At point 2, I had to configure click on 'Configure a Project' button.
As a result, some new have been created on https://console.developers.google.com/apis/credentials page
"OAuth client"  & "Web client (Auto-created for Google Sign-in)" (screenshot attached with date March the 6th ,i.e., yesterday)

When I click on "OAuth client", I can see that a "Client ID for Android" has been created for my "com.elementique.messages" app.

and now the “android.accounts.AuthenticatorException: ServiceDisabled” is not happening anymore! It's gone! (just tested 30 minutes ago)

-> I'll check with the customers that where blocked and see if this is working for them, because, for the time being, I

If yes, that would mean that a "Client ID for Android" is now needed to use Authentication scopes like "https://mail.google.com/"?

Can dev team confirm my com.elementique.messages is now in good shape with Google API portal OAuth client Id for Android app
and that I do not have to change anything to obtain OAUth2Token to use GMAIL using IMPA connection?

Also, I stumbled upon this page that says there are now new restrictions about some Google API

https://wordpress.org/support/topic/be-careful-everybody-who-is-using-oauth-2-0-to-access-gmail-google-gsuite-apis/

But I am not using these! I am just using the android SDK.. and, as an Android developer, I received no warning about that, which makes sense, since it's for "Gmail/Google/Gsuite APIs"

Maybe there was a 'communication bug' between teams on your side?


Thanks a lot for your help :-)

screenshots

It seems that the new "Client ID for Android" I created for my Android app on page https://console.developers.google.com/apis/credentials did solve the problem!

More info here https://stackoverflow.com/questions/55008300/rare-exception-android-accounts-authenticatorexception-servicedisabled-what/55118077#55118077

Should the Android SDK documentation be updated about that?

Thanks

Hi,

The problem is now back again and I did not make any code changes in my app.

My customers now say the app is not able to connect to GMail anymore.

I could reproduce the problem on my side:

How I did to reproduce the problem:

1 - I have my com.elementique.messages app working fine (i.e. able to interrect with GMail using IMAP) , using the scope "oauth2:https://mail.google.com/" along with my email personal account pascal.dalfarra@gmail.com - everything is OK

 2 - I went on https://myaccount.google.com/permissions?utm_source=google-account&utm_medium=web and remove the access I granted to my com.elementique.messages . This access is ask programmatically by the app: this has always been working fine, except early March 2019, after a change on Google 's side.

3 - I deleted the data from my android app and restarted: it tries to ask access to "oauth2:https://mail.google.com/" scope, but then an exception occurs (like in ealry March):
2019-07-26 18:48:32.377 12502-12502/com.elementique.messages W/System.err: android.accounts.AuthenticatorException: ServiceDisabled
2019-07-26 18:48:32.377 12502-12502/com.elementique.messages W/System.err:     at android.accounts.AccountManager.convertErrorToException(AccountManager.java:2217)
2019-07-26 18:48:32.378 12502-12502/com.elementique.messages W/System.err:     at android.accounts.AccountManager.-wrap0(AccountManager.java)
2019-07-26 18:48:32.378 12502-12502/com.elementique.messages W/System.err:     at android.accounts.AccountManager$AmsTask$Response.onError(AccountManager.java:2060)
2019-07-26 18:48:32.378 12502-12502/com.elementique.messages W/System.err:     at android.accounts.IAccountManagerResponse$Stub.onTransact(IAccountManagerResponse.java:69)
2019-07-26 18:48:32.378 12502-12502/com.elementique.messages W/System.err:     at android.os.Binder.execTransact(Binder.java:573)

this happens when I do a

       accountManager.getAuthToken(account, "oauth2:https://mail.google.com/", null, activity, accountManagerCallback, null);


I am now totally lost and do not understand at all what's going on.

As an Android developer, what am I suppose to do?
I just use the Android API to get access to this, not any Google cloud or web google API: can you please explain me what I should do to make this work as before (this has been workind since 2012)

According to my logs, very first problem occured on "2019-07-26 08:18:36" (time zone Belgium)

Google Play Store customers now start the refund procedure: this is not acceptable. I definitely need some help there.

I hope you can help me with that quiet quickly.

Thanks beforehand for your help and understanding.

FYI, I am already in contact with the Google Play Developer support team: they pointed these urls to me:

    https://support.google.com/cloud/answer/9110914#restricted-scopes
    https://developers.google.com/terms/api-services-user-data-policy

I do not understand: one is about the "Google Cloud Platform OAuth policy violations": I do not use Google Cloud: I use the Android API

The second is about restricted scope

Product         Permitted Application Types
Gmail  

    Native and web email clients that allow users to compose, send, read, and process email via a user interface
    Applications that automatically backup email
    Applications that enhance the email experience for productivity purposes (such as applications for customer relationship management, delayed sending of email, or mail merge)
    Applications that use information from emails to provide reporting or monitoring services for the benefit of users (such as applications that automate travel itineraries or track flight or package delivery statuses)


My app is a 'native' android client, so it should OK for it to use this scope, right?

Also this second page mention this url https://console.cloud.google.com/apis/credentials/consent : should I do something there?

Summary:

I do not understand why my Android email app suddenly does not have access anymore to GMail since today. This already happened early March.
I managed to find a solution on my own at that time (by creating a "Client ID for Android" on https://console.developers.google.com/apis/credentials ) but now it looks like, AGAIN, something change on Google's side, and, AGAIN, as an ANDROID developer, I wasn't warned. (bigger letters do not mean I am screaming... I am just trying to emphasize )

I am totally OK if things change on your side, but I think I should be warned upfront, and have access to clear documentation about which actions I should do in order to comply to the new situation so my app works back again and I do not lose Google Play Store customers.

I am looking forward to have clear guidance and help from your side.

Thanks beforehand,

Pascal Dal Farra

 

Additional info,

I went on https://console.cloud.google.com/apis/credentials/consent?pli=1&project=elementiqueapp&folder&organizationId&duration=P1D
 To ask my app to be verified, but this about web apps, not about Android apps.

How am I supposed to ask for my https://play.google.com/store/apps/details?id=com.elementique.messages Android app to verified?

Thanks

Additional info:

as per https://developers.google.com/terms/api-services-user-data-policy the deadline for that is
"
For Gmail Restricted Scopes:

Enforcement of the Gmail requirements in this section began on January 15, 2019. Applications that had access to Gmail Restricted Scopes prior to January 15, 2019 must obtain their first Letter of Assessment no later than December 31, 2019 to keep access to Gmail Restricted Scopes. All other apps must first be verified and obtain the letter prior to being granted access to Gmail Restricted Scopes.
"

My Android app is using "oauth2:https://mail.google.com/" scope since 2012...

Question:
Why is my app now blocked? If I understand that correctly, I should benefit from a grace period till December 2019, right?
Can you please contact the Google Cloud team so my app is unblocked and I have time to comply to the new policy?

Hi,

I am trying to explain to Google Cloud tech team that my app is an old (Android) app using AOtuh since 2012, I it looks like the message does not go through, or that they consider my OAUth Google Cloud app is a new one (I created some stuff on Google Cloud platform in March / see this thread)

Can I kindly ask you to help, as I have been in touch with some many people at Google (New York, Dublin, multiple support people), but it seems it's just not possible to have someone from Google cloud tech team just to explain my case and unblock my app and ive me time to comply with new OAuth policy without having ALL MY NEW CUSTOMERS blocked?

This is a bottle tossed at sea: I now really feel hopeless about this. Hope you can help.

Thanks

Hi,

As I see some activity here, I'd like to say that this is now OK (at least for me).

I had to go through a "Google certification procedure" so that my Android app can have access (back again) to the "oauth2:https://mail.google.com/" restricted scope.
It's a pity that my app was 'broken' twice by some changes happening at GCP 's side, without GCP team notifying me (as an ANDROID developer)

I hope this will not happen again in the future

Thanks

Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete.