I have created a custom story with a custom action and custom properties. All of this is approuved by Facebook. My action have the explicit share capacity whitch should post the graph action on the newsfeed.
When i test my code from my device with FBDialogs presentShareDialogWithOpenGraphAction, everything is fine, no errors, no logs. On Facebook i can see the post in my timeline and activity log but NOT in my newsfeed.
This problem exists only in Facebook desktop version. In my fb mobile app, the custom story appear in newsfeed, no issue in this case.
My facebook application is in sandbox mode.
I have search a lot on the web and see a few solutions like the explicit_shared flag on the action but not working.
Have somebody resolved this problem ?
Related
I have to implement navigation from facebook post to my native iOS app or app store if the app is not installed. For that, I have tried Facebook APP Link feature but it did not work. Then I created Firebase Dynamic link and post it on facebook app directly. After tapping on posted link, it shows one pop up saying "Leave Facebook? This webpage is trying to open an app outside of Facebook. Are you sure you want to open it?"
After tapping on Yes, it does nothing. I have cross verified the created link with https://app_id.app.goo.gl/apple-app-site-association It shows associated bundle id, team id, app store id.
Can anyone please suggest me the proper pathway to implement deep linking with facebook post to the app?
Also, can we test deep linking with the app which is not on the App Store?
Thanks in advance.
Facebook doesn't like users to leave their app. They stopped supporting App Links in their iOS app almost a year ago, and have never supported Universal Links (which is what Firebase Dynamic Links uses).
The only workaround is to send users to a landing page with a CTA button, and put another deep link behind that button (on a different domain than the one on which you're hosting this landing page). It's an extra step for the user, but currently the only option. Branch.io (full disclosure: I'm on the Branch team) does this via the Deepviews feature. Dynamic Links currently doesn't have an equivalent, so you'd need to build something yourself.
I'm using the Open Share Dialog from Facebook SDK for iOS in my iPhone App to share a custom story. I created open graph action and object which is already successfully approved by Facebook review team and live.
But if a user shares a story using my App, it's not shown on the news feed of his friends. So I googled a lot and looked here in stackoverflow and everyone writes to set the ExplicitlyShared flag to true. But this is not working for me using the share dialog. After setting this flag to true user stories will not be generated anymore and the post button is disabled.
Also in the Developer Docs Facebook provides this hint:
Anybody a solution?
I used exactly the same code as in the Facebook OpenGraph Share Dialog sample on GitHub: https://github.com/fbsamples/ios-howtos/tree/master/FBOGSampleSD
I recently implemented open graph in one of my iOS apps. Currently it posts a custom activity that when tapped is suppose to show more information about the activity.
This seems to be working for the majority of users. However, I've had a few report that when they click/tap on the posted activity it simply directs them to the app facebook page.
Has anyone else experienced this inconsistency? I cannot figure out what is going on.
I'm currently working on a prototype for adding Facebook social features for future iOS games. One of the features I've been working on involves using the new native Facebook Composer to post to a link to the game, and then tracking the post and giving the player coins for every person who likes the post. After the post, I get their feed and look for a post with a matching application ID. I've already got that part working correctly if I don't use the new native Facebook Composer (either old style dialogs, or just a direct post with no dialog).
The problem I'm encountering is when using the new SLComposeViewController, the post will appear to come from the application "iOS" id "213546525407071" rather than the id for my application.
Is there a way to change the attributed application so that it uses my application ID instead of iOS?
That's how SLComposeViewController works. If you want your own app designated, you have to design your own UI and use FBRequestConnection from the Facebook SDK as discussed here.
We have an iOS app that publishes certain activity to Facebook that contains links to pages on our domain. Our intention is for friends to click on those links and view them as webpages.
However, when you click on links in these published stories in the FB iOS app, it's auto launching our app instead of going to an embedded Web View or kicking out to safari.
Note: We still want to have single sign on (SSO), so just want to change the behavior of clicking links in published stories.
To clarify, this is what I'm talking about:
My app is able to publishes http://foo.com/123 into the FB newsfeed for a particular user that opts in.
That person's friends see the link, but when they click it, it just goes to http://foo.com/123 in the browser instead of launching my FOO app. This is because my app doesn't yet handle incoming context from FB iOS app.
I still want FB SSO to work from my FOO app. That is, when clicking on FB sign in in my FOO app, it jumps out to the FB iOS app (if installed) and does a single sign on and redirects back to my app. IOW, I don't want to break this authentication scenario that currently works.
What setting in the FB developers App Settings controls this? It's not clear from the documentation. I see sections for Native iOS app and Website which I currently have set but it's unclear which sub-setting affects the behavior in question. Also, it's not clear even if I was to find the setting, can I affect it without affecting SSO.
The setting you want in the Facebook App dialog is under the iOS Native section (see the screenshot below) - set both the highlighted sections to Disabled.
This won't affect Facebook login/SSO in the app, so you'll still be able to do the OAuth dances.