We use FB JavaScript SDK and we're loading it asynchronously, according to their docs:
https://developers.facebook.com/docs/reference/javascript/
We use it to handle the login and for some basic calls to their API (mostly to publish stories and share links):
https://developers.facebook.com/docs/reference/javascript/FB.login/
https://developers.facebook.com/docs/reference/javascript/FB.api/
Since we started using it, we have experienced different issues on some browsers and devices.
As an example, yesterday we experienced problems trying to post on the user's feed from an iOS device (FB.api('/me/feed', 'post'...)), this problem lasted several hours. Earlier, we experienced problems in other platforms such as IE.
It seems like FaceBook pushes changes to their SDK without testing properly on a wide range of devices.
My questions (not easy questions, I believe):
Have you experienced similar problems. Do you think it is reliable?
Is there any realistic alternative to it?
I've always used the JavaScript SDK and it's been fine. Sure, there are issues from time to time, but that's part of being a Facebook developer.
The only alternative I can think of would be the PHP SDK. Both should be equally reliable.
Related
Just these past 2 days, all of the iOS users have complained that they are hitting a Page not found from their Facebook APP built-in browser to my site. It's been quite stressful for me.
The URLs have Chinese in them, and have always worked until these couple of days (I suppose when the built-in browsers started to work).
Any way to fix this? Thanks!
We had similar issue. In our urls we have hashes (#) when we remove it from shared links it works normally.
Question is why facebook built-in browser doesn't like hashes?
It can be connected with release new version of facebook app on iOS systems which was pushed on 29th August.
I am new to iPhone development. I’ve added Facebook sharing functionality and I also want to add the Like feature from Facebook. I’ve followed one of the examples; it works if Facebook sharing functionality hasn’t been implemented, because some files create contradiction (specifically FBRequest.h). But I want to add both sets of functionality at the same time. Any suggestions?
If you are new then its not a issue. Everybody have same brain. So its not a big issue. Check
this link: http://www.raywenderlich.com/1626/how-to-post-to-a-users-wall-upload-photos-and-add-a-like-button-from-your-iphone-app
First of all understand it then implement it. I know you will surely implement this in Your
App. Best of luck.
I used to use MGTwitterEngine as my main twitter library for iOS, however, the last commit to the project's master branch is more than one year old (at the time of this writing) and the documentation is not that great. Now I am starting a new project and would like to get rid of the "clunky" MGTwitterEngine, what are other twitter libraries out there for iOS? Which are your favorites and why?
I found the following so far:
MPOAuth
ShareKit (provides a lot more than just Twitter sharing)
Apple announced in the WWDC keynote that Twitter access will be built into the OS in iOS 5, so assuming that means built-in API access its likely that all third-party Twitter libraries are being left to wither. Those who develop for iOS have access to the beta APIs, so even though we can't say anything for sure about future API releases, they could (NDA notwithstanding).
That being said, I'd add DDSocialClient to the list. Like ShareKit it does a whole lot more than Twitter, but it's much less prescriptive on user interface. It restricts itself mostly to the nuts and bolts of the service integration. Whether you think that's liberating or just more work is probably a judgment call.
iOS5 is coming out soon but i'm using MGTwitterEngine and it works like a charm. http://mattgemmell.com/2008/02/22/mgtwitterengine-twitter-from-cocoa
Also you can try sharekit but I dont like it as much.
I have recently wired up my application to use the Facebook iOS SDK (http://github.com/facebook/facebook-ios-sdk). The integration works fine, but the pages loads really slow. It takes really a long time to load the login screen. Login action takes more than 10-60 seconds.
I didn't have this problem with Facebook Connect. Am I missing something? Is there a way to optimize this?
Update
I did scan the activity through HTTP Scoop over Wi-Fi which revealed something interesting, there are some .js and .css files that are taking a lot of time in the new Facebook iOS SDK (login.php, ar7ed2ft.css, 4wj242ne.js, abl6sgyy.js,) where as the old one was zippy. How to let Facebook know about it?
New Facebook iOS SDK
Old Facebook Connect
Implement OAuth 2.0 yourself. It just uses HTTPS, extremely easy to implement. In my experience, it was easier than using their confusing, document-less SDK. Important is getting authentication token. You can access all their graphs with it.
If you implement it yourself, you can choose login screen dialog design as one of:
touch
WAP
WAP is uglier because it's for older phones, but if you really need it, it may help you.
Try using this one http://github.com/facebook/facebook-iphone-sdk
Is there an library for the iPhone using the new Facebook Graph API yet?
This library is great: http://www.capturetheconversation.com/technology/iphone-facebook-oauth-2-0-and-the-graph-api-a-tutorial-part-2
I am using it with great success in a current iPad project.
Update: Author just posted code to github: http://github.com/reallylongaddress/iPhone-Facebook-Graph-API
Update: Please check https://github.com/reallylongaddress/iPhone-Facebook-Graph-API/issues/4 if you find post to FB crashing while using code
Not that I have seen and trying to write something myself has been without success. I am VERY disappointed with Facebook and there lack of support in this area especially since they want developers to move over to the API, however iPhone developers are SOL at the moment which is a shame since using their current SDK is a pain in the ass with all of their callbacks and delegates. It is not very clean at all.
FB Graph API SDK for iPhone is rumored to be released during WWDC. Android SDK is already officially announced (but not released, yet).