I think i dug through the whole facebook sdk documentation but can't seem to find the way to get the users Phone number or Address. Is this feature removed, as of spoken in this thread where it's suggested it will be re-enabled in a few weeks (2011).
This information is not available via the Facebook APIs and will not be added anytime soon. If you want this information from the user you should prompt them for it after they have logged into your application using Facebook.
Here's a link to Facebook's APIs:
https://developers.facebook.com/docs/reference/api/user/
You can use the graph API explorer to gain a clearer understanding of what information is and isn't available.
Related
I'm looking for the right approach to solve the following problem:
For my own non-business Instagram account I like to read which accounts follow me and which accounts like and comment my posts.
I read about the old and the new API, about API deprecation etc. Now I'm unsure which approach shall I choose?
Instagram Platform API
Graph API
other approach like browser automation (e.g. InstaPy)
Instagram/Facebook says "If you are building apps for Instagram Non-Business Accounts, please use the Instagram Platform API". But the process to get an account seams to be complicated. And as I understand until 2020 Instagram will deprecate this API completely.
Additionally as I understand the sandbox mode doesn't help me, since it is restricted and won't show the real results.
From what I can tell, you should use the Instagram Platform API. I think you're right that the Graph API is only for servicing Business Accounts.
I'm in the same boat. I made an app that lets users sign in with their own non-business accounts. Setup OAuth flow using the old API, which works in sandbox.
However, I submitted for approval this week and haven't heard anything. There's no way to contact Instagram or know how long it will take to get approved.
I personally have some experience with InstaPy and I can tell you that it is used mainly for directly interacting with said accounts. You can follow, comment, like, etc... on these accounts that follow you but actually accessing a list of all of them would be more tricky. That's why I wouldn't recommend browser automation for the goal you have set out for.
i facing an issue regarding the FaceBook Graph API.
actually a friend of me, have an FB App whitch can be used for the Graph API.
But in that case I activate a FB dev APP for myself, i'm not able to generate a valid security Token with the App-ID and App-Security.
At first the App is live and activated. For that I don't understand the error message at the end.
Second I don't want to have a User-Token with a validation for an hour.
These are the step's i following:
getting App Token
https://graph.facebook.com/oauth/access_token? client_id=20179479xxxxxx&client_secret=3048xxxxxxxxxxxxxxx&grant_type=client_credentials
The result i'm receving:
"access_token": "20179479xxxxxxx|Pqxxxxxxxxxxxxxxxxx",
Now if im trying to use the Graph API Explorer and trying these token as authentication, I'm facing an #200 OAuthexception
my request:
Get -> /v2.12/coca-cola
"(#200) Access to this data is temporarily disabled for non-active apps or apps that have not recently accessed this data due to changes we are making to the Facebook Platform. https://developers.facebook.com/status/issues/205942813488872/",
Have somebody any ideas how to solve or what i'm missing here?
With the Security Token from my friend he can use the example with coca-cola from the developer like in the documentation and example from FaceBook as well.
Thanks in advance
Facebook is changing the API due to a security issue. This means new apps have more restrictions and less access (for the minute) than apps that were already registered and using the API, probably why your friends key works. Seen as your app is either new or hasn't recently accessed the data you are requesting, you currently cannot fetch it.
Its not known what features will be removed from the API following this incident - as a result I wouldn't come to rely to heavily on any feature the API offers.
Im hearing that the ability to retrieve events could either be removed or the data you can access from an event is going to be severely limited, however thats not from any official facebook source. All apps will be subjected to a review according to this official facebook post, before they are granted access to the Events API, Groups API, and Pages API.
I am trying to access workplace data using Facebook Workplace API. I am the System Administrator for the workplace. Still I dont get the CommunityId in the Custom Integrations page.
Has anyone come across this same situation? Any suggestions would be great !!
You can find your Community ID by making a Graph API GET call to graph.facebook.com/community with a custom integration access token (https://developers.facebook.com/docs/workplace/integrations/custom-integrations/reference/community)
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.
I'm using MonoTouch (latest version) and I want to be able to allow the user of my app to make a wall post based on a log entry made in this app. All I need is a simple implementation so that the user can tap "Share on Facebook" (UIActionSheet) and then it logs them into Facebook (shows the login) and returns the token which I can then use to make the WebRequest to post to their wall.
I've seen the MonoTouch bindings on github but have no idea how to use it. Can someone please provide a simple sample of how to just login to Facebook to retrieve a token so I can post. I know how to do the post, it's the auth process that I'm not getting right.
Thank you.
Neal
Neal,
I have added a sample that replicates about half of the Facebook sample here:
https://github.com/mono/monotouch-bindings/tree/master/facebook/sample
I would recommend to use client-side javascript login more than native device login.
Sooner or later you might want an Android, Windows Phone or even Facebook version.
Having an In-App browser wrapper to deal with javascript and direct Graph API calls are easier for cross-platform implementation. Just from my personal experience.