I'm trying to implement the new AppLinks API for my Application to route the Facebook-Users to my mobile App.
I've set up the meta correctly, but the Facebook App opens always the URL within the internal Web-Browser (but it shows then at the top right, but that a normal User wouldn't know for what it stands for and wouldn't klick on it).
<meta property="al:web:should_fallback" content="true" />
But if I set the should_fallback to false, the Post is opened directly in the App - But then the Fallback to the WebApp doesn't work anymore.
<meta property="al:web:should_fallback" content="true" />
So Facebook doesn't implemented the AppLinks implementation correctly (so that it doesn't make sense) or did I forget something?
Facebook Documentation
PS: On Android it works correctly: After clicking on a Applink it opens directly my native App, and if the App is not installed then it opens the normal Web-Page
For the Pinterest iOS App this way also doesn't work - but there the Implementation is better than it is in Facebook - There a Infobox is shown to the User:
Does it exist a better solution for iOS or have I to wait until Facebook is investigating into this (if they do)?
I am not sure my comment will be useful but we met similar situation. At same time while we tried to solve issue with fall back we found that everything works well for Instagram. We compared our metatags and found that we have only one difference. It is additional metatag fb:app_id. We added it to the page and magic happened. When app is installed then fb suggest to open it. When it is not installed it does redirect to web url (og:url).
Related
It was working before as it should be: Clicking on my website url from facebook native app (shared post) redirects to the App store when my native app is not installed. If my native app is installed, it opens the url in my app.
I have all the required meta as well as this one:
<meta property="al:web:should_fallback" content="false" />
Suddenly, redirecting to the app store when my native app is not installed stopped working.
Does Facebook no longer support al:web:should_fallback meta tag?
Everything was working fine!
I want to let you know that the issue is now fixed. It was a bug on Facebook object platform. I submitted a bug report on the Facebook bug tracker and they reproduced the problem and fixed it.
How can I publish my GWT application on Facebook?
EDITED:
Facebook requires from the application to have some FacebookSDK configuration in <body> tag on index.html page.
The GWT-generated index.html doesn't contain the <body> tag at all, (it has <bodies> instead o_O ).
How do I do that?
I tried to add these lines to the <bodies> tag and upload app to facebook, but when I click "next" on App QuickStart page I get "Something went wrong. We're working on getting it fixed as soon as we can." Facebook popup.
The app is generated by libgdx and works perfectly in browser on my own server.
Is there better way to publish GWT app?
There are some docs and question here and there, but it looks like they are related to old approach. Thanks!
In my iphone application , i have a reqiurement post to facebook.When i click the same post from Facebook the host app should come up.When i searched here https://developers.facebook.com/docs/applinks/ios it requires some metadata to be added in my file. So i did it.
<meta property="al:ios:url" content="schemename://" />
<meta property="al:ios:app_store_id" content="app store id" />
<meta property="al:ios:app_name" content="Example App" />
<!-- Other headers -->
But it neither opening my app nor redirecting to itunes.
Please suggest me what i did wrong here??
There is also another work around to this. I discovered it by reverse engineering how Spotify manages deep linking. To see this - share a Spotify playlist on your feed. The Facebook iOS app will launch directly into the Spotify iOS app from the shared playlist.
Long story short - Facebook have enable this for Spotify. If you put this meta tag in:
<meta property="fb:app_id" content="174829003346">
then your deep links will magically work (that's the Spotify facebook app ID). I'm still trying to establish if this is due to a misconfigured app or if we're looking at a potential anti-trust case.
By the way - this isn't a workable solution. If your app (and thus URL scheme) isn't installed, the Spotify app will open in its place. It is, however, very interesting behaviour.
This is expected behavior in 2017.
The al:ios:url tag you are using is supposed to do this. Unfortunately, the functionality has been broken for over a year on iOS, and it is a known issue that Facebook has essentially written off as wontfix.
Facebook will now only deep link on iOS if al:web:should_fallback is set to false. This means if your app is not installed, the user will always be taken to the App Store page rather than your own website, even if you have specified al:web:url. Most savvy brands do not want a new user’s first experience to be the App or Play Store page and they are also not willing to sacrifice attribution data. Because of this, al:web:should_fallback is now almost universally set to false, which means there is currently no workable way to launch a third-party app directly from the newsfeed in the iOS Facebook app.
Things still work correctly in the Android Facebook app, but obviously this could change at any time. It's unfortunate Facebook hasn't been more transparent about the change to the iOS version, because there is quite a bit of confusion about it.
You can read more about details behind this issue here.
But there is a workaround.
Services like Branch.io (full disclosure: I am on the team) get around this by implementing a judicious combination of App Links, URI schemes, and iOS Universal Links. Essentially what you need to do is open a page in the webview and then have a button or other user-driven CTA event that launches the app from there. It's an extra step for the user, but currently the best workaround. If you just want to be able to post a link that goes into your app when it is installed and otherwise goes to a webpage (or the App/Play Store), then Branch links are definitely your simplest solution.
Branch link routing logic
I have a facebook app built using iframe. It works ok on most modern browsers except Safari on Windows platform. On Safari windows platform, the cookies seem to get lost as a user move from initial form page to 2nd page with questions.
Here is the live link
http://on.fb.me/1hCfgOX
Can someone help me on how to fix this?
Ok, i found a fix for it which works perfectly. Checkout the following links:
Safari 3rd party cookie iframe trick no longer working?
Facebook Iframe App with multiple pages in Safari Session Variables not persisting
And
http://lightyearsoftware.com/2009/11/on-the-pain-of-developing-for-facebook/
I hope this will fix your issue also, as it fixed mine. If you got any problem, let me know.
Thank you
besides header, you might also need to add w3c/p3p.xml and w3c/policy.p3p files to your website. See here for more details and sample files: Session null in IFrame in ASP.net MVC only in safari browser
I am wondering how this site detected that I have their iOS app installed when I visited their web site on my phone.
http://drafthouse.com/austin
Sites can implement Safari Smart App Banners. See Apple's documentation for details:
Promoting Apps with Smart App Banners
It is done via something like this:
<meta name="apple-itunes-app" content="app-id=myAppStoreID, affiliate-data=myAffiliateData, app-argument=myURL">
These are called Smart App Bannners and are a feature of MobileSafari on iOS 6. You can add these using literally one line of HTML code (a <meta> tag, see the linked docs).