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
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.
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).
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).
I have an AIR app where the user could post on his/her FB wall by using the following link style:
http://www.facebook.com/sharer.php?s=100&p[url]=http://www.someurl.com&p[images][0]=http://image.jpg&p[title]=Title&p[summary]=Summary%20Text
It was working some time ago, however it seems to have stopped working now.
I URL encode the whole query string (maybe that's the problem?), and I've tested the resulting link works outside of AIR. I also have a link for Twitter, with another query string and it works with no problems. I've seen some other people having similar problems as well, but the solutions I've seen like using javascript:window.location haven't worked. Also tried to load a custom HTML through loadString() and afterwards redirect to the desired page, with no success either.
What do you suggest? Right now I'm using navigateToUrl, but would like to avoid it.
I'm not exactly sure why this is not working for you, but I'm sorry to inform you that the facebook share button has been deprecated and is no longer supported.
You can read about it in the documentation for the Facebook Share:
The Share button has been deprecated in favor of the Like button, and
will no longer be supported. Please use the Like button whenever
possible to drive maximum traffic to your apps.
And in the documentation for the Like Button:
What happened to the old Share button?
We deprecated the Share Button when we launched the Like button,
because the Like button improves clickthrough rates by allowing users
to connect with one click, and by allowing them to see which of their
friends have already connected
Since it's not supported anymore I'd accept the behavior of it to be unpredictable and maybe it's the reason why it stopped working for you.
I'm not a flash developer and don't have any solution for that, but you should stop using the deprecated method.
Edit
My point is that since you are using a deprecated functionality, even if you manage to fix the current problem, you'll face others later on, so what's the point in spending time on finding/fixing the problem?
As for using like button in AIR, a simple google search for "adobe air facebook like" has resulted in this: Creating a Facebook Like Button in Flash Professional for Adobe AIR.
Also, when posting/sharing something through facebook, their system scraps the url (unless they have a cached version) and so the image, title, description, etc can also come from the Open Graph tags in that page.
Can someone tell me how to implement facebook recommendation or like on mobile (iPhone, Android) web browser?
I following the guides for plugin approach and FB.ui approach:
http://developers.facebook.com/docs/reference/plugins/like
http://developers.facebook.com/docs/reference/javascript/FB.ui
but, none of them gave a mobile web sharing experience for recommentation/like. All of them give me desktop version of recommendata/like page.
Is there any tutorial or examples for Facebook sharing on mobile web? Can anyone help?
Thanks.
<div id="facebook_code"><iframe src="http://www.facebook.com/plugins/like.php?href=www.facebook.com%2F[FACEBOOK USER NAME OR ID]&layout=standard&show_faces=false&width=250&action=like&colorscheme=dark&height=80" scrolling="no" frameborder="0" class="facebook_like_button" allowTransparency="true">
Using the like button was a little bit of a fit, but here is how you do it.
The class is so you can style and position a div, the code calls facebook's like.php script so no need to include an extra call to a js file. The code I used also removes the pop up box that you can not style with the FB faces in it, it just displays names. Leave enough vertical room, in this case 80px for the text to wrap with the BLANK likes this text.
You might have to open a web view/safari because either way you're going to have to prove that the user is logged into facebook somehow.
I'm not sure their iOS SDK supports this but have a look at it on GitHub and maybe check the forks to see if anyone has found a way to add the like button.
You may also be interested in sharing rich content and media using Kik API. It lets you integrate your mobile app into Kik Messenger and use Kik's own transport and infrastructure to share content with other mobile app users. It is also very simple to integrate - about 5 lines of code, in simpler scenarios. There is more info on Kik API website: http://www.kik.com/dev and http://apiblog.kik.com
Disclaimer: I'm one of the developers behind Kik API :)