Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sign in with Google temporarily disabled for this app #100

Closed
ADRuf opened this issue Dec 12, 2019 · 7 comments
Closed

Sign in with Google temporarily disabled for this app #100

ADRuf opened this issue Dec 12, 2019 · 7 comments

Comments

@ADRuf
Copy link

ADRuf commented Dec 12, 2019

I'm getting this message when I try to access the Google Analytics API via R rga using the command: rga.open(instance = "ga")

Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In

This was working last month but now I keep getting this error. Any ideas?

@EricGoldsmith
Copy link
Contributor

Doing a Google Search on that error message yields this from Google. So, it seems to be specific to the credentials you're using. Perhaps that article will help you resolve it.

@ADRuf
Copy link
Author

ADRuf commented Dec 16, 2019

Thanks @EricGoldsmith. I saw that article but I couldn't figure out what to do next. I revised my programs to use googleAnalyticsR instead of rga and it is now working.

@EricGoldsmith
Copy link
Contributor

FYI ... similar issue there: https://github.com/MarkEdmondson1234/googleAnalyticsR/issues/292

@ADRuf
Copy link
Author

ADRuf commented Dec 16, 2019

Thanks! Looks like googleAnalyticsR was updated so it works as an alternative. Closing this issue.

@ADRuf ADRuf closed this as completed Dec 16, 2019
@EricGoldsmith
Copy link
Contributor

EricGoldsmith commented Dec 16, 2019

The change to googleAnalyticsR was to the default test account - no code changes to the package. IOW, the author followed the steps in the Google help article above to re-verify the test account.

Something similar for the default test account for this package could also be done, but would have to be done by @skardhamar, who owns the account.

That said, you shouldn't be using the default test account for anything other than testing, but should instead create your own account (as explained here). Relying on the test account will subject you to the whims and abuse of anyone else using it.

@ADRuf
Copy link
Author

ADRuf commented Dec 16, 2019

Got it, I understand now. Thanks for your help and patience on this.

@MarkEdmondson1234
Copy link

Yes it was as @EricGoldsmith says, I needed to re-verify the app with updated scopes and a privacy policy links etc. Long term its best to use your own OAuth2 app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants