According to the most recent docs, this isn’t a bug because it’s not even a feature any more. Nowhere in the docs does it mention the native login: http://docs.coronalabs.com/guide/social/implementFacebook/index.html
Here is the link for the bug report. Sorry it took me so long to submit a sample!
This is still being looked at by engineering, but it’s not a high priority item. There are disadvantages to using this method as well as advantages. The social plugin might use the method you want. But it requires a Pro subscription.
Rob
We have enterprise subscription, and even with the iOS plugin I can confirm that there’s no native login dialog (unless it’s undocumented somewhere or we just haven’t learned how).
I’ve asked some colleagues of mine and in fact, this is one of the main reasons why they said they won’t consider building their business on Corona. It needs a real Facebook SDK, not a plugin.
I’m very interested in this too, so if you won’t answer to a Starter subscription member, then at least give a better response to someone with enterprise. Yes we could re-integrate Facebook SDK ourselves but why should we have to even consider that? We don’t have an android guy so we can’t just have it on one platform and not the other, and it’s much more work…
And just curious, what’s the disadvantage to using the native dialog?
The facebook.* API does not support the iOS internal login dialog. Even with Enterprise, as long as you’re using our facebook.* interface, you’re not going to get that dialog, though in theory the “Social” plugin uses the iOS share sheet which should use the native login and only fall back to the Facebook fastswitch if it’s not setup.
If you are an Enterprise subscriber, why can’t you use the Facebook SDK directly from Facebook if the facebook.* API isn’t good enough?
See: https://developers.facebook.com/docs/facebook-login/ios/v2.0#dialogs
The limited to iOS 6 or later is no longer an issue, an frankly the lack of the person’s image isn’t that important, but the permissions thing, mentioned both in the disadvantages and in the Special Considerations area are things that have to be worked around with that dialog.
I don’t know if you felt my answer to ArdentKid was too short, but it says everything that I can really say about it.
1. Its still an open bug. We have not closed it.
2. There has been discussion about it but with iOS 8 and the chaos dropped on us by Apple over the past couple of weeks and with other higher priority bugs and features and since the Facebook fastswitch works and is Facebooks recommended method, there isn’t urgency to implement this other non-crossplatform way to login.
As a side note, I did edit my answer because I hit the send button before I was ready. Please read the revised answer if you’re basing your post off of a received email.
Rob
Will this ever be addressed?
I’m curious how many corona users have released an app with facebook login. This is absolutely horrible, especially since apps > 50mb won’t always resume after being suspended and coming back from facebook (making login IMPOSSIBLE).
I think users would prefer the web view even.
So, if corona isn’t going to fix this, then can you please find out for me how to force the web view when calling facebook.login()?
According to the most recent docs, this isn’t a bug because it’s not even a feature any more. Nowhere in the docs does it mention the native login: http://docs.coronalabs.com/guide/social/implementFacebook/index.html
This is still being looked at by engineering, but it’s not a high priority item. There are disadvantages to using this method as well as advantages. The social plugin might use the method you want. But it requires a Pro subscription.
Rob
We have enterprise subscription, and even with the iOS plugin I can confirm that there’s no native login dialog (unless it’s undocumented somewhere or we just haven’t learned how).
I’ve asked some colleagues of mine and in fact, this is one of the main reasons why they said they won’t consider building their business on Corona. It needs a real Facebook SDK, not a plugin.
I’m very interested in this too, so if you won’t answer to a Starter subscription member, then at least give a better response to someone with enterprise. Yes we could re-integrate Facebook SDK ourselves but why should we have to even consider that? We don’t have an android guy so we can’t just have it on one platform and not the other, and it’s much more work…
And just curious, what’s the disadvantage to using the native dialog?
The facebook.* API does not support the iOS internal login dialog. Even with Enterprise, as long as you’re using our facebook.* interface, you’re not going to get that dialog, though in theory the “Social” plugin uses the iOS share sheet which should use the native login and only fall back to the Facebook fastswitch if it’s not setup.
If you are an Enterprise subscriber, why can’t you use the Facebook SDK directly from Facebook if the facebook.* API isn’t good enough?
See: https://developers.facebook.com/docs/facebook-login/ios/v2.0#dialogs
The limited to iOS 6 or later is no longer an issue, an frankly the lack of the person’s image isn’t that important, but the permissions thing, mentioned both in the disadvantages and in the Special Considerations area are things that have to be worked around with that dialog.
I don’t know if you felt my answer to ArdentKid was too short, but it says everything that I can really say about it.
1. Its still an open bug. We have not closed it.
2. There has been discussion about it but with iOS 8 and the chaos dropped on us by Apple over the past couple of weeks and with other higher priority bugs and features and since the Facebook fastswitch works and is Facebooks recommended method, there isn’t urgency to implement this other non-crossplatform way to login.
As a side note, I did edit my answer because I hit the send button before I was ready. Please read the revised answer if you’re basing your post off of a received email.
Rob