Hi, 

Maybe it's the same issue for this 
thread<https://groups.google.com/d/msg/adwords-api/aucqEmo0m5w/G1VqAo1NiMkJ>
. 
If it doesn't help the situation, please let me know again.

Best,
- Takeshi

On Thursday, August 22, 2013 6:11:57 AM UTC+9, Mark wrote:
>
> Having used the adwords API for some years and upgraded various versions 
> of the PHP client library including the apility days however, we are having 
> major problems with the migration from v201209 to v201306
>
> Our use is solely to run our own adwords account by automatically changing 
> adverts prices,  adding new adgroups and keyword for new products.
>
> Currently we maintain some 13K + adgroups.
>
> We use the PHP client library as the base of our development for 
> authentication, updating and communication included from within our own 
> scripts which communicate directly with our database servers.
>
> As you can imagine as we have been offline since the sunset of v201209 
> this is now critical.
>
> Currently,  we have downloaded the v201306 php client library and uploaded 
> it to a test area on our server.
>
> We have followed the instructions about getting an OAuth 2.0 refresh_token 
> and that is where we have hit a brick wall.
>
> We have created a client_id and client_secret both of which have been 
> placed into the src/Google/Api/Ads/Adword/auth.ini file.
>
> The next step was to run GetRefreshToken.php
> We have ran this from  [url]/examples/AdWords/Auth/GetRefreshToken.phpand 
> initially ended up with a blank page.
>
>  
> Some debug later and we found that the command:
>
>
> if (__FILE__ != realpath($_SERVER['PHP_SELF'])) { 
>
> return;
> }
>  
> was creating the problem. The realpath command is returning false 
> (something common seamingly as the script running does not have write 
> privilages to the lower level items of the path) and therefore the two 
> values did not match and consequently the script was just stopping without 
> any message hence the white screen.
>  
>
> So we commented out these commands and tried again.   This time we got a 
> little further but still received an error.
>
> Log in to your AdWords account and open the following URL: 
>
> https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=[REMOVED].apps.googleusercontent.com&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&scope=https%3A%2F%2Fadwords.google.com%2Fapi%2Fadwords%2F&access_type=offline
>
> After approving the token enter the authorization code here: 
> Your OAuth2 Credentials are incorrect.
> Please see the GetRefreshToken.php example.
> {
>   "error" : "invalid_request"
> }
>
> Even with the error, we tried to use the url by manually posting it in a 
> browser but that give us an error that the url was incorrect.
>  
> Having trolled through many forum and web posts we are still no further 
> forward as to what could be the problem.
>  
> Any assistance to just get past this first step of getting a refresh_token 
> would be appreciated
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to