Redirection to the appstore from a deeplink works randomly on facebook messenger, only on ios.
After clicking the link, when the prompt pops up asking if the user wants to leave Messenger and open another app, pressing Continue will often leads to nowhere, leaving the user stuck on the https://[my.domain].link.
The times it will work, it always pops up the prompt 2 times asking to leave Messenger when it is working. The first prompt never works, only the second one does.
This behavior will happen randomly for the same link.
I have tried tweaking the $uri_redirect_mode parameter, unsuccessfully
The parameters I'm passing to the link are ase simple as follows :
'$uri_redirect_mode': 1,
'$canonical_identifier': canonicalIdentifier,
'$desktop_url': 'https://itunes.apple.com/fr/app/myApp/appId',
'$ios_url': 'https://itunes.apple.com/fr/app/myApp/appId',
'$android_url': 'https://play.google.com/store/apps/details?id=com.myApp'
I expect the branch deep link to work in a more consistent way on facebook messenger, knowing that I don't have this problem on whatsapp (ios) or android. Please help me understand if I'm missing something
Branch Links are known to resolve to your fallbacks on FB messenger regardless if you have the app installed or not. For Branch Links shared on IOS Facebook Messenger, you should enable a deep view as an intermediate step between your redirect.
Reference: https://docs.branch.io/links/integrate/#expected-link-behavior
If you have additional questions, please write in to support#branch.io. Thanks.
Related
First post after decades as a frequent visits, thanks all for the help throughout the years!
Im building a solution that will require webcam/microphone access.
The solution will be running in an iframe in another system.
We cant controll the attributes on the iframe to add allowed="..." and our solution is (and must) hosted on another domain.
IE, we cant show the promt for the user allowing access to webcam/mic
We want to use Uppy webcam in an popup window, but, as we noticed, the actual promt for access occurs in the "mainpage" and not the popup, so we cant seem to reach it.
If we run the solution when its not in an cross-origin iframe (new tab), everything works perfectly!
Any suggestions on how to work around this issue?
Regards
Pär
I am developing a simple application using ADF comes with basic CRUD operations (create, read, update, delete). In this case, as you can see, I have dragged a link to the 1st column which is highlighted in yellow.
So whenever I deploy it and click that, it is supposed to redirect me to the Edit page where client will allow to make commit:
I did make sure the Action of link is associated with the Edit page (as highlighted in yellow above). However, the link wouldn't redirect me anywhere, no response.This is the unbounded task flow:
Okay so I have found out the solution. Due to the default setting, the application will be deployed on IE and this message will prompt out. As you can see, the message is mentioning about browser's compatibility. My IE is version 11.6, I'm not sure what's the issue here since my IE is kinda latest version but this message still pops out and affects the redirect link from working. However, simply copy the application URL to Google Chrome and run should fix this issue. Hope this helps in future.
If the two pages in the Unbounded Task Flow, then Add WildCard Control Flow Rule
and connect the two pages with the WildCard.
Or you can use the Popup instead of opening a new page for edit
I am developing a PWA using react JS
There is a requirement that we need to display the add to Home screen even after the App has been added to the Home screen for the first time
Can any body suggest if this is possible and how?
INFO: Mostly this app will be run on Google Chrome and Safari
Refer to this answer. You simply can't do that, unless you want to do it in specific development/test machines where you can set the below chrome flag,
chrome://flags/#bypass-app-banner-engagement-checks
You can't expect all your end users to set this flag, so this can't be a solution for all the real users.
I also don't see why you would have to show the banner even after adding to home screen, for any other use case. Browsers don't allow this for obvious reasons. It will be annoying the user, if the prompting is left to developers. Linked answer have more clarification on the same.
I'm implementing an application using the full MEAN stack.
I created a login page to signup with facebook to be able to show a profile page. But I discovered some problems. For this reason, I created a smaller version of my webapp, maintaining the same project structure.
The complete code, executable (only replacing "client id" and "secret") with "npm install" and after "nodemon" is available here: https://github.com/Ks89/MEAN-OAuth_Example
If I'll call (with a browser) the rest API that I created to login with facebook at "http://localhost:3000/api/auth/facebook", everything will be ok!
But if I'll want to do the same thing, clicking on the "Login" button, I'll receive the error as in figure:
I know that the problem is related to CORS, but how can I'll fix this in my application, maintaining the same project structure?
I don't want to put the "rest path" inside the HTML. I tried for many days different solutions without success.
If you want, experiment directly on my application that I created exactly to write this question ;).
If really necessary, I'll able to post the entire source code here, but I prefer an organized and executable code into a repository for this particular question.
Please, give me some ideas and hopefully a solution, because I'm really blocked.
The example routes from the passport-facebook repo are intended for multipage apps, not ajax requests. If you look at what those routes are doing, /auth/facebook is just a redirect to Facebook where the user is expected to log in if necessary and authorize your application. When you make that same request from angular, it follows the redirect and tries to load the Facebook page, but the browser blocks you as your console screenshot shows. CORS would be relevant if Facebook wanted to allow you to request their login form across origins, but they don't because that would basically make you a phisher.
It looks like you're trying to handle authentication without leaving the page, but at some point you're going to need the user to leave your site and be redirected to Facebook in order to complete the OAuth flow. You can either open a pop-up containing the Facebook OAuth dialog (it looks like this is what the Facebook JavaScript SDK does by default) or just use your app's current tab with something as simple as <a ng-href="{{facebookOauthUrl}}">Log in with Facebook</a>.
I'm just trying out a simple app in the CocoonJS launcher which contains some links that open some external page.
This works fine, but the problem is that I can't identify a way to go back a page (i.e. history back). The launcher app just displays the page in fullscreen, no user controls visible at all. This is troublesome, because when my users tap on an ad, I want them to be able to go back to the game.
Am I missing something or is this simply not supported?
I do not know of any way to display a navigation bar or something similar.
Nevertheless, you can open your external urls via Cocoon.App.openURL(url); which will enable the user to open it via a normal browser where you can navigate back.
Regards.
I agree with the solution proposed by Scdev. Also, interstitials or fullscreen ads usually have a dismiss button themselves. I might be misunderstanding something.
Regards,
Iker.