iOS app using OAuth2 with Google and Safari presents open page dialog - ios

I have finally got my iPhone app to authenticate and return back to my app with the authorisation code. The main problem was that the reverse client id did not get picked up by my app. I had to add an url scheme of my bundle id instead of the reverse client id.
Anywho, the problem is post authenticating in Safari I am presented with a open 'app name' page dialog. If the user clicks open it works fine. If they leave it for just a few seconds it redirects them to the Google homepage and they have to start all over again. If they are using two factor authentication by any other method than phone call I think it fails too.
How can I avoid this open page dialog?

The solution I found was to use the official Google library for iOS. This does not involve Safari like the AeroGear library I was using does.

Related

iPhone OAuth login request redirects to App not Browser, doesn't work

My current scenario is:
Running an iPhone on the latest iOS
LinkedIn App is installed and logged in
Web browser is NOT logged into LinkedIn (because I have the app)
Developing a web app with "log in with LinkedIn" functionality
On the iPhone, clicking the "log in with LinkedIn" button redirects me straight the the LinkedIn App, which subsequently does nothing - just shows me my feed. I have verified this same behaviour occurs on a third-party site as well as my own. Note that Android exhibits similar behaviour, though I haven't tested as extensively there.
I've found several workarounds:
If I open the web site in Private Browsing mode clicking the login button asks me if I want to open the App or stay in the browser.
If I long-press and "Open in background tab" the login button it'll open (in the background, of course) instead of redirecting to the app, allowing me to log in.
If I manually type "linkedin.com" into the browser and log in then it seems to work too.
None of these are even vaguely practical for end users, essentially forcing us to remove the option entirely.
I'm fairly sure this is a problem at LinkedIn's end and the solution is either:
Don't redirect to the App for OAuth Authorize requests, or
Make the App correctly handle OAuth Authorize requests.
If I'm incorrect and there's some way we can stop this redirect from the client side I'd be happy to hear, otherwise I hope LinkedIn engineers actually see this...
See the comments in Issues with Linkedin Social connection
LinkedIn already confirmed that it is a problem on their side.

Use URL scheme to open react-native App

I am working on a react-native app that uses the Spotify api.
Long story short, I had to use the LiknkingIOS Library to open the auth page in the Safari app and get the necessary tokens and all works, I even got to redirect to my app one the user is successfully authenticated using a custom URL scheme.
The only problem is that a prompt saying "Open in 'myApp'?" appears.
I need help figuring out a way to avoid the prompt from appearing or using another component to open Spotify's auth page without leaving the app.

Link to Ionic page from external website

I'm integrating an Ionic app with a 3rd party web authentication framework. The framework requires that the user visit a web page to authenticate and then receive several authentication token cookies.
I plan to open a link to the external login page, have the user authenticate, and then be redirected back to the Ionic app.
I need a URL to the homepage of my app so that the login page can redirect the user back after logging in. How do I generate a a URL for a location in the Ionic app?
why not just use the in app browsers plugin so that the user never has to leave the app in the first place.
https://github.com/apache/cordova-plugin-inappbrowser
Our app has a blog and we use this
$scope.readMore = function (index) {
$scope.link = $scope.articles[index].WebLink;
window.open($scope.link, '_blank', 'transitionstyle=crossdissolve,toolbarposition=top');
};
by using the option _blank we can have the user open up a webpage inside the app not have to have the navigate away from the app in order to access a url, i also looks way better than a iframe.

Google Plus not able to redirect to application after sharing in iOS

the issue is in sharing of some thing using google plus in iOS application. the login works fine of google plus in my and google provided demo.
when i implemented it back 2 months it worked fine but suddenly i checked it today it gives error.
1) when i try to share some thing it redirects me to safari as expected. in both case when i am trying to login.
2)but when i press share button it shows sharing dialogue and after that it redirect to new page and error comes like "about:invalid#zClosurez"
3)but when it opens safari for login and i authorise app and it redirect me to my app back perfectly.
4)sharing is working fine the things that user wants to share is shared but it does not redirect back to my app.
https://code.google.com/p/google-plus-platform/issues/detail?id=794&can=8&colspec=ID%20Type%20Status%20Component%20Owner%20Summary%20Stars
click for detailed question
Thanks in advance
This was a bug Google's side with the page that was redirecting the user back - it was fixed in a release this week, so you shouldn't see the issue any longer.

Different Facebook Auth Dialog in Safari?

I found two different FaceBook auth dialog while using two apps one is "Poker by Zynga" and other one is I am developing.
When I use FaceBook login in "Poker by Zynga" then Safari opens this page:
And when I use my app which is under development now, then Safari opens this page:
You can see both of these are two different pages. In Poker by Zynga, it says "Logged in as Vicky Gupta - Log Out" where user can choose Log Out to sign in as a different user. While in my app it says "You are logging into this app as Vicky Gupta", in this there is no Log Out button. The only way to log in as a different user to open FaceBook in Safari and then log out from there.
Does any one know why this difference is occurring ? am i missing something in FaceBook app settings? Or is this a normal behavior because I don't think so?
Note: I am using the latest FaceBook SDK (with graph api).
If you are using latest iOS Facebook SDK, I think to logout a user you just have to delete the token obtained by the Facebook main object.

Resources