Re: Credential could not be refreshed, java client library version v201708

Hi Samanth, Have you tried all of the solutions from above? If they all do not work, please share logs with me via reply privately to author. Thanks, Anthony Google Ads API Team ref:_00D1U1174p._5001UOCjOu:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog:

Re: Credential could not be refreshed, java client library version v201708

Hi Koshish, Even I am facing the same problem (It works fine in my local machine but it fails on server with error= Credential could not be refreshed). Can you please let me the steps to resolve this issue. On Thursday, November 21, 2019 at 1:13:48 AM UTC+5:30, adsapiforumadvisor wrote: > >

RE: Credential could not be refreshed, java client library version v201708

Hi Koshish, Thank you for reaching out to support. Can you make sure that you're using the same set of credentials on both the machines (local and server)? If you could compare the settings used for your local machine with the server settings, it might help you pinpoint the issue. Could you

Re: Credential could not be refreshed, java client library version v201708

On Wednesday, October 25, 2017 at 8:26:22 AM UTC+5:45, hari krishna wrote: > > Seems this is issue with our proxy server, our proxy server changing the > url and that causes this refresh token expire issue. We fixed it in our > side. > > Thanks! > Hari. > > On Friday, September 22, 2017 at

Re: Credential could not be refreshed, java client library version v201708

Seems this is issue with our proxy server, our proxy server changing the url and that causes this refresh token expire issue. We fixed it in our side. Thanks! Hari. On Friday, September 22, 2017 at 11:11:00 PM UTC+5:30, Bharani Cherukuri (AdWords API Team) wrote: > > Hello Hari, > > To

Re: Credential could not be refreshed, java client library version v201708

Hello Hari, To rule out issues with the client library or your *ads.properties* file, could you issue the access token request via curl as follows? curl --data "grant_type=refresh_token" \ --data "refresh_token=*YOUR_REFRESH_TOKEN*" \ --data "client_id=*YOUR_CLIENT_ID*" \ --data

Re: Credential could not be refreshed, java client library version v201708

> > Below property commented out in ads.properties file. Can you Please check >> is there anything to do with this. >> > # Enable/disable automatic OAuth2 token refreshing. Default is enabled. #api.adwords.refreshOAuth2Token=false Thanks! Hari. -- --

Re: Credential could not be refreshed, java client library version v201708

Hi Bharani, I have given error message above. Same Error message I am getting.It is not giving any SAOP logs for this call. I only have java error log which i have given below. Please let me know if you need any other information. Can you please check why Refreshtoken got expired. This

Re: Credential could not be refreshed, java client library version v201708

Hello Hari, Your code snippet looks good. To investigate the issue further, could you provide us the logs with complete error message you received with the new refresh token? Thanks, Bharani, AdWords API Team On Wednesday, September 20, 2017 at 8:36:50 AM UTC-4, hari krishna wrote: > > Hi,

Re: Credential could not be refreshed, java client library version v201708

Hi Bharani, If I generate new refresh token it will work fine. But after couple of days it is not working and i need to generate new refresh token to make it work. I am following below link to generate refresh token.

Re: Credential could not be refreshed, java client library version v201708

Hello Hari, Could you try and regenerate the refresh token again by following this guide ? You can refer to the example from the Java client library for generating the

Credential could not be refreshed, java client library version v201708

Hi, We are getting Credential could not be refreshed error occasionally. We are using java client library version v201708. I generated new refreshToken also but that did not work to solve the issue permanently. Can you please help us to resolve this issue permanently. Below is the stack