I am using Facebook Connect. When I click on the "Log In" button of the Facebook dialog, it just disappears like normal, but not Login.
If I log in through a device and then press the Go button of the keyboard and if I press Enter in the simulator after entering my username and password that it has successfully logged in but not by clicking on the "Log In" button.
When you say Facebook Connect, I assume you're referring to the current version of the Facebook SDK outlined at iOS Tutorial.
If so, can you confirm that your FBSessionDelegate method fbDidLogin is getting called? (Put a logging message or debugging breakpoint there and confirm that this is the case.)
If it's not getting called, that can happen if you don't put this code in your application delegate, but rather have it in some other object.
Related
I am authenticating user via google login. Whenever i open gmail login window after clicking on login button i can't add login credentials in text Field on simulator because keyboard is not appearing Also user interaction getting disable whenever click on textfield. ? Any one know what is the exact issue?
I submitted my application to Facebook's App Center and now I need to update the application name. When I go to the application settings, and click 'edit' the display name is greyed out. I'm guessing I need to cancel my submission and resubmit but when I click on the "Cancel Submission" a load dialog appears and the page just hangs.
Problem:
I run the sample iOS SDK code for facebook connect. When Facebook app is not installed, the sample app authenticates through Safari just fine and the sample app is able to post successfully.
When native Facebook app is installed, the sample app causes the Facebook app to be launched for authentication which shows a page that is requesting login for the demo app. When I press the login, it brings up another window that has the allow/"don't allow" options. So far so good. The problem is that if I logout from within the sample app (i.e., [_facebook logout:self]) and try to login again, pressing the "login" button in the Facebook app does nothing (it's supposed to take you to the allow/"do not allow" page).
I have specified the App-ID in the sample app and I have included the fb[app-id] (e.g., fb1234) in the plist under 'URL Types' (otherwise, the Safari authentication would not have worked either).
Any help is appreciated.
It does not take you again to the "allow/don't allow" page because the user already gave permission to the app. The only way the page can show again is when the user revoke the access from the Facebook admin panel. I'm not sure if there's a part of the API that can actually revoke the access of the app from the iOS SDK.
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 have built a small app that gets informations from a database on a website.
the first thing the app does is to fetch an rss feed and then display it.
Apple guidelines tell to let the user decide if he/she wants to connect to the Internet, so I have placed an alert at the beginning showing "The app will connect to the Internet. Continue?" with two buttons: "Yes", and "No, quit"
if the user chooses "No, Quit", then I call:
[[UIApplication sharedApplication] terminateWithSuccess];
It Works. But I have read that Apple disencourage that, (Not an official API???) and that the only way to terminate an app should be the use of the Home button.
I tried an alernative: if the user press "No, Quit" I simply show a label that says "Quit the app using the Home Button"...
So, what should I do? leave the alert and quit the app or just show the "please quit" label???
You may never actively terminate your app, otherwise Apple will reject the app (I know by experience ;-). Only thing you can do is show a dialog, e.g. a UIAlertView without any buttons, asking the user to quit via home button.
But I never heard about the guidelines you've cited regarding an Internet connection. Please give a link. I've worked on a lot of apps that connect to the Internet without asking and Apple never complained.
Just leave off the "No" button.
Either the user will hit "Yes" and connect, or the user will terminate (or background) your app by switching to another app, since they have no other choice.
App termination by simply forcing the user to do something reasonable.