Note that there are some explanatory texts on larger screens.

plurals
  1. PONo interaction with Facebook iOS SDK dialog after switching to thread?
    primarykey
    data
    text
    <p>I'm playing around a little bit with the Facebook iOS SDK.</p> <p>I have a TabBar App (with MainWindow.xib) and I successfully integrated the Facebook SDK.</p> <p>The problem is that non of the Facebook pop up dialogs are responding to my user interactions.</p> <p>For example. I want to post something in the wall. The Facebook SDK opens a dialog but if i try to interacte with the dialog it doesn't happen anything. </p> <p>The log tells me: [Switching to process 2365 thread 0x12d07]</p> <p>How can I fix it?</p> <p>I'm using the simulator.</p> <p>The important code int the AppDelegate looks like that, it's actually more or less the same like on developer.facebook.com:</p> <p>Thank you a lot.</p> <pre><code>// AppDelegate.h @interface AppDelegate : UIResponder &lt;UIApplicationDelegate, FBSessionDelegate, FBDialogDelegate&gt; { Facebook *facebook; } @property (nonatomic, retain) Facebook *facebook; @property (strong, nonatomic) IBOutlet UIWindow *window; @property (strong, nonatomic) IBOutlet UITabBarController *tabBarController; // AppDelegate.m @implementation AppDelegate @synthesize facebook; @synthesize window = _window; @synthesize tabBarController = _tabBarController; - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { facebook = [[Facebook alloc] initWithAppId:@"APP_ID" andDelegate:self]; if (![facebook isSessionValid]) { [facebook authorize:nil]; } self.window.rootViewController = self.tabBarController; [self.window makeKeyAndVisible]; return YES; } @end </code></pre> <p>Kind regards.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload