Recently i registered app on yammer to use yammer for login to my web app. There is a problem on iOS with this flow, because when i try to login I get mobile yammer app login pop up & after that it only opens yammer app, and no redirection to my web app actually happens.
This only happens on iphone, on all other devices it works, on android also works with yammer app installed. Somebody familiar with this ?
Related
I have an ionic 3 app that needs to launch my company’s Twitter page in the device’s browser. The Twitter link is like : https://www.twitter.com/mycompany.
When I add this link to my page, the behavior is like this:
If there is no Twitter app installed on the device, the ionic app
will launch the device browser with the Twitter url above.
If the Twitter app has been installed on the device, the ionic app will
launch the Twitter app, and users have to log in to use the Twitter
app.
This happens on iOS only, even when using InAppBrowser plugin.
Is there any way to always launch the link using the device’s browsers, even when the Twitter app has been installed? It really annoys when users have to create an account and log in to Twitter app just to view my company’s Twitter page.
Thanks.
I'm writing a hybrid app with Ionic and the workflow I imagine for a perfect facebook integration would be the following:
Scenario of a user logged in facebook with a native app:
Open my app
Touch login with facebook
Be prompted for facebook permissions and approve
Be directed to the desired screen of my hybrid app
Scenario of a user logged in facebook with his mobile browser:
Open my app
Touch login with facebook
Be prompted for facebook permissions and approve
Be directed to the desired screen of my hybrid app
Scenario of a user not logged in facebook (both in the native app and mobile browser):
Open my app
Touch login with facebook
Be prompted for facebook credentials
Be prompted for facebook permissions and approve
Be directed to the desired screen of my hybrid app
Is it possible to achieve as the mechanisms used to save session of a native app and a web app (facebook website) are way different?
How can I know if the native app is installed and once I know how can I use its session to prompt the user for permissions (as the android native apps do)?
Thanks in advance
How can I develop a kiosk mode app which will be used for many different facebook users. Each one could have logout by my app and not by the official facebook app cause they will not have access to the official facebook app.
In response, a facebook employ told me this: https://developers.facebook.com/bugs/696057353756212
any suggestion is welcome.
Basically, if you're building a kiosk app, you don't want to use SSO, since you cannot control who's logged into the Facebook app.
If you're using the LoginButton, it's as easy as doing something like:
loginButton.setLoginBehavior(SessionLoginBehavior.SUPPRESS_SSO);
And when your app exits, just do a closeAndClearTokenInformation() as you've already alluded to.
What SUPPRESS_SSO does is it will only bring up a web dialog for users to log in, and will bypass the Facebook app altogether.
Is it possible to use the Facebook iOS SDK to authenticate within an app (not go to Safari), and also keep those authentication credentials for the next launch of the app?
I have usedFacebook SDK sample code SessionLoginSample to check . It opens the Facebook login account in the safari....I want it to open with-in the app ..
I am not using FBConnect as it is been expired ...How to use it for the Facebook SDK
of
https://github.com/facebook/facebook-ios-sdk ...its sample code
https://github.com/facebook/facebook-ios-sdk/tree/master/samples/SessionLoginSample
this sample code here~~
The Facebook iOS SDK will open within the app provided your user is on iOS 6 and has their Facebook account setup within the device. Otherwise, it will gracefully fallback to the Facebook App (if installed) and then only to Safari. From the SDK Docs:
The native Login Dialog is available after a user has logged into
Facebook on their device. If the device isn't connected to Facebook,
the native Login Dialog isn't available and permission requests will
be made via the fast-app-switch to the Facebook app (if installed) or
Safari. The Facebook SDK methods [...] will seamlessly fallback to
this fast-app-switch behavior.
If your user has neither Facebook configured on their iOS 6 device nor the Facebook app installed and you still want the login to happen within your app, your best alternative might be to pull up a UIWebView pointed to your own server somewhere that carries out a server-side login.
Bear in mind a big disadvantage of a UIWebView-based approach is that your UIWebView does not share cookies with Safari so even if the user is already logged in within Safari they'll still need to re-enter their username and password again in your app. I'd be a little hesitant to do so in a third party app since there's no way to know if they're spoofing the Facebook site and phishing for my credentials.
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
login.loginBehavior = FBSDKLoginBehaviorWeb;
I have integrated Facebook functionality into my applications. By using the link https://github.com/facebook/facebook-ios-sdk, I have integrated the Facebook. In this application, at the time of login, it's opening Safari and at the same time the application is going to the background and then after login again it's coming back to the application. My intention is that this flow can accept the application store or not.
This is the official Facebook iOS SDK and many apps in App Store already use it. So you can use it inside your app.
Also, the flow in your question is exactly what the documentation of the library describes and is, again, used by apps that are already in App Store:
If the device is running in a version of iOS that supports multitasking, but it doesn't have the Facebook app of version 3.2.3 or greater installed, the SDK will open the authorization dialog in Safari. After the user grants or revokes the authorization, Safari redirects back to the calling app. Similar to the Facebook app based authorization, this allows multiple apps to share the same Facebook user access_token through the Safari cookie.
So, yes, there is nothing wrong with this flow.