I have an Android app that uses Google SignIn as a sign-in method.
In the Google Play Console, I'm supposed to provide a test account for Google to conduct app reviews. However, I'm facing an issue with that.
Even though I provide a Google account to test, as you can see in the below screenshot, there's an Identification Verification step that blocks Google reviewers to proceed with their job.
From my understanding, this step appears when Google suspects a sign-in. Although this test account is created/used in Japan, Google reviewers use it in other countries e.g. India (most of the time), the US, etc, that would be why this sign-in is considered as suspicious.
Then here's a question. What can I do about this situation? Just for your references, I already tried the following but nothing helped.
Disable 2FA (i.e. No additional authentication is configured)
Sign out from the test account in all of my devices (IIRC, with this approach, previously Google reviewers succeeded in sign-in without the Identification Verification step, but seems not this time)
Google reviewers or even their support team will never help me with this so it'd really be appreciated it if you know the workaround. Thanks.
Related
I have created a project at Google Developer Console. And I have followed the steps to create an OAuth Consent screen to ask users for their consent to let me use their email address and Google Calendar for my App. App is still at Test Mode, and everything is working fine.
But for the users of Google Workspace (G Suite) (#domain.com) the consent screen is not working. It just ends up saying that Something went wrong and ... the request is malformed.... I am sure it isn't malformed, because it is just working fine for non-workspace (#gmail.com) users.
I got it working later by Manage Domain Wide Delegation by logging into the Google Workspace Admin account and manually setting up my Apps's service account Client ID and Scopes. The process allowed users of that #domain.com (non-admin) email to get my consent screen working.
But this is not practical. I can't ask every #domain.com email address user to contact their Google Workspace Admins and add my app to the domain wide delegation area manually.
There are apps and services out there which connected to my non-admin Google Workspace account without having my Admin do it for me.
So there must be some way to get my consent screen work on #domain.com email addresses hosted at Google Workspace without involving the Admin account or Domain wide delegation stuff.
How can I get it done? Please help, I can't find any solution online.
EDIT More banging head in the wall, but no similar issues found on the internet. So what I feel like is that I need to wait for my OAuth application to be approved for production for it to work for Google Workspace accounts. PLEASE HELP if you know there is some other issue and I can try to fix...
Thanks.
Looks like there was some temporary issue with Google. I emailed them, and the issue was fixed.
We have a client application that runs on Windows that is used by thousands of users in the financial market in order to make analyses and charts. Since long we have an integration with Twitter where you can easily post a chart together with short text. Many users have asked us to implement a similar feature for LinkedIn since this is becoming increasingly popular among our users.
The API for sharing on LinkedIn works fine for us, but we need to refresh the access token every 60th day, which cannot be made completely seamless for the user. Since our application is not a web app, we need to launch a browser on order to refresh the access token and this is disruptive for the users.
The docs at Authorization Code Flow (3-legged OAuth) says that some selected partners can get refresh tokens as a complement to access tokens. That would be perfect for our integration. How can we become one of those "partners"? I have not found any information how to apply for this.
I have looked for a way to apply to become a partner that can get a refresh token, but failed to find any information.
I am trying to pull data from Youtube Analytics API using R and have hit a wall. I'm getting a Status 403 error. I can confirm that:
I have tried logging out of all accounts, rebooting, re-authenticating and then logging into 1 account and it didn't work
I have tried using just the https://www.googleapis.com/auth/youtube.readonly scope (which is supposed to be correct) and all youtube analytics scopes are authorized within the app (each with their own credential key), it didn't work.
I have tried authenticating from different browsers, it didn't work
I can confirm that the call worked from https://developers.google.com/apis-explorer/#p/youtubeAnalytics/v2/youtubeAnalytics.reports.query.
UPDATE
I have found the solution and updated the code to what is now working
scopes<- c('https://www.googleapis.com/auth/youtube.readonly')
endpoint<- oauth_endpoints('google')
youtubeapp<- oauth_app(appname='Youtube Analytics API',
key=client_id,
secret=client_secret)
youtube_token<- oauth2.0_token(
endpoint= oauth_endpoints('google'),
app = youtubeapp,
scope = scopes)
raw_data<- GET(paste("https://youtubeanalytics.googleapis.com/v2/reports?dimensions=",dimensions,"&endDate=",enddate,"&ids=",ids,"&metrics=",metrics,"&startDate=",startdate,sep=""),
config=youtube_token,content_type('application/json'))
content(raw_data, as= 'text')
I have figured out that access permissions are dictated by Youtube (not API IAM), so for example even though my personal email is owner of Brand account and API I still need to authenticate the call using the Brand Account or it won't work (I get 403 error for personal email). I tried switching my Youtube channel from Brand to personal and then my personal email worked. However, I need it under the brand account, so I have switched back.
I will leave this code up regardless because I found that good examples using R were lacking, I hope you find this useful.
i have test account for google adword
i got source code from provided by google adwords
but it stuck with me below error
[QuotaCheckError.INVALID_TOKEN_HEADER # ; trigger:'INSERT_YOUR_DEVELOPER_TOKEN_HERE']
while i am searching for developer token then
Google Adword Account > Account Setting > AdWords Api Center
in document they are asking for
bur in test account no such a thing like AdWords Api
now for campaign performance may i able to get with test account or i have to spend money to it?
Thanks,
Jimmy Darji
Use the developer token from the production account (even if it’s not approved yet)
Use the developer token of your production manager account when making requests against the test manager account. Even if it’s not approved yet, the token will still work on test accounts, including the ones you just created.
reference here
The Google Analytics Plugin for PhoneGap has an example app that contains the following code:
// Note: A request for permission is REQUIRED by google. You probably want to do this just once, though, and remember the answer for subsequent runs.
navigator.notification.confirm('GA_PLUGIN would like your permission to collect usage data. No personal or user identifiable data will be collected.', permissionCallback, 'Attention', 'Allow,Deny');
I've looked through the Google Analytics mobile SDK docs (although I have not read them start-to-finish) and have been unable to locate this requirement. I also don't see it in the Terms of Service at http://www.google.com/analytics/terms/us.html.
I don't mind requesting permission from the end user, but I certainly don't do it on web sites and I don't seem to recall getting many of these requests within apps that I've installed either.
Is the comment in the code correct?
Found it! Sort of. It's in the Measurement Protocol / SDK Policy doc. It states:
You will give your end users proper notice about the implementations and features of Google Analytics you use (e.g. notice about what data you will collect via Google Analytics, and whether this data can be connected to other data you have about the end user). You will either get consent from your end users, or provide them with the opportunity to opt-out from the implementations and features you use.
That's the Measurement Protocol / SDK Policy. It's not 100% clear to me that it refers to the iOS and Android SDKs. On the one hand, the table of contents type thing on the left has it under Measurement Protocol > Resources. The iOS and Android SDKs are outside of Measurement Protocol. So that suggests it doesn't apply to the iOS and Android SDKs. On the other hand, the Measurement Protocol doesn't seem to have an SDK associated with it, so that the suggests that "SDK" in the title may be referring to the iOS and Android SDKs.
I do wish this were clearer.