-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dubious "User cancelled the login process" errors #90
Comments
Hm, looks like a possible race condition when handling the deeplink. I will investigate more |
Hi I'm facing the exact same issue. After clicking the Uber Login Button in my app, I get redirected to the native Uber app where I click "Allow". I am redirected back to my app. However, I see the following error: Using Swift 3. Would appreciate any help! |
Following up with respect to the above question @jbrophy17 |
I got the same problem here. Does anyone have any update on this? The Strange thing is I can run the Objective-C demo without this issue. I am using:
|
Hey @liaa, @Avinodh, and @regosen: Just double checking, but did you include the deep link handlers in your @available(iOS 9, *)
func application(_ app: UIApplication, open url: URL, options: [UIApplicationOpenURLOptionsKey : Any]) -> Bool {
return RidesAppDelegate.sharedInstance.application(app, openURL: url, sourceApplication: options[UIApplicationOpenURLOptionsKey.sourceApplication] as? String, annotation: options[UIApplicationOpenURLOptionsKey.annotation] as AnyObject)
}
func application(_ application: UIApplication, open url: URL, sourceApplication: String?, annotation: Any) -> Bool {
return RidesAppDelegate.sharedInstance.application(application, openURL: url, sourceApplication: sourceApplication, annotation: annotation as AnyObject)
} |
@edjiang I am also facing this issue and also when I click on Ok from error popup Uber app doesn't redirect to my own app and when I manually open my app console logs the same error message. But in the backend of Uber it says I authorised my app to use Uber but actually Uber app throws me this error. Any help? |
Did you register the URL scheme in your app's info.plist? |
Hey @edjiang, I'm also seeing this but only for the first time when i press the Uber Login Buttun and the system shows me the alert "x" wants to open "Uber". After clicking allow and the redirect to my app i get:
Second login works fine so that makes me think it's not an issue in the configuration but i might be wrong. |
What iOS version and SDK version are you on, @nafetswirth? |
@edjiang SDK version is 0.8 iOS versions were 9.2, 10.2 and 11.2.1 |
Fix is published to Cocoapods, 0.8.1. Thanks so much for your help! |
@edjiang Been away from this project for a while, but back to working on it. Glad to see a fix for this was just released. Will test this and see if it works in my use case. Thanks for publishing this! |
Hi @edjiang
My environment is:
Please let me know if I am missing anything. |
^ replying to my comment above, I have successfuly solved it. I needed to add the following to my
I bieleve this is mentioned in your |
Uber Android Authentication with uber SDK Solved As Uber latest SKD version 0.10 Android have this "user cancel login" bug Please following the official link which is based on Uber SDK 0.8 where the latest one has the issue which is 0.10. Please use sample code from below link which is 0.8 uber sdk, without "login cancel issue". Following sample for android uber sdk is 0.8. https://github.com/uber/rides-android-sdk Please change to this one in Manifest file for LoginRedirectReceiverActivity
Rest is update your code with Happy Coding :) |
Hi @edjiang, ios - 13.5 Thanks |
(Using UberRides 0.5.2 via CocoaPods, tested on iPhone6 with iOS 9.3.4)
Immediately after obtaining a valid access token via deep link, our login methods themselves will sometimes return a nil accessToken with the following error:
Note that I definitely did not cancel anything as the user. All I did was press "Allow". This has happened with both of the following methods (with AllTrips request):
If we ignore the error and use the valid access token we had already received beforehand, everything seems ok.
The text was updated successfully, but these errors were encountered: