Using OAuth sign in for an app and it's getting stuck during the loading screen as seen below. The status has been changed to 'in production' as you can see, and no verification is needed according to google. It does say however my app has not been reviewed, does my app need to be put on the play store having been reviewed for this to work? Currently it's only on internal testing track and yet to be published. Any help on this is much appreciated.
Just to note this works fine when app is in testing status.
Related
I have been trying to solve this for many days now, to no avail. I want to use the google-fit APIs, and it seems that I am getting stuck in an infinite loading screen during the OAuth Consent flow.
For the consent screen I have:
Gone to the google cloud console
I have enabled Google Fit
Setup the OAuth consent screen with a logo, company name, etc
Added scope that I need
Added me as a test user
I also created the credentials:
I got the SHA-1 of my debug Keystore, which is used to sign the test version of the application
I created a new Android credential, giving the SHA-1 and the package name from the AndroidManifest.xml file.
The code I use is just the android sample for Google Fit here here: https://github.com/android/fit-samples/tree/main/BasicHistoryApiKotlin
Everything works fine when the OAuth consent screen is in test mode.
However, when I put the Oauth Consent screen in Production mode, it stops working.
I get stuck in this screen, which appears immediately after selecting the user account.
By taking a look at the logs, I see this error:
2021-10-22 17:44:53.737 2571-3763/? E/Auth: [GoogleAccountDataServiceImpl] getToken() -> NEED_REMOTE_CONSENT. App: com.google.android.gms.fit.samples.basichistoryapi, Service: oauth2:https://www.googleapis.com/auth/fitness.activity.write
NOTE: This happens only when submitting the OAuth screen for production. In test, it works correctly. Normally I should be able to see this screen https://support.google.com/cloud/answer/7454865?hl=en (since I am not verified) and be able to proceed after clicking a button. But this does not happen.
NOTE 2: I know this has appeared multiple times in stack overflow, but my case has to do with my consent screen in production mode (which should still work according to Google with a warning), even if Google hasn't approved it.
I would appreciate any help the community could give me. Has anyone encountered issues like this when going into production?
My app uses the Google Drive API to back up user files. I wanted to test my app sign-in from scratch so I manually revoked the app from my Google account settings but when I go to sign in again, I'm stuck loading the consent screen (see below) after choosing my Google account.
This is what I have...
Publishing status is "Testing", user type is "External", and I've added/using the right test users
Registered both my debug and production keys under OAuth 2.0 Client IDs
Scopes are only "./auth/drive.appdata" and "./auth/drive.file"
Domain is verified, provided organization website, support email, privacy policy link, and custom app icon
This is what I've tried...
Reinstalling the app and clearing data
Waiting about 24 hours
Removing the Google account from the device and signing in again
Deleting and reuploading my debug SHA-1 key
Disabling and reenabling the entire Google Drive API
Using a different Google account that has never been used with my app before (makes me think it's something on Google's end)
Using different test devices (emulator + physical devices)
Checking out old code branch from known-good time (in other words, sign-in code is the same)
I emphasize again that this sign-in and OAuth flow was working before (albeit showing the consent screen for "unverified" apps since it's still under development). I have not changed any scopes nor reconfigured the OAuth consent screen.
Does anyone have advice on other things to try here? Given that this was working before, I'm not sure what else I can change from my Google APIs dashboard.
I understand that my question is very similar to one asked before, however in that case apparently using a different account ended up working – that is not the case for me.
Mine was the same case. It used to work fine, but then after some months Google sign in Screen asked verification, and then after some days this loading stuck issue appeared.
But the issue was of Goole Drive Scopes if you don't want to go for verification and your use case is simple then use recommended scopes as mentioned here https://developers.google.com/drive/api/v2/about-auth
I just wanted listing, getting and creating of files, the below scopes did the work for me
GoogleSignin.configure({
scopes: [
'https://www.googleapis.com/auth/drive.appdata',
'https://www.googleapis.com/auth/drive.file',
],
...
...
});
taken the create file scope from here https://developers.google.com/drive/api/v3/reference/files/create
I had the opposite problem of most of you: my consent screen worked fine in testing mode but got the infinite loading bar in production. It turned out I was using the wrong Google Photos scope in my app code. I was only requesting https://www.googleapis.com/auth/photoslibrary.readonly in Google Cloud Console, but in my app I was using https://www.googleapis.com/auth/photoslibrary. I'm still not sure why I was allowed to use a broader scope in testing but not in production.
Had a similar situation when my app was rejected for using 'YouTube' in the description after being on the Play Store for 4 years...[but anyway]
After dinking with it for a long time and creating new credentials all kinds of stuff
I went to:
google account
revoked access for the app in question
in the dev console: move the app back to testing [make sure you have testing users on your list]
uninstall the App
install the app
after I picked the account, I got the same blank consent screen with a twirling progress dialog, but I also got an email; once I confirmed it was me through the email the progress bar went away and I got the oauth dialog as expected, when I clicked allow, everything worked. Back when I originally built the App before it was rejected, I don't remember the email confirmation being required, but I could be wrong. I swear I had tried this a dozen times. I wonder if Google does something on its end...
I eventually got it working after I changed my consent screen to production mode instead of testing. The issue on Google's end (see comments) seems to have been closed with "Won't fix (inactionable)".
Update: There appears to be different causes for being stuck at the OAuth screen. In my particular case, it turned out to be a Google-side issue that I believe they later may have fixed. Other answers here may be equally helpful but I've accepted my own answer because that was specifically the conclusion to my own problem.
I recently uploaded my first application to Play Store, a link to my application with the services of admoob, but for some reason only test ads appear and not real and I'm sure everything is correct with the code I also applied to google to check the application and nothing changed
Update. My app which was also showing the test ads only, I did two things:
Set up the ad-apps.txt in Admob
After my app got "reviewed" and "published" in Play store, the app started showing live-ads.
Until the time it was in "being reviewed", it used to show test-ads.
Please check if you have updated the ad-mob app ids to the correct value from your account and not the one which was used for test-ads.
I assume you would have done this, check your app from another device or ask your friends to download and see what they see. If they see the real ads, it would mean Google has stored your device id as test device for your app.
I uploaded an app to internal testing track to the dev console and added a user.
When I go to the app page through the link, it shows (Internal Beta). But the app version I added isn't there. Even though I got a notification that it had been processed and should be live.
So the test user is succesful, and the app was added. But even though it says I am a beta user it doesn't show any app?
Right so I followed the test link to store, but it turns out you can't do that on your phone as it will just get you to the store app which only shows the live version. You need to follow the link on a desktop and send it to your phone from there...
Today I added my first application to play google stores. Send your application went smoothly. The application was in store. But as I want to download this application pops up an alert: Authentication is required. Sign in with your Google Account. I might also add that I am logged into your Google account, and checking whether the application runs on several other phones. But unfortunately, the situation repeated itself. Very Please help.
I had the same problem and how to fix it is very simple just go to your apps description and update it with anything I just added one word clicked update and an hour later worked perfectly
I cant comment as I am a new user.
But it seems its an issue with the Google Play, as every one is facing the same issue.
I got 7 apps uploaded yesterday and none of them are working. I have retried to upload again today, and waiting to see the outcome.
Let me know if your apps are working fine now or if any updates on this.