When I launch the firebase dynamic link, it keeps relaunching my app. Is there a way to not relaunch it? For iOS and Android. Android I read you have to put the intent filter but I do not know how to do it for iOS. Because of certain functions, i require the app to maintain its state, because I am waiting for a webhook from the other app that I have launched to.
And the other app, doesnt append the data back to me... so I lose all my data. <<< this happens IF I provide the dynamic link to the other app and it calls the dynamic link.
Currently, what I am doing is just relaunching the app and relying on a callback url that the other app offers which also currently not working out, firebase dynamic link gives me useless information, instead of keeping the original link, it gives me the fallback url, which unable to append parameters as the other app appends a & without url encoding, so all i get is a url with 0 information.... and even with the information I have to jump through hoops to navigate to the right page... seriously... why?
Please help. I have no idea what to do.
PS:
So ultimately removing all my intent-filter with host and scheme of my Firebase dynamic link. Removing my associated domains app links. Ultimately, I am unverifying myself to the app link. But it gives me the most ideal result which allows an external app to call my app, and continue where I left off.
Related
Inside my android app I have hardcoded a link to some web service. Now every time the link to the web service changes, I need to make an update of the whole app through Goggle Play for changing this link.
Better would be if the application first connects to some other “static” web service and then gets the properly link that I can change whenever I want without an update.
Even better would be if it could be done somehow with Google Play, but I didn’t found any information for such a functionality.
Are there some suggested solutions to do that?
Implement GCM in your app and push notification with new url to all devices any time it changes. Then store that url in shared preferences / database on device.
We have a case where we want to navigate between apps, case where
triggering a payment will open the payment app
once the payment is complete it should navigate back to the original app.
I have found few theoretical solution for (1), can use Android Intent(I hope I'm right here), or use services like https://deeplink.me. Which navigate to the payment app, I assume here that I can pass some complex data along with the request to navigate to the correct page on my app.
For problem 2, I'm yet identify a solution, Do I have include Intent filter in the source app too? say the source app uses the payment app's sdk and is there a way I could pass back the response an HTTP response which the source app can use to navigate to the right page (payment success or failure).
You are correct: an Android Intent can be used to open another app (documentation). Facebook's Applinks standard can also do this, as can the Branch.io service (amongst many other things). Deeplink.me AppWords is a neat concept, though it appears to be bid-based and I can't see a way to open a specific app on demand.
However, unless there is a need to use an external app for this, why not just integrate something like the Stripe Android SDK, or PayPal's braintree SDK or native SDK directly into your app? That way you don't even have to worry about passing data around externally and you retain end-to-end control of the process. Seems like a far more elegant solution!
Recently I built an Android app that consume data through JSON from a back-end. There is no public/front zone, it's only back-end. Moreover I built a showcase-website just to let people know the app exists.
Back-end and Showcase-Webiste reside at two different URLs. In the developer console I enabled the app indexing and the showcase-website is the one I set.
I'd like to add deep linking but I can't figure out how to configure the intent-filter.
For example, suppose my showcase-website URL is this:
http://nolimitsworld.com/
How should I configure the data section of the intent-filter? the host parameter should be?
The question in your subject line is misleading. You do have a public web site, and that's your showcase web site. Use that showcase web site for your intent filter. The backend url only gets called from your android app anyway, so no one needs to know that one but you.
If you still need help figuring it out, please remove the api url from your question, and just show us the url to your showcase web site instead (and only register that one with google).
Now if your other concern is that you wish to index your application without going through any web site at all since most people wouldn't recognize the domain name of your web site anyway, then there is actually no need to do deeping linking and app indexing through google.
You could just get away with indexing the content of your app with a search provider and launching your app with an explicit intent. Google doesn't even need to get involved if you do that.
Is it possible to have some piece of data passed in to the app on the very first app run through via the Google Play link (maybe as an Intent).
The scenario I envision is this:
I share a special url to my app in the market for special clients (promotion, etc)
They download the app, install the app.
On the first run, I can pull off the data I put on the url somehow
Magic happens
Current Solution
My current solution to this problem is sending out a generic link to the market, and have a second url that they click that my app has an intent-filter. I'd really like to have only one url for people to click.
Thoughts
An alternative I've considered, is having the link go to my server, save some unique information about the HTTP Request, then try to correlate that information with a web request on the first app run, but that seems very error prone (IP isn't unique on Wi-Fi behind a NAT, User Agents don't match...).
Any advice would be greatly appreciated.
Have a search for the com.android.vending.INSTALL_REFERRER Intent. This source, for example, says:
Starting with Android 1.6, the Android Market's emits a broadcast
Intent named com.android.vending.INSTALL_REFERRER whenever certain
parameters are added to the market url. Note that web version of the
Market also passes these parameters to your devices upon install.
I have no idea how up-to-date or well-supported that is, but it sounds like what you want.
I am working on an Android login app for a service called Netclassroom. There are many for different schools (you can google for one), but I'd prefer not to share the one I'm working on. They're all the same. I want the app to log into the site using given credentials, but I'm running into a problem.
The problem is that it "does not use authentication" and the post request doesn't work? Is it even possible to log into a site like this? By that I mean that I want to enter credentials and get to the member page to parse.
You can make an app that just starts the browser on a particular URL. Here's a post that describes how to do it,
How can I open a URL in Android's web browser from my application?
Further, I think you are asking if the app can circumvent the normal web page login mechanism. Don't do that. There's a login on the web page for a reason. If your app gets around that, then it's decreasing the security that the folks that designed the web page put in place. The correct thing to do is to work with the folks that wrote the website. If they think what you are doing is acceptable, they should make their login cookie longer-lived, or allow the user / pass fields to be stored in the browser, etc.
Again, there's absolutely no rational for making the android app less secure than the browser app.