I am using google's own sample GetKeywords.php . Every setting in auth.ini
is perfect, checked a zillion times.
--code snippet at bottom ---
{below is shown by print_r($user) ;}
}Printing user
AdWordsUser Object ( [email:AdWordsUser:private] => [myemail]@gmail.com
[password:AdWordsUser:private] => [correctpassword]
[requestHeaderElements:AdsUser:private] => Array ( [authToken] =>
[userAgent] => AwApi-PHP-3.0.0-Freelance Developer [clientEmail] =>
client_1+[myemail]@gmail.com [developerToken] => [myemail]@gmail.com++USD
[applicationToken] => ) [defaultServer:AdsUser:private] =>
https://adwords-sandbox.google.com [defaultVersion:AdsUser:private] =>
v201109 [logsDirectory:AdsUser:private] => /var/www/api/logs
[soapCompression:AdsUser:private] => 1
[soapCompressionLevel:AdsUser:private] => 1 [wsdlCache:AdsUser:private] =>
0 [authServer:AdsUser:private] => https://www.google.com
[oauthInfo:AdsUser:private] => [oauthHandler:AdsUser:private] =>
AndySmithOAuthHandler Object ( ) )
the result is :
{ this is the shown exception }
An error has occurred: Failed to get authToken. Reason: BadAuthentication
---------------this is the code,full file i send in next message, though it
is google's own sample code------------------------
try {
// Get AdWordsUser from credentials in "../auth.ini"
// relative to the AdWordsUser.php file's directory.
$user = new AdWordsUser();
echo "Printing user</br>";
print_r($user);
// Log every SOAP XML request and response.
$user->LogAll();
// Run the example.
GetKeywordsExample($user, $adGroupId);
} catch (Exception $e) {
printf("An error has occurred: %s\n", $e->getMessage());
}
================
On Monday, 19 March 2012 08:28:40 UTC+5:30, dkasak wrote:
>
> I'm not talking about the URL of the downloads in this case.
>
> The page:
> http://code.google.com/apis/adwords/docs/guides/reporting.html
>
> ... used to have an example report definition, which STARTED with the
> line:
>
> <reportDefinition>
>
> ... and this has been changed to:
>
> <reportDefinition xmlns="https://adwords.google.com/api/adwords/cm/v201109";>
> It's difficult to say from the announcement exactly what you're changing
> other than the download URL. This XML namespace change is NOT mentioned in
> the blog post, yet past experience tells me to expect more than what is
> announced, and this is a decent hint that you will start to require this XML
> namespace in the report definition as of the next API hack. Please confirm.
>
> Anyway, the point remains ... if you are looking to improve things, then do
> it in the NEXT API RELEASE, and not the current one.
>
>
>
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
