facebookConnectPlugin.login shows web browser instead native implementation #348
Comments
Same issue |
Same here too. |
it is also happening to me :/ |
I have the same issue. Working perfectly fine on iOS8, but iOS9 and iOS10 are using the web browser. |
same here. My |
After reading quite a few posts on the topic, it would seem this is expected behavior. Anyone find anything saying otherwise? |
Uhm.... I said in the first post that I was able to open it directly via The official facebook implementation looks very professional and great. So what I can do to have a professional solution with facebook 2016-10-20 15:00 GMT+02:00 Tim Shultis notifications@github.com:
|
Patrick, I can't speak for your experience. But this sums up what I have been reading. |
Here is an issue on this project for basically the same thing. #53. |
Hmm I'm using iOS 10 on this completely. I'll try to debug it if I find time later on the next week 👍 |
web browser is the expected behavior since ios 9 |
No @robertarnesson. Why it should be? And I had iOS 10 on the day. Then please tell us how to switch to non-web-browser. Thanks in Advance! 👍 |
this has been asked a million times, please read the facebook sdk documentation above. This is the direction facebook has decided to go with the sdk, its not something the plugin has control over. |
Hey guys,
a few hours ago I clicked on the facebook login button and I was redirected to a real facebook app window.
Then I changed nothing and logged out and logged in again and then after click on facebook login again, I was redirected to a web browser.
Why?
I'm using default script.
First on 12:14:
Second on 17:59:
Don't know what the difference is.
On the first screenshot you can see that the app is newly created and requesting access first time. On second screenshot it says that it is already granted.
But I revoked the permissions and tried again so that I get the first screenshot again - but again as second screenshot only in web browser.
So what I'm doing wrong?? 👎
Thanks in Advance for ideas!
The text was updated successfully, but these errors were encountered: