-
Notifications
You must be signed in to change notification settings - Fork 40
Deprecated API calls #22
Comments
I am experiencing same problems, but changing api version in Koala gem leads to other problems. After change of versiion, my problems starts at checking which ad account is personal with result: |
@thinkberg would you be able to update us about current state of the development to fix this issue? |
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. |
2.1.1 :175 > accounts = Zuck::AdAccount.all |
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 |
@okte2 |
Thank you for your quick response! 2016/05/04 0:54�$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. |
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:
|
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!
The text was updated successfully, but these errors were encountered: