I added a uber link button to my web app that passes my current location for pickup and a dropoff address to the app. I tested it on Saturday and it worked. I clicked the button, the uber app on my iPhone opened immediately with my current location as the pickup address and the address I passed in as the dropoff. I'm sending latitude and longitude as well as text address. It was working perfectly.
Now, since Monday, the same code is doing something different; even when I send the exact request. Now I get, "This site is attempting to open a pop-up window". I click "Allow". Then I get, "Open this page in "App Store". I click "Open" and it brings up the Uber app in the app store. From there I click OPEN. It opens the app, but the pickup and dropoff addresses are not being passed in.
I've tried different addresses and get the same result. Here's the link I'm sending (I removed my client ID for this post).
https://m.uber.com/ul?client_id=xxxxxxx&action=setPickup&pickup=my_location&dropoff[latitude]=33.392117&dropoff[longitude]=-112.000173&dropoff[formatted_address]=3747%20E.%20Southern%20Avenue%20Phoenix,%20AZ,%2085040
Can anyone please help?
Is it possible you forced the link to open in Safari at some point? The universal link remembers how you last opened it and tries to do that again. So in this case, it seems like it's trying to open it in Safari, which goes to a page that redirects to the App Store, rather than opening the native Uber app.
If that's the case you can long press on your button and you should see an option to 'Open in "Uber"' If you tap that, it should work as expected (and continue to for future taps)
Take a look at this comment
Related
I have published an alpha version of my action quite a while ago. I'm trying to determine the bare minimum to get it visible to testers.
I have whitelisted the one email account I had created for this test.
If I add them and send them the opt in link, it opens a page with the title "null" and says something along the lines of "we can't find what you're looking for..."
If I open the same link as the owner of the action it works fine.
What do I need to do to enable white listed users to access the action on their devices?
The link must be opened on a mobile device that has the Assistant installed. It can't be opened on the web. (The Assistant is the one that actually needs to go to the page - not a browser.)
The approach I usually use is:
In the Assistant, make sure it is set to the account you want to use. I usually go to the "Explore" screen and click my user avatar in the upper right to set it to the right one.
Send the link to the authorization page via email, hangouts, or some other chat.
Open that link by clicking on it. If you're prompted for an app to use to open the link, select Google or Google Assistant.
For universal links, there are two breadcrumbs: one for going back to the app containing the original link and the other sending the user to the unviversal URL in safari. Is there anyway to hide the forwarding breadcrumb so the user doesn't have the option to click it? The problem i'm facing is, once they hit that URL, when using another universal link in the future, it automatically sends the user to the app store rather than the app itself, despite the app being installed.
We use URL Schemes for our iPhone Application. If a user enters a certain URL in his Browser, then our App opens right away, if installed. If it is not installed then the user is directed to our mobile Website.
We embed these URLs in QR-Codes. So our user just need to scan the barcode, click "open url" and are directed right to our App / mobile Website.
However there is a Problem with some QR-Code-Scanners. For example "QR Code Scanner" from "iHandy Corp" opens the URL inside their own app. And because they open it inside their own app, URL Schemes apparently doenst work anymore. Even though the User has installed our App, he is still directed to our mobile Website.
Has anyone else run into that issue? I just want our users be able to use any QR-Code-Scanner they please und still be directed directly into our app, when they scan our URLs.
Yes, but you can't do anything about it. If the app sends the URL to an internal web view control, and not to the platform to be opened by the browser, it just doesn't work.
I have developers working on the backend of my app using phonegap and once the user clicks facebook/twitter share a browser pops up and you can log in and share but after
that you cannot escape back to the app, if you get out of the apps altogether then try and return to my app you're right back at the facebook/twitter screen instead of in my app. This is only happening on iphon because on android they have a back button. The only way to get back into the app is to restart the iphone/ipod to get back to open
the app from beginning. I cannot have this as the only option for
people to share from my app as it would be horrible and could ruin my
app before I launch it. They say their is no way to fix it but Im sure its fixable so I am trying to get any info on this that I can.
The other issue is the facebook post itself. currently it post like this
Sent from Appname(with link to app)
www.appname
Text here
but this is kinda counter intuitive because the actual message should
be on top otherwise it will get lost in the other text. They said
this is the only way facebook allows it. Is it possible to get it like this
Text here
Sent from appname(linke here)
www.appname.com
Again any help on these two issues would be great so I can pass the
info to my developers.
Question:
I am actively looking in the source code on Github's facebook-ios-sdk project myself but I was wondering if anyone already knows how to relaunch an app that sent an iPhone user to Safari, such that the user can come back after some work has been finished?
Example:
When using facebook to login, the original app is relaunched after the facebook login page has authenticated the user.
Motivation:
I would like to be able to do the same for youtube videos without having to completely lose the user. I don't want to use the standard webview approach because I don't want to provide extra space to first let the video load for the user and then have the user click the play button. I want to skip the play button and its associated click entirely! Instead I want the user to be able to click on just an everyday regular iPhone button and be shown the video with the navigation for coming back to the app via relaunch.
You need your app to register a "custom URL scheme". Then get the callback in the remote web service to return a URL with that scheme. iOS will then launch your application.
More (somewhat old) info available here.
A list of common custom URL schems on iOS can be found here.
Generally, as part of the OAuth login process, you supply a callback URL as one of the paramaters. What this does, is tell the remote server (YouTube), that on successful authentication, redirect the user to the supplied URL. If YouTube supports this (does it support OAuth?) then on successful user login within safari, youtube will tell users safari to redirect to the supplied url. If this url is a "custom URL scheme" it will cause your app to relaunch and you can handle the situation from there.