from:"maxSonic Sun"

Re: Support HD solution image for image ad?

2016-08-10 Thread maxSonic Sun

Hi,

I think this feature is heavily used by most of the adwords customer. So 
will it go into production in the next few months?

On Thursday, August 11, 2016 at 2:50:00 AM UTC+8, Vishal Vinayak (Adwords 
API Team) wrote:
>
> Hi,
>
> We have added this enhancement to the feature request list but we don't 
> yet have a date on when this would go into production. Please follow our 
> blog  for future updates on this 
> feature.  
>
> Regards,
> Vishal, AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/646aaebc-c1ce-4676-b2a6-16f2ad2a6379%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Support HD solution image for image ad?

2016-08-10 Thread maxSonic Sun



Hi,


I tried to create the HD solution image ad for an all feature display 
campaign, but failed.  However, in the UI page of adwords, that is a 
description saying that the HD solution is supported. But in the api 
document, unlike the one in template ads, there is no way to set the 
dimension for HD image. I have asked the support engineer in China for a 
long time, he said that adwords engineer will fix this bug in feature, 
However, there has been 5 months since I asked this question and google is 
not going to fix it? 








 








-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/f5af792e-022c-4fb3-89a4-4fd5f8c5bb43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

anyway to choose ios > 8.0?

2016-08-10 Thread maxSonic Sun

Hi,

According to the adwords 
document 
https://developers.google.com/adwords/api/docs/appendix/mobileplatforms, 
it seems that I can only select ios > 7.0 ? Anyway to choose a larger 
version number?


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/647c6267-88d2-407f-bd85-51b72f2999ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

need to set bidding scheme when using target cpa?

2016-05-20 Thread maxSonic Sun

Hi,

I was trying to set a campaign with params:

{'status': 'PAUSED', 'startDate': '20160520', 'endDate': None, 
'adServingOptimizationStatus': 'CONVERSION_OPTIMIZE', 'frequencyCap': {
'impressions': None, 'level': '', 'timeUnit': ''}, 'networkSetting': {
'targetContentNetwork': True, 'targetPartnerSearchNetwork': False, 
'targetGoogleSearch': False, 'targetSearchNetwork': False}, 
'advertisingChannelType': 'DISPLAY', 'name': 'cpa-install-123_377-0', 
'biddingStrategyConfiguration': {'biddingStrategyType': 'TARGET_CPA'}, 
'budget': {'budgetId': 846619889}, 'advertisingChannelSubType': 
'DISPLAY_MOBILE_APP'}



But always got the response as: 

Server raised fault: '[RequiredError.REQUIRED @ 
operations[0].operand.biddingStrategyConfiguration.biddingScheme]'



as from the document pasted below, I should be able to create the campaign 
without setting any biddingscheme, right?


Best Regards,
Sonic

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/be5f28c3-a4f7-4c98-8328-fcbfd5ba3bcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-03-07 Thread maxSonic Sun

Hi Mark,

Any update?

Best Regards,
Sonic Sun

On Wednesday, February 24, 2016 at 7:27:19 PM UTC+8, maxSonic Sun wrote:
>
> Hi Mark,
>
> Same encoding.
>
> ubuntu@ip-10-0-26-250:~$ echo $LANG
> en_US.UTF-8
>
> Best Regards
> Sonic
>
> On Wednesday, February 24, 2016 at 4:47:30 AM UTC+8, Mark Saniscalchi 
> wrote:
>>
>> Hello Sonic,
>>
>> I can see that you have en_US.utf8 as an available locale, but is it 
>> actually being used? What is the output of echo $LANG? I've reproduced 
>> and resolved your issue by setting the locale to a different value, so I 
>> suspect you might not actually have that set correctly on the VM.
>>
>> I pointed out the logger issue earlier because it appeared in the output 
>> and *was not* related to your case, so I wanted to make that clear. 
>> Sorry if that instead caused any confusion.
>>
>> Regards,
>> Mark
>>
>>
>>
>> On Saturday, February 20, 2016 at 2:14:47 AM UTC-5, maxSonic Sun wrote:
>>>
>>> Hi Mark,
>>>
>>> On my server machine, the locale is
>>> ubuntu@ip-10-0-24-250:~$ locale -a
>>> C
>>> C.UTF-8
>>> en_US.utf8
>>> POSIX
>>>
>>> But I still have the problem. The system I have is ubuntu 14.04 server 
>>> on aws. That should not be the ANSII encoding problem. 
>>> *And by the way, my problem is not caused by the logger as you pointed 
>>> out in the previous post, it is caused by the decoding of the xml. *The 
>>> scenario you pointed out happened nowhere on my machine.
>>>
>>> As you can see, is a SAX parser problem.
>>>
>>>
>>> <https://lh3.googleusercontent.com/-T-0kdzKwXWQ/Vp-ti3ztPcI/A4k/_WvW8uoQeZs/s1600/PastedGraphic-4.png>
>>>
>>>
>>>
>>>
>>>
>>> On Saturday, February 20, 2016 at 12:44:58 AM UTC+8, Mark Saniscalchi 
>>> wrote:
>>>>
>>>> Hello Sonic,
>>>>
>>>> Sorry for the delay. If you look to my initial response, I did run and 
>>>> successfully retrieve an account name containing utf-8 characters using 
>>>> the 
>>>> get_account_hierarchy.py example in v201509 using Python 2. This was on a 
>>>> machine where the default encoding is utf-8. I provided the code above as 
>>>> a 
>>>> potential work-around, but if that still fails to work, I would suggest 
>>>> modifying the default encoding used by your VM to utf-8.
>>>>
>>>> You may recall earlier that I was able to replicate your issue on a VM 
>>>> using ANSII encoding. I was also able to resolve the problem on that VM by 
>>>> modifying the default encoding to utf-8. The suds-jurko library doesn't 
>>>> seem to state this as a requirement, but it doesn't seem to handle utf-8 
>>>> characters well otherwise. Going forward, we'll be suggesting in our 
>>>> documentation that setting the default encoding to utf-8 is a requirement.
>>>>
>>>> Regards,
>>>> Mark
>>>>
>>>> On Friday, February 19, 2016 at 9:42:16 AM UTC-5, maxSonic Sun wrote:
>>>>>
>>>>> Hi Mark, 
>>>>>
>>>>> Any update?
>>>>>
>>>>> Best Regards,
>>>>> Sonic
>>>>>
>>>>> On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi 
>>>>> wrote:
>>>>>>
>>>>>> Hello Sonic,
>>>>>>
>>>>>> That looks correct, so you are using the right version of suds-jurko 
>>>>>> at least.
>>>>>>
>>>>>> On my workstation, I created a campaign with the name that you're 
>>>>>> having issues parsing and ran the get_campaigns.py example. I ran (sort 
>>>>>> of) 
>>>>>> without issues:
>>>>>>
>>>>>> INFO:oauth2client.client:Refreshing access_token
>>>>>>> DEBUG:suds.transport.http:opening (
>>>>>>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl
>>>>>>> )
>>>>>>> DEBUG:suds.transport.http:sending:
>>>>>>> URL: 
>>>>>>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>>>>>>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>>>>>>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset

Re: not able to choose the ExplorerAutoOptimizerSetting in the ui of mobile app install ads' adgroup.

2016-03-01 Thread maxSonic Sun

Hi Nadine,

I tried CONVERSION_OPTIMIZER according to this 
article 
https://developers.google.com/adwords/api/docs/guides/driving-mobile-app-downloads.
 
But fail again with the *Targeting Optimization* check box disappeared.
I 
read 
https://developers.google.com/adwords/api/docs/reference/v201509/CampaignService.BiddingStrategyConfiguration?hl=zh-cn,
 
I think there is no other option could be set for the mobile app install 
ads.

Best Regards,
Sonic Sun

On Wednesday, March 2, 2016 at 7:20:42 AM UTC+8, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Greetings Sonic Sun!
>
> Are you talking about the *Targeting Optimization* check box that isn't 
> appearing? The reason that's not appearing is because there's a difference 
> in your bidding strategy for the two ad groups.  At the top of the first 
> screenshot, I can see that your bidding strategy is *Target CPA 
> (conversions)*. In the later screenshots showing the API created ad 
> group, the bidding strategy is *Max CPC*. By default, a new campaign 
> cannot do *Target CPA* because there needs to be conversions already in 
> the system for it to take effect. This difference in bidding strategy means 
> that the check box won't be there until there are enough click to allow you 
> to convert that ad group over to CPA rather than CPC. Check out our Bidding 
> guide <https://developers.google.com/adwords/api/docs/guides/bidding> for 
> a more in-depth explanation of how CPC versus CPA works in the API.
>
> Best,
> Nadine, AdWords API Team
>
> On Tuesday, March 1, 2016 at 3:23:54 AM UTC-5, maxSonic Sun wrote:
>>
>> Hi,
>>
>> I think this is a problem between the api and the ui of the adwords, why 
>> should I ask this question on the Community Forum? It should not be an api 
>> bug?
>>
>> BRs,
>> Sonic Sun
>>
>> On Tuesday, March 1, 2016 at 1:18:01 AM UTC+8, Anthony Madrigal wrote:
>>>
>>> Hello,
>>>
>>> Since you are unable to select the ExplorerAutoOptimizerSetting in the 
>>> UI, I recommend asking your question on the AdWords Community Forum 
>>> <https://www.en.advertisercommunity.com/t5/Google-AdWords/ct-p/Google_AdWords>.
>>>  
>>> They should be the best suited to help you. 
>>>
>>> Regards,
>>> Anthony
>>> AdWords API Team
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/2bffa9b2-75be-4e02-aed4-1fc2ff3738c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: not able to choose the ExplorerAutoOptimizerSetting in the ui of mobile app install ads' adgroup.

2016-03-01 Thread maxSonic Sun

Hi,

I think this is a problem between the api and the ui of the adwords, why 
should I ask this question on the Community Forum? It should not be an api 
bug?

BRs,
Sonic Sun

On Tuesday, March 1, 2016 at 1:18:01 AM UTC+8, Anthony Madrigal wrote:
>
> Hello,
>
> Since you are unable to select the ExplorerAutoOptimizerSetting in the UI, 
> I recommend asking your question on the AdWords Community Forum 
> .
>  
> They should be the best suited to help you. 
>
> Regards,
> Anthony
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/398e0055-85f2-454a-b48b-a1803d1832c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

not able to choose the ExplorerAutoOptimizerSetting in the ui of mobile app install ads' adgroup.

2016-02-29 Thread maxSonic Sun

Hi All,

I use the sample code form the googleads-python-lib to create the moble app 
install ads, but I am not able to choose the below option after the adgroup 
is created.







This is the the adgroup created by the api, please notice that the option 
is not available and the type is not aggressive:




This is the adgroup created with ExplorerAutoOptimizerSetting as true, 
however, this option could not be check off after setting it to true in the 
api.  please notice that the option is not available and the type *is *
aggressive




Below is the code.

import uuid

from googleads import adwords
import datetime


CAMPAIGN_ID = 'INSERT_CAMPAIGN_ID_HERE'

def make_campaign(client):
# Initialize appropriate services.
campaign_service = client.GetService('CampaignService', 
version='v201601')
budget_service = client.GetService('BudgetService', version='v201601')
  
# Create a budget, which can be shared by multiple campaigns.
budget = {
'name': 'Interplanetary budget #%s' % uuid.uuid4(),
'amount': {
'microAmount': '5000'
},
'deliveryMethod': 'STANDARD',
'period': 'DAILY'
}
  
budget_operations = [{
'operator': 'ADD',
'operand': budget
}]
  
# Add the budget.
budget_id = budget_service.mutate(budget_operations)['value'][0][
'budgetId']
  
# Construct operations and add campaigns.
operations = [{
  'operator': 'ADD',
  'operand': {
  'name': 'Interplanetary Cruise #%s' % uuid.uuid4(),
  'status': 'PAUSED',
  'advertisingChannelType': 'DISPLAY',
  'biddingStrategyConfiguration': {
  'biddingStrategyType': 'MANUAL_CPC',
  },
  'endDate': (datetime.datetime.now() +
  datetime.timedelta(365)).strftime('%Y%m%d'),
  # Note that only the budgetId is required
  'budget': {
  'budgetId': budget_id
  },
  'advertisingChannelSubType': 'DISPLAY_MOBILE_APP',
  # Optional fields
  'startDate': (datetime.datetime.now() +
datetime.timedelta(1)).strftime('%Y%m%d'),
  'adServingOptimizationStatus': 'ROTATE',
  'frequencyCap': {
  'impressions': '5',
  'timeUnit': 'DAY',
  'level': 'ADGROUP'
  },
  'settings': [
  {
  'xsi_type': 'GeoTargetTypeSetting',
  'positiveGeoTargetType': 'DONT_CARE',
  'negativeGeoTargetType': 'DONT_CARE'
  }
  ]}}]
campaigns = campaign_service.mutate(operations)

# Display results.
for campaign in campaigns['value']:
  print ('Campaign with name \'%s\' and id \'%s\' was added.'
 % (campaign['name'], campaign['id']))
  return campaign['id']
  

def main(client, campaign_id):
  # Initialize appropriate service.
  ad_group_service = client.GetService('AdGroupService', version='v201601')

  # Construct operations and add ad groups.
  operations = [{
  'operator': 'ADD',
  'operand': {
  'campaignId': campaign_id,
  'name': 'Earth to Mars Cruises #%s' % uuid.uuid4(),
  'status': 'ENABLED',
  'biddingStrategyConfiguration': {
  'bids': [
  {
  'xsi_type': 'CpaBid',
  'bid': {
  'microAmount': '100'
  },
  }
  ]
  },
  'settings': [
  {
  # Targeting restriction settings. Depending on the
  # criterionTypeGroup value, most TargetingSettingDetail 
only
  # affect Display campaigns. However, the
  # USER_INTEREST_AND_LIST value works for RLSA campaigns -
  # Search campaigns targeting using a remarketing list.

not able to choose the

2016-02-29 Thread maxSonic Sun

Hi All,

I use the sample code form the googleads-python-lib to create the moble app 
install ads, but I am not able to choose the below option after the adgroup 
is created.







This is the the adgroup created by the api, please notice that the option 
is not available and the type is not aggressive:




This is the adgroup created with ExplorerAutoOptimizerSetting as true, 
however, this option could not be check off after setting it to true in the 
api.  please notice that the option is not available and the type *is *
aggressive




Below is the code.

import uuid

from googleads import adwords
import datetime


CAMPAIGN_ID = 'INSERT_CAMPAIGN_ID_HERE'

def make_campaign(client):
# Initialize appropriate services.
campaign_service = client.GetService('CampaignService', 
version='v201601')
budget_service = client.GetService('BudgetService', version='v201601')
  
# Create a budget, which can be shared by multiple campaigns.
budget = {
'name': 'Interplanetary budget #%s' % uuid.uuid4(),
'amount': {
'microAmount': '5000'
},
'deliveryMethod': 'STANDARD',
'period': 'DAILY'
}
  
budget_operations = [{
'operator': 'ADD',
'operand': budget
}]
  
# Add the budget.
budget_id = budget_service.mutate(budget_operations)['value'][0][
'budgetId']
  
# Construct operations and add campaigns.
operations = [{
  'operator': 'ADD',
  'operand': {
  'name': 'Interplanetary Cruise #%s' % uuid.uuid4(),
  'status': 'PAUSED',
  'advertisingChannelType': 'DISPLAY',
  'biddingStrategyConfiguration': {
  'biddingStrategyType': 'MANUAL_CPC',
  },
  'endDate': (datetime.datetime.now() +
  datetime.timedelta(365)).strftime('%Y%m%d'),
  # Note that only the budgetId is required
  'budget': {
  'budgetId': budget_id
  },
  'advertisingChannelSubType': 'DISPLAY_MOBILE_APP',
  # Optional fields
  'startDate': (datetime.datetime.now() +
datetime.timedelta(1)).strftime('%Y%m%d'),
  'adServingOptimizationStatus': 'ROTATE',
  'frequencyCap': {
  'impressions': '5',
  'timeUnit': 'DAY',
  'level': 'ADGROUP'
  },
  'settings': [
  {
  'xsi_type': 'GeoTargetTypeSetting',
  'positiveGeoTargetType': 'DONT_CARE',
  'negativeGeoTargetType': 'DONT_CARE'
  }
  ]}}]
campaigns = campaign_service.mutate(operations)

# Display results.
for campaign in campaigns['value']:
  print ('Campaign with name \'%s\' and id \'%s\' was added.'
 % (campaign['name'], campaign['id']))
  return campaign['id']
  

def main(client, campaign_id):
  # Initialize appropriate service.
  ad_group_service = client.GetService('AdGroupService', version='v201601')

  # Construct operations and add ad groups.
  operations = [{
  'operator': 'ADD',
  'operand': {
  'campaignId': campaign_id,
  'name': 'Earth to Mars Cruises #%s' % uuid.uuid4(),
  'status': 'ENABLED',
  'biddingStrategyConfiguration': {
  'bids': [
  {
  'xsi_type': 'CpaBid',
  'bid': {
  'microAmount': '100'
  },
  }
  ]
  },
  'settings': [
  {
  # Targeting restriction settings. Depending on the
  # criterionTypeGroup value, most TargetingSettingDetail 
only
  # affect Display campaigns. However, the
  # USER_INTEREST_AND_LIST value works for RLSA campaigns -
  # Search campaigns targeting using a remarketing list.

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-02-24 Thread maxSonic Sun

Hi Mark,

Same encoding.

ubuntu@ip-10-0-26-250:~$ echo $LANG
en_US.UTF-8

Best Regards
Sonic

On Wednesday, February 24, 2016 at 4:47:30 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> I can see that you have en_US.utf8 as an available locale, but is it 
> actually being used? What is the output of echo $LANG? I've reproduced 
> and resolved your issue by setting the locale to a different value, so I 
> suspect you might not actually have that set correctly on the VM.
>
> I pointed out the logger issue earlier because it appeared in the output 
> and *was not* related to your case, so I wanted to make that clear. Sorry 
> if that instead caused any confusion.
>
> Regards,
> Mark
>
>
>
> On Saturday, February 20, 2016 at 2:14:47 AM UTC-5, maxSonic Sun wrote:
>>
>> Hi Mark,
>>
>> On my server machine, the locale is
>> ubuntu@ip-10-0-24-250:~$ locale -a
>> C
>> C.UTF-8
>> en_US.utf8
>> POSIX
>>
>> But I still have the problem. The system I have is ubuntu 14.04 server on 
>> aws. That should not be the ANSII encoding problem. 
>> *And by the way, my problem is not caused by the logger as you pointed 
>> out in the previous post, it is caused by the decoding of the xml. *The 
>> scenario you pointed out happened nowhere on my machine.
>>
>> As you can see, is a SAX parser problem.
>>
>>
>> <https://lh3.googleusercontent.com/-T-0kdzKwXWQ/Vp-ti3ztPcI/A4k/_WvW8uoQeZs/s1600/PastedGraphic-4.png>
>>
>>
>>
>>
>>
>> On Saturday, February 20, 2016 at 12:44:58 AM UTC+8, Mark Saniscalchi 
>> wrote:
>>>
>>> Hello Sonic,
>>>
>>> Sorry for the delay. If you look to my initial response, I did run and 
>>> successfully retrieve an account name containing utf-8 characters using the 
>>> get_account_hierarchy.py example in v201509 using Python 2. This was on a 
>>> machine where the default encoding is utf-8. I provided the code above as a 
>>> potential work-around, but if that still fails to work, I would suggest 
>>> modifying the default encoding used by your VM to utf-8.
>>>
>>> You may recall earlier that I was able to replicate your issue on a VM 
>>> using ANSII encoding. I was also able to resolve the problem on that VM by 
>>> modifying the default encoding to utf-8. The suds-jurko library doesn't 
>>> seem to state this as a requirement, but it doesn't seem to handle utf-8 
>>> characters well otherwise. Going forward, we'll be suggesting in our 
>>> documentation that setting the default encoding to utf-8 is a requirement.
>>>
>>> Regards,
>>> Mark
>>>
>>> On Friday, February 19, 2016 at 9:42:16 AM UTC-5, maxSonic Sun wrote:
>>>>
>>>> Hi Mark, 
>>>>
>>>> Any update?
>>>>
>>>> Best Regards,
>>>> Sonic
>>>>
>>>> On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi 
>>>> wrote:
>>>>>
>>>>> Hello Sonic,
>>>>>
>>>>> That looks correct, so you are using the right version of suds-jurko 
>>>>> at least.
>>>>>
>>>>> On my workstation, I created a campaign with the name that you're 
>>>>> having issues parsing and ran the get_campaigns.py example. I ran (sort 
>>>>> of) 
>>>>> without issues:
>>>>>
>>>>> INFO:oauth2client.client:Refreshing access_token
>>>>>> DEBUG:suds.transport.http:opening (
>>>>>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl
>>>>>> )
>>>>>> DEBUG:suds.transport.http:sending:
>>>>>> URL: 
>>>>>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>>>>>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>>>>>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
>>>>>> 'Authorization': u'REDACTED'}
>>>>>> MESSAGE:
>>>>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>>>>>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
>>>>>> http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
>>>>>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
>>>>>> http://schemas.xmlsoap.org/soap/envelope/
>>>>>> ">REDACTEDREDACTEDREDACTEDfalsefalseIdNam

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-02-19 Thread maxSonic Sun

Hi Mark,

On my server machine, the locale is
ubuntu@ip-10-0-24-250:~$ locale -a
C
C.UTF-8
en_US.utf8
POSIX

But I still have the problem. The system I have is ubuntu 14.04 server on 
aws. That should not be the ANSII encoding problem. 
*And by the way, my problem is not caused by the logger as you pointed out 
in the previous post, it is caused by the decoding of the xml. *The 
scenario you pointed out happened nowhere on my machine.

As you can see, is a SAX parser problem.

<https://lh3.googleusercontent.com/-T-0kdzKwXWQ/Vp-ti3ztPcI/A4k/_WvW8uoQeZs/s1600/PastedGraphic-4.png>





On Saturday, February 20, 2016 at 12:44:58 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> Sorry for the delay. If you look to my initial response, I did run and 
> successfully retrieve an account name containing utf-8 characters using the 
> get_account_hierarchy.py example in v201509 using Python 2. This was on a 
> machine where the default encoding is utf-8. I provided the code above as a 
> potential work-around, but if that still fails to work, I would suggest 
> modifying the default encoding used by your VM to utf-8.
>
> You may recall earlier that I was able to replicate your issue on a VM 
> using ANSII encoding. I was also able to resolve the problem on that VM by 
> modifying the default encoding to utf-8. The suds-jurko library doesn't 
> seem to state this as a requirement, but it doesn't seem to handle utf-8 
> characters well otherwise. Going forward, we'll be suggesting in our 
> documentation that setting the default encoding to utf-8 is a requirement.
>
> Regards,
> Mark
>
> On Friday, February 19, 2016 at 9:42:16 AM UTC-5, maxSonic Sun wrote:
>>
>> Hi Mark, 
>>
>> Any update?
>>
>> Best Regards,
>> Sonic
>>
>> On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi wrote:
>>>
>>> Hello Sonic,
>>>
>>> That looks correct, so you are using the right version of suds-jurko at 
>>> least.
>>>
>>> On my workstation, I created a campaign with the name that you're having 
>>> issues parsing and ran the get_campaigns.py example. I ran (sort of) 
>>> without issues:
>>>
>>> INFO:oauth2client.client:Refreshing access_token
>>>> DEBUG:suds.transport.http:opening (
>>>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl)
>>>> DEBUG:suds.transport.http:sending:
>>>> URL: https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>>>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>>>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
>>>> 'Authorization': u'REDACTED'}
>>>> MESSAGE:
>>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>>>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
>>>> http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
>>>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
>>>> http://schemas.xmlsoap.org/soap/envelope/
>>>> ">REDACTEDREDACTEDREDACTEDfalsefalseIdNameStatus0100
>>>> Traceback (most recent call last):
>>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 859, in emit
>>>> msg = self.format(record)
>>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 732, in 
>>>> format
>>>> return fmt.format(record)
>>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 471, in 
>>>> format
>>>> record.message = record.getMessage()
>>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 335, in 
>>>> getMessage
>>>> msg = msg % self.args
>>>>   File "/usr/local/lib/python2.7/dist-packages/suds/__init__.py", line 
>>>> 168, in 
>>>> __str__ = lambda x: unicode(x).encode('utf-8')
>>>>   File 
>>>> "/usr/local/lib/python2.7/dist-packages/suds/transport/__init__.py", line 
>>>> 96, in __unicode__
>>>> %s""" % (self.code, self.headers, self.message)
>>>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 
>>>> 577: ordinal not in range(128)
>>>> Logged from file http.py, line 89
>>>> Campaign with id '374649914', name '15-abc-1-mmep-中国－IOS', and status 
>>>> 'ENABLED' was found.
>>>
>>>
>>> The error you're seeing there is a known issue that the suds logger has 
>>

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-02-19 Thread maxSonic Sun

Hi Mark, 

Any update?

Best Regards,
Sonic

On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> That looks correct, so you are using the right version of suds-jurko at 
> least.
>
> On my workstation, I created a campaign with the name that you're having 
> issues parsing and ran the get_campaigns.py example. I ran (sort of) 
> without issues:
>
> INFO:oauth2client.client:Refreshing access_token
>> DEBUG:suds.transport.http:opening (
>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl)
>> DEBUG:suds.transport.http:sending:
>> URL: https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
>> 'Authorization': u'REDACTED'}
>> MESSAGE:
>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
>> http://schemas.xmlsoap.org/soap/envelope/
>> ">REDACTEDREDACTEDREDACTEDfalsefalseIdNameStatus0100
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 859, in emit
>> msg = self.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 732, in format
>> return fmt.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 471, in format
>> record.message = record.getMessage()
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 335, in 
>> getMessage
>> msg = msg % self.args
>>   File "/usr/local/lib/python2.7/dist-packages/suds/__init__.py", line 
>> 168, in 
>> __str__ = lambda x: unicode(x).encode('utf-8')
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/suds/transport/__init__.py", line 
>> 96, in __unicode__
>> %s""" % (self.code, self.headers, self.message)
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 577: 
>> ordinal not in range(128)
>> Logged from file http.py, line 89
>> Campaign with id '374649914', name '15-abc-1-mmep-中国－IOS', and status 
>> 'ENABLED' was found.
>
>
> The error you're seeing there is a known issue that the suds logger has 
> with unicode characters, but it doesn't prevent the sample from completing. 
> As you can see, the Campaign's name can be retrieved and printed without 
> issues. This definitely seems like an issue specific to the environment the 
> code is run on. I went a step further and ran this on a separate VM 
> instance, and was able to reproduce it in that case.
>
> The workstation has its default character encoding set to utf-8 and the VM 
> has it set to ANSIX3.4-1968, which is probably related. I think suds might 
> have some flaky behavior here depending on the environment used. In the 
> meantime, you can avoid this error by encoding the output of string fields 
> such as:
>
> # Display results.
> if 'entries' in page:
>   for campaign in page['entries']:
> print ('Campaign with id \'%s\', name \'%s\', and status \'%s\' 
> was '
>'found.' % (campaign['id'], 
> campaign['name'].encode('utf-8'),
>campaign['status'].encode('utf-8')))
>
> I'll continue investigating this, as a better fix may need to come 
> upstream from the suds library.
>
> Regards,
> Mark
>
> On Monday, February 1, 2016 at 9:12:24 PM UTC-5, maxSonic Sun wrote:
>>
>> Hi Mark,
>>
>> Here is the version:
>> __version__ = "0.6"
>> __build__ = ""
>>
>> Best Regards
>> Sonic Sun
>>
>> On Monday, February 1, 2016 at 11:32:44 PM UTC+8, Mark Saniscalchi wrote:
>>>
>>> Hello Sonic,
>>>
>>> I'd just like to confirm, could you tell me what the version number is 
>>> in the following file:
>>>
>>>
>>> /project/apiservice/venvdocker/local/lib/python2.7/site-packages/suds/version.py
>>>
>>> Thanks,
>>> Mark
>>>
>>>
>>> On Monday, February 1, 2016 at 2:51:27 AM UTC-5, maxSonic Sun wrote:
>>>>
>>>> Hi,
>>>>
>>>> There is something weird here, I am able to parsed some other unicode 
>>>> characters and also other accounts of my customer. I have listed all the 
>>&g

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-02-10 Thread maxSonic Sun

Hi Mark,

I have tried and it seems that the code will not run into the suds client :(
In the code below, the graph will always be {}, leaving no way to have any 
content in it. And the error message is ":1:29168: not well-formed 
(invalid token)", I think this message is from the xml parsing part, not 
the logger.
graph = dict()
try:
graph = customer_service.get(selector)
except Exception as e:
print str(e)

I tried to print the xml by using the MessagePlugin's receive method and 
the xml could be printed without error. And I tried to encode and decode it 
into utf-8, it was fine in the receive method, but outside that method, the 
error message occurred, i.e ":1:29168: not well-formed (invalid 
token)".
After debugging for a while, it turned out that it may be the problem of 
suds, however, as I have the same problem with the java client, I think 
that the SOAP XML from google may contain some illegal thing.

I have noticed that you are using the campaign service, could you use the 
ManageCustomerService, though I cannot see the code from google side, I 
suspect that there is a problem with the generation for the customer 
service xml. The code example 
is 
https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201509/account_management/get_account_hierarchy.py

Best Regards,
Sonic Sun

On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> That looks correct, so you are using the right version of suds-jurko at 
> least.
>
> On my workstation, I created a campaign with the name that you're having 
> issues parsing and ran the get_campaigns.py example. I ran (sort of) 
> without issues:
>
> INFO:oauth2client.client:Refreshing access_token
>> DEBUG:suds.transport.http:opening (
>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl)
>> DEBUG:suds.transport.http:sending:
>> URL: https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
>> 'Authorization': u'REDACTED'}
>> MESSAGE:
>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
>> http://schemas.xmlsoap.org/soap/envelope/
>> ">REDACTEDREDACTEDREDACTEDfalsefalseIdNameStatus0100
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 859, in emit
>> msg = self.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 732, in format
>> return fmt.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 471, in format
>> record.message = record.getMessage()
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 335, in 
>> getMessage
>> msg = msg % self.args
>>   File "/usr/local/lib/python2.7/dist-packages/suds/__init__.py", line 
>> 168, in 
>> __str__ = lambda x: unicode(x).encode('utf-8')
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/suds/transport/__init__.py", line 
>> 96, in __unicode__
>> %s""" % (self.code, self.headers, self.message)
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 577: 
>> ordinal not in range(128)
>> Logged from file http.py, line 89
>> Campaign with id '374649914', name '15-abc-1-mmep-中国－IOS', and status 
>> 'ENABLED' was found.
>
>
> The error you're seeing there is a known issue that the suds logger has 
> with unicode characters, but it doesn't prevent the sample from completing. 
> As you can see, the Campaign's name can be retrieved and printed without 
> issues. This definitely seems like an issue specific to the environment the 
> code is run on. I went a step further and ran this on a separate VM 
> instance, and was able to reproduce it in that case.
>
> The workstation has its default character encoding set to utf-8 and the VM 
> has it set to ANSIX3.4-1968, which is probably related. I think suds might 
> have some flaky behavior here depending on the environment used. In the 
> meantime, you can avoid this error by encoding the output of string fields 
> such as:
>
> # Display results.
> if 'entries' in page:
>   for campaign in page['entries']:
> print ('Campaign with id \'%s\', name \'%s\', and status \'%s\' 
> was '
>

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-02-09 Thread maxSonic Sun

Hi Mark,

Thanks for your reply :)

I will try your solution to walk around the issue. Will report to you if I 
encounter any other problem.

Best Regards,
Sonic Sun

On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> That looks correct, so you are using the right version of suds-jurko at 
> least.
>
> On my workstation, I created a campaign with the name that you're having 
> issues parsing and ran the get_campaigns.py example. I ran (sort of) 
> without issues:
>
> INFO:oauth2client.client:Refreshing access_token
>> DEBUG:suds.transport.http:opening (
>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl)
>> DEBUG:suds.transport.http:sending:
>> URL: https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
>> 'Authorization': u'REDACTED'}
>> MESSAGE:
>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
>> http://schemas.xmlsoap.org/soap/envelope/
>> ">REDACTEDREDACTEDREDACTEDfalsefalseIdNameStatus0100
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 859, in emit
>> msg = self.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 732, in format
>> return fmt.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 471, in format
>> record.message = record.getMessage()
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 335, in 
>> getMessage
>> msg = msg % self.args
>>   File "/usr/local/lib/python2.7/dist-packages/suds/__init__.py", line 
>> 168, in 
>> __str__ = lambda x: unicode(x).encode('utf-8')
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/suds/transport/__init__.py", line 
>> 96, in __unicode__
>> %s""" % (self.code, self.headers, self.message)
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 577: 
>> ordinal not in range(128)
>> Logged from file http.py, line 89
>> Campaign with id '374649914', name '15-abc-1-mmep-中国－IOS', and status 
>> 'ENABLED' was found.
>
>
> The error you're seeing there is a known issue that the suds logger has 
> with unicode characters, but it doesn't prevent the sample from completing. 
> As you can see, the Campaign's name can be retrieved and printed without 
> issues. This definitely seems like an issue specific to the environment the 
> code is run on. I went a step further and ran this on a separate VM 
> instance, and was able to reproduce it in that case.
>
> The workstation has its default character encoding set to utf-8 and the VM 
> has it set to ANSIX3.4-1968, which is probably related. I think suds might 
> have some flaky behavior here depending on the environment used. In the 
> meantime, you can avoid this error by encoding the output of string fields 
> such as:
>
> # Display results.
> if 'entries' in page:
>   for campaign in page['entries']:
> print ('Campaign with id \'%s\', name \'%s\', and status \'%s\' 
> was '
>'found.' % (campaign['id'], 
> campaign['name'].encode('utf-8'),
>campaign['status'].encode('utf-8')))
>
> I'll continue investigating this, as a better fix may need to come 
> upstream from the suds library.
>
> Regards,
> Mark
>
> On Monday, February 1, 2016 at 9:12:24 PM UTC-5, maxSonic Sun wrote:
>>
>> Hi Mark,
>>
>> Here is the version:
>> __version__ = "0.6"
>> __build__ = ""
>>
>> Best Regards
>> Sonic Sun
>>
>> On Monday, February 1, 2016 at 11:32:44 PM UTC+8, Mark Saniscalchi wrote:
>>>
>>> Hello Sonic,
>>>
>>> I'd just like to confirm, could you tell me what the version number is 
>>> in the following file:
>>>
>>>
>>> /project/apiservice/venvdocker/local/lib/python2.7/site-packages/suds/version.py
>>>
>>> Thanks,
>>> Mark
>>>
>>>
>>> On Monday, February 1, 2016 at 2:51:27 AM UTC-5, maxSonic Sun wrote:
>>>>
>>>> Hi,
>>>>
>>>> There is something weird here, I am able to parsed some other

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-02-01 Thread maxSonic Sun

Hi Mark,

Here is the version:
__version__ = "0.6"
__build__ = ""

Best Regards
Sonic Sun

On Monday, February 1, 2016 at 11:32:44 PM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> I'd just like to confirm, could you tell me what the version number is in 
> the following file:
>
>
> /project/apiservice/venvdocker/local/lib/python2.7/site-packages/suds/version.py
>
> Thanks,
> Mark
>
>
> On Monday, February 1, 2016 at 2:51:27 AM UTC-5, maxSonic Sun wrote:
>>
>> Hi,
>>
>> There is something weird here, I am able to parsed some other unicode 
>> characters and also other accounts of my customer. I have listed all the 
>> pip lib in my machine, I think I have installed all the lib correctly. By 
>> the way, I didn't change any of the import in the py file, how can it be 
>> changed to other libs if I do nothing in the lib?
>>
>> This issue is also happened in the Java lib for the same account of our 
>> customer.
>>
>> After some debugging, it seems like there will be noway to parsed the id 
>> like: 15-abc-1-mmep-中国－IOS. Please notice that the － is different from -.
>>
>> Best Regards,
>> Sonic Sun
>>
>> On Friday, January 22, 2016 at 4:39:42 AM UTC+8, Mark Saniscalchi wrote:
>>>
>>> Hello,
>>>
>>> We aren't able to replicate this issue with account names containing 
>>> unicode characters. In my case, I ran the get_account_hierarchy.py 
>>> <https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201509/account_management/get_account_hierarchy.py>
>>>  
>>> sample and got the expected result:
>>>
>>> CustomerId, Name
>>> --Redacted, マーク Test Account
>>>
>>> I think this might have to do with something else. In the stacktrace, I 
>>> noticed that you aren't using the sax parser embedded in the suds-jurko 
>>> library. On even closer observation, I noticed that you weren't even using 
>>> the suds-jurko library. This is almost definitely the cause of the problem, 
>>> as I don't think our library is compatible with the original suds library, 
>>> which is now woefully unmaintained. I suggest uninstalling both googleads 
>>> and the suds library you're using currently. Then reinstall googleads with 
>>> pip using the following command:
>>>
>>> pip install googleads
>>>
>>> Our setup.py file should then install all of the necessary dependencies 
>>> automatically, which should resolve this problem.
>>>
>>> Regards,
>>> Mark Saniscalchi
>>>
>>> On Wednesday, January 20, 2016 at 2:22:09 PM UTC-5, maxSonic Sun wrote:
>>>>
>>>> Hi,
>>>>
>>>> I have the error as shown in the first pic below. It seems that it is 
>>>> caused by the decoding of the soap xm. The second pic  is my code. 
>>>> However, 
>>>> if I remove the "name" from the selector, everything works fine.
>>>> My customers have lots of Chinese Name in their MCC accounts. I think 
>>>> it is caused by the unicode problem of python and both the Chinese. How 
>>>> can 
>>>> I solve this problem to avoid this kind of error?
>>>>
>>>>
>>>>
>>>> <https://lh3.googleusercontent.com/-T-0kdzKwXWQ/Vp-ti3ztPcI/A4k/_WvW8uoQeZs/s1600/PastedGraphic-4.png>
>>>>
>>>>
>>>> <https://lh3.googleusercontent.com/-lWDEJ7LLcPc/Vp-tlw4VxyI/A4s/5DkEn5oey7E/s1600/PastedGraphic-6.png>
>>>>
>>>>
>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/98fd9d99-4d64-40e6-ad03-0486f237eb38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SOAP XML error for Chinese Names in ManagedCustomerService

2016-01-31 Thread maxSonic Sun

Hi,

There is something weird here, I am able to parsed some other unicode 
characters and also other accounts of my customer. I have listed all the 
pip lib in my machine, I think I have installed all the lib correctly. By 
the way, I didn't change any of the import in the py file, how can it be 
changed to other libs if I do nothing in the lib?

This issue is also happened in the Java lib for the same account of our 
customer.

After some debugging, it seems like there will be noway to parsed the id 
like: 15-abc-1-mmep-中国－IOS. Please notice that the － is different from -.

Best Regards,
Sonic Sun

On Friday, January 22, 2016 at 4:39:42 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello,
>
> We aren't able to replicate this issue with account names containing 
> unicode characters. In my case, I ran the get_account_hierarchy.py 
> <https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201509/account_management/get_account_hierarchy.py>
>  
> sample and got the expected result:
>
> CustomerId, Name
> --Redacted, マーク Test Account
>
> I think this might have to do with something else. In the stacktrace, I 
> noticed that you aren't using the sax parser embedded in the suds-jurko 
> library. On even closer observation, I noticed that you weren't even using 
> the suds-jurko library. This is almost definitely the cause of the problem, 
> as I don't think our library is compatible with the original suds library, 
> which is now woefully unmaintained. I suggest uninstalling both googleads 
> and the suds library you're using currently. Then reinstall googleads with 
> pip using the following command:
>
> pip install googleads
>
> Our setup.py file should then install all of the necessary dependencies 
> automatically, which should resolve this problem.
>
> Regards,
> Mark Saniscalchi
>
> On Wednesday, January 20, 2016 at 2:22:09 PM UTC-5, maxSonic Sun wrote:
>>
>> Hi,
>>
>> I have the error as shown in the first pic below. It seems that it is 
>> caused by the decoding of the soap xm. The second pic  is my code. However, 
>> if I remove the "name" from the selector, everything works fine.
>> My customers have lots of Chinese Name in their MCC accounts. I think it 
>> is caused by the unicode problem of python and both the Chinese. How can I 
>> solve this problem to avoid this kind of error?
>>
>>
>>
>> <https://lh3.googleusercontent.com/-T-0kdzKwXWQ/Vp-ti3ztPcI/A4k/_WvW8uoQeZs/s1600/PastedGraphic-4.png>
>>
>>
>> <https://lh3.googleusercontent.com/-lWDEJ7LLcPc/Vp-tlw4VxyI/A4s/5DkEn5oey7E/s1600/PastedGraphic-6.png>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/0881767e-5b09-442c-aabd-c1daee6e5574%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

SOAP XML error for Chinese Names in ManagedCustomerService

2016-01-20 Thread maxSonic Sun

Hi,

I have the error as shown in the first pic below. It seems that it is 
caused by the decoding of the soap xm. The second pic  is my code. However, 
if I remove the "name" from the selector, everything works fine.
My customers have lots of Chinese Name in their MCC accounts. I think it is 
caused by the unicode problem of python and both the Chinese. How can I 
solve this problem to avoid this kind of error?







-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/8313467a-45d2-4274-94ba-59faa3a08647%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Support HD solution image for image ad?

Support HD solution image for image ad?

anyway to choose ios > 8.0?

need to set bidding scheme when using target cpa?

Re: SOAP XML error for Chinese Names in ManagedCustomerService

Re: not able to choose the ExplorerAutoOptimizerSetting in the ui of mobile app install ads' adgroup.

Re: not able to choose the ExplorerAutoOptimizerSetting in the ui of mobile app install ads' adgroup.

not able to choose the ExplorerAutoOptimizerSetting in the ui of mobile app install ads' adgroup.

not able to choose the

Re: SOAP XML error for Chinese Names in ManagedCustomerService

Re: SOAP XML error for Chinese Names in ManagedCustomerService

Re: SOAP XML error for Chinese Names in ManagedCustomerService

Re: SOAP XML error for Chinese Names in ManagedCustomerService

Re: SOAP XML error for Chinese Names in ManagedCustomerService

Re: SOAP XML error for Chinese Names in ManagedCustomerService

Re: SOAP XML error for Chinese Names in ManagedCustomerService

SOAP XML error for Chinese Names in ManagedCustomerService

17 matches

Site Navigation

Mail list logo

Footer information