Hi,
Exactly the same issue since last week. Using the same package/library +
credentials to connect on two applications :
- the first one is a cron script that operate spooled operations. Working
fine and still ok. It runs every 30mn.
- the second is a web application : it works one time, and then invalid
grant too.
This couple of applications has been working for months but the web
application is failing since last week.
I'm using this sample code to get a session :
// Generate a refreshable OAuth2 credential
// and can be used in place of a service account.
Credential credential = new OfflineCredentials.Builder()
.forApi(OfflineCredentials.Api.ADWORDS)
.fromFile()
.build()
.generateCredential();
ReportingConfiguration reportingConfiguration
= new ReportingConfiguration.Builder()
.skipReportHeader(false)
.skipColumnHeader(false)
.skipReportSummary(false)
// Enable to allow rows with zero impressions to show.
.includeZeroImpressions(false)
.build();
AdWordsSession session = new AdWordsSession.Builder()
.fromFile()
.withOAuth2Credential(credential)
.withReportingConfiguration(reportingConfiguration)
.build();
- DB.
Le mardi 22 novembre 2016 15:44:32 UTC+1, Deepankar Biswas a écrit :
>
> Hi Josh
>
> I am facing this issue and its very strange.
>
> 1) The access is very much there and not revoked.
> 2) I refreshed the token today for my MCC account and it worked for the
> first time and now again invalid grant.
>
> I took the dump of the AdWords user also and it has all valid data.
>
> Where should I look to fix this?
>
> On Monday, November 16, 2015 at 9:49:01 PM UTC+5:30, jnewm...@gmail.com
> wrote:
>>
>> Hello,
>>
>> About 3 weeks ago we started seeing this error when we refresh the access
>> token for many random accounts, { "error" : "invalid_grant" }. We never
>> had any problems refreshing access tokens up until now. Also, not all
>> accounts are having problems refreshing their tokens; many refresh just
>> fine. To temporarily fix the issue we have been reauthorizing each account,
>> but other accounts start to have the same problem. The only information I
>> could find on the forum is that the refresh token has manually been
>> revoked, which doesn't make sense to me. I've read through the
>> documentation at "
>> https://developers.google.com/adwords/api/docs/guides/authentication";
>> and it looks like our TokenUrl, AuthUrl and Scope are up to date. Any help
>> is greatly appreciated, thanks.
>>
>> Get Authorization Code:
>>
>>
>> https://accounts.google.com/o/oauth2/auth?client_id=XXXXX&redirect_uri=XXXXXX&scope=
>> https://www.googleapis.com/auth/adwords
>> &response_type=code&access_type=offline&approval_prompt=force";
>>
>>
>>
>> Below is an example of the url and parameters we are using to retrieve
>> initial access and refresh token:
>>
>>
>> https://www.googleapis.com/oauth2/v3/token?code=XXXXXXXXXXXXX&client_id=XXXXXXXXX&client_secret=XXXXXXXXX&grant_type=authorization_code&redirect_uri=XXXXXXXX
>>
>>
>>
>> Below is an example of the url and parameters we are using to refresh
>> access tokens:
>>
>>
>> https://www.googleapis.com/oauth2/v3/token?refresh_token=XXXXX&client_id=XXXXX&client_secret=XXXXX&grant_type=refresh_token
>>
>
> *DISCLAIMER*: The information in this message is confidential and may be
> legally privileged. It is intended solely for the addressee. Access to this
> message by anyone else is unauthorized. If you are not the intended
> recipient, any disclosure, copying, or distribution of the message, or any
> action or omission taken by you in reliance on it, is prohibited and may be
> unlawful. Please immediately contact the sender if you have received this
> message in error. Further, this e-mail may contain viruses and all
> reasonable precaution to minimize the risk arising there from is taken by
> OfferGrid. OfferGrid is not liable for any damage sustained by you as a
> result of any virus in this e-mail. All applicable virus checks should be
> carried out by you before opening this e-mail or any attachment thereto.
> Thank you - *OfferGrid Networks (P) Ltd*.
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/32406a32-9fa8-4b00-a16a-662ea52d71a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
