I am using the facebook-iphone-sdk framework to integrate my iPhone app to FB. The problem is when I click the button it gives an error "The application you are using is misconfigured for the Facebook integration. Please download the latest version of the app."
I was able to connect with FB only once. For the first time it worked fine and I was also able to post some data into my wall but afterwords it not working, and the above error occurs.
What could I be doing wrong?
The Bundle ID is case sensitive so watch out for that.
e.g. com.myapp.MyApp is not the same as com.myapp.myapp
This happened to me and gave the same error message.
May be you are using the deprecated API of facebook... Please use the New FBGraph API for facebook integration ....
How to share or post by mail, twitter and facebook from the current application?
This is not only about email... here you will find the tutorial and sample code for facebook integration.....!!
Possible Solutions:
1) Double Check that you are putting in the right facebook app id in your code, and that you didnt somehow overwrite that when you made it work the first time.
2) Check that in the facebook developer profile you have all the proper things set up (They have decent doc's for how to set up properly).
3) Check that you are using the most up to date version of the SDK for fb.
4) Consider using the built-in Facebook for iOS6, since you probably wont be releasing your app before iOS 6 comes out anyways.
5) If all else fails, start over and go through the instructions from beginning to end. Check and re-check everything you set up and carefully scan for little typos or something. It's probably a minor mistake somewhere that you're overlooking.
6) Post code if you want more specific help. An error message isnt enough to deduce what your problem is.
Just delete you app from facebook dashboard, create it again, and then change the facebookID in you App-Info.plist, in the key FacebookAppId and URL types array key. I did it and my app works fine.
Delete facebook app, force perform login in safari..
Related
I have this really odd problem. The bosses in the office decided to do facebook tracking by using the [FBSettings publishInstall:<appIDhere>] in the app delegate. This works because the graph.facebook.com/<appID>/activities, etc are called, and Facebook returned true.
However, the problem is that this is NOT showing up in the dashboard. The app_activate shows up just fine, it's just that the app install is not showing at all.
So, my questions are:
Why is it that the install is not read correctly? The call is made and facebook response. Why is it that it's not showing up in the dashboard?
Does facebook do any other filtering? For example, if I delete the app and then reinstall, should the app be counted to have installed twice? In this case, the call to graph.facebook.com/ is made twice to send the MOBILE_APP_INSTALL activity. After this, does facebook do any other filtering? e.g. they remember device tokens, etc?
I am not quite sure how facebook differentiate using the URL scheme. I presume that this is to differentiate people who upgraded compared to people who installed. How does the fb<appid> help as a URL Scheme?
Thank you in advance for all your help.
My iOS application allows me to login using my own facebook account successfully. But when I send it on test flight to a friend, the app downloads but when he presses connect to Facebook (which works on my simulator and personal device), it won't let him log in. Doesn't even give him the option to, just spits out an error (com.facebook.sdk error 2). What am I missing? What would cause it to work for me, but not for others? I'm just looking for a general answer here because I followed all the facebook tutorials and I can't imagine what kind of thing could be going wrong.
I just figured out the problem. Should have been SUPER obvious, but being new to development I didn't realize I needed to change the sandbox setting to disabled in order to allow others to access facebook through my app.
This error pops up when your app is not authenticated properly.
You need to keep your BundleId the same at all places.
Change your bundleId in the app that you have registered on Facebook as com.asdad.casd instead of < teamId >.com.asdad.casd
I am using sharekit to integrate FB in my app and using xcode4. Everything was fine till I was using my old FB app's id and secret. After all being done I created a new app at developers.facebook.com and entered the new key and secret in the app, now here's what which happens, if a previous session exist in the app means a valid access token, then I am able to post on my wall but when I deleted the app from the simulator to check things from scratch then I start receiving this error instead of the login dialog:
"Sorry, the application you are using is misconfigured for Facebook integration......"
I've tried to use the same configuration as per my older apps but nothing happening. Any help would be much appreciated as I am quite much stuck with this problem. Thanks very much for your time.
In the last 6 weeks, Facebook has changed the way session-tokens are stored (https://developers.facebook.com/docs/offline-access-deprecation/). ShareKit may not have implemented the new FBConnect SDK. I highly suggest implementing the SDK directly instead of using ShareKit.
I had the same problem with you with exactly the same error string. but now it's working with me and I can share texts in my new app, and I did nothing in the app's config. don't if this is true, but my conclusion is that facebook need some time to approve your new app.
so just wait couple of hours.
I am working on simple facebook integration that allows users to post high scores to their wall. The way doodlejump handles this is my inspiration. I have it functioning, but it's not very clean and I'm not sure what to do.
I followed the instructions at http://developers.facebook.com/docs/guides/mobile to get up and running. One of the first things it has you do it call [facebook authorize:nil delegate:self]. After that you can call [facebook dialog:#"feed" andParams:params andDelegate:self] to make a post to the users wall. I have two issues with this.
First, when you call authorize it exits your app as that is facebook's new desired methodology as part of "One Single Sign-On" (OSS). That ok, what isn't ok is that my app is doing this even if the user is already signed on. I do not see a way to check if the user is already signed on.
The second issue is that it exits my app to authorize my app to post something to facebook. It seems acceptable to exit the app to sign on to facebook. Most users will have already done this, so no big deal. But my app should not have to exit just to get user authorization to post something. DoodleJump doesn't do that but I'm not sure how.
I tried digging through old posts but the SDK has changed so a lot of them are no longer valid. Thanks.
Based on the latest Facebook SDK (located at Github) and it's example I have determined that this is the expected behavior.
It is built around the new fangled "fast app switching" so it looks like that is just what happens.
A little lame imo but if that's what Facebook engineers have determined to be the optimal process then so be it.
I was having the same problem. Turned out it was because I hadn't set the URL Schemas in info.plist Where it says to fut fbYOUR_APP_ID make sure that you do this how they say. Your plist file should say something like fb12345 and then it will identify that the user has logged in correctly. offline_access will then work as a result
Might not be the answer you are looking for, but the app 'Hipstamatic' connects with facebook for photo upload (which I assume/hope is a similar process as wall posting) from within itself.
It could be worth seeing if they would be able to guide you if you sent the devs an e-mail?
I think they solve this issue by calling an iframe of sorts within the app, connecting the app to facebook and performing facebook activities, then closing once complete.
Hope this helps!
What permissions are you requesting? If you don't ask for offline_access the framework will make the user log in each time.
You can also try ShareKit
It's an open source library for iOS to share links, images and more. It's very simple and also works with Twitter and other social networks.
The site also contains some video tutorial and some code examples to integrate the Facebook API, Check this
I'm using the official FBConnect library for iOS and trying to get it working in my iPad app. Here's what's strange: when my friend logs in using the call to authorize:permissions:delegate, everything works fine: the dialog asks for his authorization to connect to Facebook, the fbDidLogin delegate method gets called, all is well.
However, when I try to login, the dialog never changes. The keyboard is dismissed, the password field is cleared and it just sits there. The issue is the same in both the simulator and on the device.
Here are the things I've checked and triple checked:
My login name and password are correct. If I do put in the wrong password, an "invalid username/password" message appears, and that isn't happening.
The application is not in sandbox mode.
The Application ID is correct (my friend can login without problems).
Some additional information:
Original application was created by my friend.
I created a second FB app and put in the new Application ID
My friend can login with the new Application ID
I can log in to neither.
This appears to suggest that there is something different about my friend's account, rather than the app itself.
We've been banging our heads together on this for a couple of days now. What could be causing this behaviour? Why isn't an error being generated?
Edit: It seems there are a lot of people affected by this, so in the interest of trying to find an answer, I've added a bounty.
There appears to be a server-side problem with Facebook logins as noted here:
http://github.com/facebook/facebook-ios-sdk/issues#issue/95
People have said that if they change their password on Facebook they are subsequently able to log in using the Facebook-iOS-SDK downloaded from github. Obviously that is a poor long-term solution and would be unacceptable in an app released through the App Store. On the bright side, there seem to be reports of similar login problems logging in from apps on other platforms as well.
Update: Facebook has a bug filed on this subject that can be viewed here:
http://bugs.developers.facebook.net/show_bug.cgi?id=13199