Reconnecting for each activity is absolutely fine. Broadly there are 3 ways I’ve seen of people implementing this: Implement mostly in a baseactivity, and have the others extend that. This is connect/disconnect in each activity, but with code in only one place. Implement connect/disconnect in a fragment, and include that in activities where auth is … Read more
OAuth Client Verification Starting July 18, 2017, Google OAuth clients that request certain sensitive OAuth scopes will be subject to review by Google. OAuth Client Verification Starting July 18, 2017, Google OAuth clients that request certain sensitive OAuth scopes will be subject to review by Google. Review is not required if you are only using … Read more
You are correct Google don’t offer a test user API in the same way that Facebook do. I think you have two options: Use “real” Google users as you stated. This can cause issues if Google blocks these accounts or adds extra checks to test if they are real users to not (Phone verification). They … Read more
Share your Drive account’s folder to your service account. Your service account’s addresss looks like XXX@XXX.iam.gserviceaccount.com. Then your service account can see the shared folder from your Drive account. So you have 35GB service account.
Clear your browser cache. Started getting this error in Chrome and then I created a new client id and was still getting the issue. Opened firefox and it worked, so I cleared the cache on Chrome and it started working.
This error occurs when there is an existing SIGNING CERTIFICATE FINGERPRINT (SHA1) on Google Developers linked to a different account. Solution is to delete the project that is using that SHA1 in console.developers.google.com for the old/incorrect project. You cannot change the SHA1 fingerprint once it is set. Remember that deleting the project takes 7 days … Read more
Please see https://stackoverflow.com/a/71491500/1213346 for a “proper” solution. This answer is just an ugly workaround that the community seems to like. … Here is a cringy workaround for this situation: Replace urn:ietf:wg:oauth:2.0:oob with http://localhost:1/ in the code posted in the question. This makes the flow go through, my browser gets redirected and fails and I get … Read more
From the specification point of view, what you are encountering is [OpenID Connect]. id_token is a [JWS] signed [JWT]. In this case, it is a “.” separated string with three components. The first portion is the header. The second is the payload. The third is the signature. Each of them are Base64url encoded string. When … Read more
I was having this exact issue and this solution worked for me. In short: clear your browser cache. In Chrome: Settings → Privacy and security → Clear browsing data → Cached images and files
Solution: Go to your developer console. Go to OAuth consent screen. Go to +Add users, under test users. Add the users for the test (even the owner email address if not working without it)