Databases
StackOverflow2013
Postsdbo
POAre URL Scheme Suffixes Working in Facebook iOS SDK 3.1?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAre URL Scheme Suffixes Working in Facebook iOS SDK 3.1?
    text
    copied!<p>I'm trying to update an app of mine to from iOS SDK 3.0 to SDK 3.1, but I'm having issues getting the URL Scheme Suffix to work. I have a few different SKUs of my app, and have been successfully using scheme suffixes for "ipad" and "iphone" with pre-3.1 SDKs. </p> <p>When implementing the 3.1 SDK and getting read permissions, the Facebook app no longer sent me back to my app (this is when NOT using the integrated Facebook login in iOS6). I noticed that if I removed the URL Scheme Suffix, the login process works as intended and I am sent back to my app after saying "OK" to the permissions. Simply changing the info.plist to not include the suffix makes it work; adding it back breaks it.</p> <p>My question then: are URL suffixes working for anybody with the 3.1 update? I haven't been able to get confirmation as to whether they are working or not. The update does seem to have changed the authentication flow quite a bit, but I can't see why this would be purposely removed. Also, is this bug on Facebook related? <a href="http://developers.facebook.com/bugs/183527235116115" rel="nofollow">http://developers.facebook.com/bugs/183527235116115</a></p> <p>Finally, since I don't feel I can update until this is resolved, what are the consequences of not updating the SDK immediately? I'd hate for my app to break because the old authentication method is killed. Does Facebook have a roadmap for when old auth will be unavailable?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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