Closed manjunath-nm89 closed 9 years ago
We've seen the same thing when upgrading to 10.0
@banderson623 what did you guys do ? Did you guys move to a older version of the dfp-api and use older version of the DFP API ?
Hey all,
Was ads-common also updated? Not that I think this is the root cause since it gets past that point (and since gem install should update both), but there was very much a misspelling in ads_common that likely would've broken this as well.
Just want to do a sanity check on what version that's using.
@manjunath-nm89 We didn't upgrade ours either, we just stayed with and older version.
@nicholaschen Yes ads-common was also updated, but let me take a look again with this fix misspelling.
@nicholaschen I'm very sure it is not the issue with the misspelling as we are using the fixed version of google-ads-common.
@banderson623 you need to upgrade soon as the dfp api will no longer support v201405 as of Aug 31st, 2015. Can you please tell me what dfp-api gem version you are using and the API version you are currently on.
I tried older versions of google-dfp-api as well like 0.9.3 which supports DFP API v201411 and ran into the same issue.
We are using service_account to impersonate and we heavily rely on it.
Can you please help me to resolve this issue before Aug 31st.
Interesting, so an older version of the gem - with no code changes - just stops working? Even now if you're using v201405?
(mind starting a thread on our api forum here: https://groups.google.com/forum/#!forum/google-doubleclick-for-publishers-api so I can track this?)
As another point, we changed the scope for the DFP API back in v201408 to https://www.googleapis.com/auth/dfp
you might want to check that you've updated this.
Awesome. I missed that. That worked. Thanks !
I upgraded to google-dfp-api v0.10.1 as the DFP API version v201405 will no longer be supported.
I use OAuth2 Service Account authentication scheme. After the upgrade, the only change which I did was change the constant OAuth2_JWT to OAUTH2_SERVICE_ACCOUNT in the dfp_api.yml file.
I deployed to my staging environment, and I ran the following.
I got this
I ensured in my admin console that my service account is authorized to pull data from DFP. Previously the above lines of code used to work fine on v201405. Am I missing something here ?