-
Notifications
You must be signed in to change notification settings - Fork 43
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
Want to direct lunch APP on loading #7
Comments
Try finding
|
Thanks Prabeen!.
But it’s not working in chrome browser in android phone. Please find my text page.
http://exploria.me/deeplink/index.html
Thanks,
Manish Jain
From: Prabeen Giri [mailto:[email protected]]
Sent: Wednesday, January 10, 2018 5:16 AM
To: prabeengiri/DeepLinkingToNativeApp <[email protected]>
Cc: BhavJain <[email protected]>; Author <[email protected]>
Subject: Re: [prabeengiri/DeepLinkingToNativeApp] Want to direct lunch APP on loading (#7)
Try finding AppLauncherFactory and update the strategy to direct
else if (browser.isAndroid) {
deepLinkingStrategy = new AppLaunchStrategyFactory('direct');
if (browser.isAndroidNativeBrowser || browser.isAndroidStockBrowser) {
deepLinkingStrategy = new AppLaunchStrategyFactory('notsupported');
}
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#7 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AQiEQwy-bUfXIhrsjiuBvAAmSqSRKY8qks5tI_o2gaJpZM4RX89p> . <https://github.com/notifications/beacon/AQiEQ2x_0WUddHsEZ0uV--KXyOmiW0WQks5tI_o2gaJpZM4RX89p.gif>
|
Ah, If I remember it correctly, chrome doesn't allow direct launch anymore, it needs to have CTA. |
ohh, There is any work around to open direct Native app on page (Android + chrome) loading.I appreciate your help. |
@BhavJain I don't think so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I want in android device direct lunch app without clicking on APP button. Please suggest what changes i need to do
The text was updated successfully, but these errors were encountered: