Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

Deprecated API calls #22

Open
ianks opened this issue Jul 6, 2015 · 9 comments
Open

Deprecated API calls #22

ianks opened this issue Jul 6, 2015 · 9 comments

Comments

@ianks
Copy link

ianks commented Jul 6, 2015

I got a notice from Facebook that my app is now making deprecated API calls

Your app is making deprecated Marketing API calls, and will stop working soon. All API versions prior to v2.3 will be deprecated on Wednesday, July 8, 2015. Please upgrade to v2.3 immediately, otherwise your application will not be able to call Marketing API anymore. You can find out more from the upgrade guide for Marketing API .

Are other people experiencing this? I imagine that its only a subset of the API calls that are being deprecated, does anyone have any info on what these may be? Are there plans to get this gem in line with the new API? I just took over an app that is dealing with this issue, so I feel a bit lost about this situation, if anyone has experienced this let me know what you have done about it!

@akemrir
Copy link

akemrir commented Aug 7, 2015

I am experiencing same problems, but changing api version in Koala gem leads to other problems.
This require more changes in Zuck, not as it looks like at first look.

After change of versiion, my problems starts at checking which ad account is personal with result:
{"error":{"message":"(#12) daily_spend_limit field is deprecated for versions v2.4 and higher","type":"OAuthException","code":12}}

@thinkberg thinkberg self-assigned this Sep 8, 2015
@amitpatelx
Copy link

@thinkberg would you be able to update us about current state of the development to fix this issue?

@thinkberg
Copy link
Contributor

The master branch should contain the fixes to work with v2.4. In case you still get deprecated warnings, check that you didn't set the Koala API version to anything less than 2.4 by hand.

@olgavasileva
Copy link

2.1.1 :175 > accounts = Zuck::AdAccount.all
type: OAuthException, code: 2635, message: (#2635) You are calling a deprecated version of the Ads API. Please update to the latest version., x-fb-trace-id: Hg7eV979gx0 [HTTP 400] graph.get_object("me/adaccounts")
Koala::Facebook::ClientError: type: OAuthException, code: 2635, message: (#2635) You are calling a deprecated version of the Ads API. Please update to the latest version., x-fb-trace-id: Hg7eV979gx0 [HTTP 400]

@okte2
Copy link

okte2 commented May 3, 2016

Thanks for the great gem! I'm working with Koala.config.api_version = "v2.6". And I could get adaccount info, but had error with getting adcampaigns. It seems the api call is deprecated. See detail below.

type: OAuthException, code: 12, message: (#12) adcampaign_groups field is deprecated for versions v2.5 and higher, x-fb-trace-id: HRjtWhhbF99 HTTP 400

@olgavasileva
Copy link

@okte2
Hey, yes, they did.
They made a major renaming of the fields. :adcampaign_groups were renamed to :campaigns
I have committed the branch with some fixes recently (named "some updates to make gem methods work with newest Ads API 2.6 #24", you might find it in pull requests), but it seem to fail on checks :)
Although, the code I have committed doesn't fix all the changes in the API, but rather, in general, only renames fields (see my README)

@okte2
Copy link

okte2 commented May 3, 2016

Thank you for your quick response!
It was solved by tweaking "list_path" part (api endpoint) of your gem files at local installed directory.
Now I want to use Ads Insights API. Could you integrate that featute in your gem or is there any way to tweak your gem to use that feature?
Thanks in advance!

2016/05/04 0:54�$B!"�(BOlga Vasileva notifications@github.com �$B$N%a%C%;!<%8�(B:

@okte2
Hey, yes, they did.
They made a major renaming of the fields. :adcampaign_groups were renamed to :campaigns
I have committed the branch with some fixes recently (named "some updates to make gem methods work with newest Ads API 2.6 #24", you might find it in pull requests), but it seem to fail on checks :)
Although, the code I have committed doesn't fix all the changes in the API, but rather, in general, only renames fields (see my README)

�$B!=�(B
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@olgavasileva
Copy link

@okte2 I see what happened! After I saw the fail of tests I didn't look at it at all.
I haven't ever used Insights API (I only came across Marketing API because of my job project), and I might need some time to check it out. So, it is really hard to say whether or not this gem could be integrated for Insights. Sorry that I cannot gave a better answer

@okte2
Copy link

okte2 commented May 4, 2016

Thank you for your comment! Looking forward to be integrated in the future ;)

2016/05/04 3:07�$B!"�(BOlga Vasileva notifications@github.com �$B$N%a%C%;!<%8�(B:

@okte2 I see what happened! After I saw the fail of tests I didn't look at it at all.
I haven't ever used Insights API (I only came across Marketing API because of my job project), and I might need some time to check it out. So, it is really hard to say whether or not this gem could be integrated for Insights. Sorry that I cannot gave a better answer

�$B!=�(B
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants