I'm running through the sample project provided with the Facebook SDK and I'm encountering something that's a little weird.
The general idea for the sample project is: You can post via the Facebook app on your phone
if that's not available but iOS 6 integration is, you can post via that.
If that's not available the last resort is to post via the Facebook website.
Now, on the simulator, which doesn't have the Facebook app, but is iOS 6.1, it allows the Facebook integration via iOS6. The modal view controller pops up, but because I'm not logged in, it asks me to do so via the iPhone settings. That's the response I want.
However, on my development 3GS, running 6.1.3, the [FBDialogs canPresentOSIntegratedShareDialogWithSession:nil]; doesn't seem to detect that the iPhone has iOS 6 Facebook integration, but just isn't logged in. Therefore the popup window for Facebook doesn't appear and doesn't ask me to log in.
Any one know why?
Related
I have a problem with Facebook integration in my application. I am working on giving the user an option to post his latest update to Facebook.
I can successfully post the message the Facebook, but I have problems with the "via MY_APP" section - the MY_APP is not clickable from my iPhone. The name of the app appears correctly, the message is published as I intended it to be, but when looking at the post from Facebook on iPhone, users are not able to click the name of my application in order to get them redirected to the AppStore or the application itself, depending on whether they have it installed or not. That usually works on my iPhone for other iOS apps.
When viewing the Facebook profile from a computer, my application name is clickable and it takes me to the app's community page (I set it up from MY_APP->Edit app->Settings->Advanced->App Page as I though it was required in order to solve the problem on the iPhone, but it didn't solve anything).
On the Settings->Basic screen I configured everything correctly (I think):
Native iOS App is chosen as integration type, and the options are as follows:
iOS Bundle ID: my bundle ID (checked it, correct)
iPhone AppStore ID: the ID (checked it, correct)
iPad AppStore ID: the ID (checked it, correct)
iOS SSO: Enabled
iOS Native Deep Linking: Enabled
URL Scheme Suffix: I left it blank
I also edited settings under Settings->Advanced for Authentication tab:
I changed the App Type from Web to Native/Desktop and disabled the sandbox mode.
Do you guys have any idea what is preventing me from being able to click on the application name when viewing the post from iPhone?
Thanks
I would like to integrate Facebook into an iOS application I am building, however it seems there is no way to set up a Facebook 'Native iOS Application' with an iOS application that is not already published and available in the App Store.
When I Set up a Native iOS Application for my Facebook App from my Facebook developer's account it requires that I fill in my App Store ID. However when I submit I get the following error message:
Your iPhone App Store ID is invalid because the iTunes App Store
reports your app as being unavailable for iPhone and iPod touch.
I have set up my application on iTunes Connect, but I have not submitted my binary yet as I am in the process of building it, so I assume that this message is due to it being unavailable on the App Store.
This seems like a catch 22 situation. I can't test my app until its in the App Store but I can't get my app in the AppStore until I have tested (and built) it. How can I test my iOS application with Facebook before release?
I've been there, but the solutions is simple.
Don't fill out the Facebook 'Native iOS Application'!
For testing all you needed is the Facebook appid.
Later on in the Deep Linking portion of the iOS Facebook Tutorial, it also mentions the AppStore ID and that you can use somebody else's ID temporarily to get all the data to save. They just say to make sure you use your own id when you finally do publish the app.
I dont think facebook Native iOS App settings are necessary. I have done facebook login with it in two of my apps and without it in one of my app and all are running well. Here are workaround by me:
Native iOS Facebook SSO won't return to app
We have a popular Facebook Application and a version of our App for the iPhone. I was wondering how we can make our Application appear in the "Apps" Section on the new Facebook iPhone app. On my iPhone I currently see links to the App store for Pixable, Badoo, Airbnb, Foursquare and WhoisNear iPhone Application.
I have filled out the Native iOS App settings in the Developer section on Facebook (including adding the Bundle ID and the iPhone app store ID) several weeks ago thinking it took a while to update, but still nothing shows up on my iPhone app.
Any help would be appreciated.
Best,
M
Screenshot of where we want our app to show up:
Edit your Application Settings and on the Basic Settings specify a Mobile Web URL for your Mobile Web integration. You should be able to set the URL to your app's iTunes URL.
Fill out the iOS information within the admin settings of your application, which also means they are using the same application id. You also have to have granted at least the basic permissions via connect on the app, and have the app installed on the phone.
I have implemented FBConnect into my iPhone App, and it works perfectly on the Simulator (v4.3). However, when I test the the same code on my iPhone (v4.3.3), it appears as though my Facebook Button now exits out of my application and opens the Facebook App. The Facebook App displays a page saying I have already authorized my app, and that I should press "Okay" to continue. At first I did not think this was necessarily indicative of a problem, but when I hit the Okay button, I am simply returned to my appViewController where I clicked on my Facebook Button in the beginning.
What I expected, and what occurs correctly in my simulator, is that a smaller Facebook subview window would appear in my application view after clicking the Facebook Button, and I would be given the option to publish to my Facebook Wall.
I should mention, that I have successfully been able to run the "DemoApp" (facebook-ios-sdk test program) on my iPhone. Also, my app does not crash and no errors are reported in my debugger console window.
Why am I experiencing such different results when running the application on my iPhone? Has anyone else experienced a similar problem? What can I do to fix it?
Thanks in advance,
Jeremy
Have you had a look at the "Authentication and Authorization" section at https://github.com/facebook/facebook-ios-sdk?
The difference between the simulator and your device is that your device has the Facebook app installed. If you didn't have the app installed, I'm guessing it would work perfectly because the authorization callbacks are handled directly within the app. However, with the Facebook app installed, after the user authenticates your app, the Facebook app "redirects" to your app using a URL handler.
It is your job to implement the correct URL handling code by setting up your plist property (which you appear to have done since your app relaunches after the Facebook app authorizes you), and also to respond correctly to the - (BOOL)application:(UIApplication *)application handleOpenURL:(NSURL *)url app delegate message. The details to implement this launch handler correctly should be listed in the link above.
I am working in face book functionality in my apps. I have integrated the latest Face book-IOS-SDK. When runs the application, the application is started and runs in the safari browser. Now I want to load the application in the user view(FB web view) instead of Safari. How can I achieve this?
Facebook doesn't want you to. Facebook's new SDK wants the user to login into Facebook once, and than that Facebook login be used in every app on the device that uses Facebook. Because of the way the iPhone works, the way they had to do that was through safari so that each app could get that info. You can go back to the original way (which so far I personally prefer), but I'm not entirely sure how.
However, if you use the new way, it will automatically redirect the user back to your app once they finish authenticating it. Also in the Safari page they can give your app permissions, ie. post status updates.