I would like to upgrade my Facebook application Graph API version from v2.3 to v2.9 .
I researched my application's usage of the Graph and Marketing APIs, and saw that it is calling the Marketing API with the version explicitly in the url.
Regarding the Graph API, the only config for it's version is in the app Dashboard (in the FB developer dashboard).
If I change the version in the Dashboard - will it affect only the non-explicit calls for the Graph API? or also the explicit calls to the marketing api?
Related
I'm currently working on a plugin for wordpress, in which I have to use Google Analytics Reporting API and Facebook's Graph API.
Now everything is working fine with their respective php SDKs, the only problem is both are very large and not suitable for a plugin.
I'm only using Google Analytics Reporting API and oAuth from google sdk and some functions of Graph API.
What can I do to reduce size of the sdk?
Thanks!
I have requirement to share a product image and its description from my website to instagram.
Can anyone tell me is it possible?.
I went through the Instagram Graph API documentation but everything is related to Mobile Apps, can i use the same API for sharing from my desktop website.
Thanks in advance.
There is content publishing API support for FB Instagram graph API. but that is in beta yet.
https://developers.facebook.com/docs/instagram-api/content-publishing
The Content Publishing API is in closed beta with Facebook Marketing Partners and Instagram Partners only. We are not accepting new applicants at this time.
The Content Publishing API is a subset of Instagram Graph API endpoints that allow you to publish media objects. Publishing media objects with this API is a two step process — you first create a media object container, then publish the container on your Business Account.
Currently, the API can only be used to publish photos.
This would also require your Instagram account to be business account to use this API.
I am trying to upgrade the api version of my facebook developer app by API Upgrade Tool
and I am getting following message:
Your app hasn't made enough calls to the Graph API to show any info,
or there are no changes for the methods you selected between v2.0 and
v2.1
How can I upgrade my facebook app's api version?
We have a facebook app which surely with open graph 1.0 (app created before May 1th, 2014, and can be switch to v1.0 with graph API explorer). The problem is, we can't get all friends from user from /me/friends - the API just behaved like 2.0 - return friends who also install this facebook app.
We heard rumors that if someone (app administrator) once call the open graph API v2.0, it will be switch to v2.0 and never come back. Is this true?
Thanks to lgy, we created these facebook apps before April 30th 2014 but didn't activate them (login/etc.), so they were switch to v2.0 by facebook.
We know how to call Facebook Graph API v1.0 and are calling it in the iOS SDK (https://developers.facebook.com/docs/apps/upgrading) but new users are getting treated as though they're signing up with v2.0.
We know that once a user logs in via Graph API v2.0, there is no going back to v1.0 for that individual user (http://code-worrier.com/blog/changes-in-facebook-graph-api-2-dot-0/) but does anyone know if all new users to your app will automatically login through v2.0 and only previous users can login v1.0? We're using the Facebook iOS SDK v3.14.
Thanks so much.
New users signing up for your application since 4/30/2014 will return app-scoped id's. The version you use in the URL for the API request won't change that.
Here's what we found out: you can still log into / use the old version of the Facebook API (v1.0). The issue is the API version that gets called by your app depends on the Facebook iOS SDK version you are using in your app. So if you want to jump back to pre-v2.0 Facebook API, you need to be using an old version of the Facebook iOS SDK (3.13.1 and previous). They are all found here: https://developers.facebook.com/docs/ios/downloads
Keep in mind, Facebook is forcing developers to upgrade to v2.0 by April 30th of 2015. But, if you have a v2.0 headache now that you don't want to fix right away, this a decent band-aid solution. In our app, we upgraded the Facebook iOS SDK to get compliant with Apple's IDFA regulations, not knowing we were upgrading to v2.0 of the Facebook API. Since our app uses some features no longer available in v2.0, this was a huge issue.
Any users that may have signed up for your app while you were using v2.0 may need to delete app related info on Facebook so that they can log in fresh when you jump back to v1.0. This will allow you to get real Facebook user IDs and not app scoped user IDs.
The last small hurdle is that Apple is now rejecting many, if not all, apps that use the IDFA. All Facebook SDKs that use v1.0 use the IDFA (to my knowledge). The only way around it is to tell Apple that you are using it, but that it is attributed to a previously served advertisement (you do this on iTunes connect). See this article here: http://www.adexchanger.com/mobile/apple-throws-a-bone-to-app-marketers-blesses-idfa-for-attribution/
Again, this is not necessarily a 'proper' solution, but if you don't have the bandwidth / resources to fix your v2.0 issues right now, it can definitely help. Just make sure to get back to v2.0 before April 30, 2015.