Facebook Returns Error Code 102
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers
Failed To Authenticate The Application Because Of App Name Mismatch Ios
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x fbapierrordomain error 2500 Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it =an error occurred during publishing only takes a minute: Sign up iOS Facebook posting using Open Graph fails - error Code 102 up vote 1 down vote favorite I am using this example to post my story to facebook. I have my own Open
Failed To Authenticate The Application Because Of App Name Mismatch Android
Graph objects, stories though. This worked well when I had existing login into my iPhone's native FB app. This login was the one who administers my FB app. I have everything verified including bundle ID, URL scheme, app store ID and so on. After some time successfully posting, I started observing that my posts were successfully getting posted (response code) but not appearing in FB timeline. I played with timeline audience access and so on, but to no avail. Then
Facebook Ios Sdk
I switched the user on device FB app, and I started getting error code 102. The response doesn't say much, except this: Error Domain=com.facebook.Facebook.platform Code=102 FBAPIErrorDomain error 3506 I figure from this documentation that this has something to do with API Session - I am doing nothing inside my app to obtain one, and I don't know if I should, if I am using the above example code. What should I do to ensure I always have valid Facebook session while I post? ios iphone facebook facebook-graph-api share|improve this question edited Dec 7 '14 at 9:19 asked Dec 5 '14 at 21:28 Nirav Bhatt 4,56442767 1 See stackoverflow.com/questions/15479534/… –Ming Li Jan 6 '15 at 19:02 upvote thanks. Just figured it through another of that kind: stackoverflow.com/a/27805425/1506363 –Nirav Bhatt Jan 6 '15 at 19:08 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted The answer to this is same as what Ming Li suggested, and has been derived from this. Before FB app approval by Facebook, one needs to add test users to perform actions related to permissions. share|improve this answer answered Jan 6 '15 at 19:10 Nirav Bhatt 4,56442767 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Nam
Sign in Pricing Blog Support Search GitHub This repository Watch 85 Star 227 Fork 418 facebookarchive/ios-howtos Code Issues 0 Pull requests 0 Projects 0 Pulse facebook developer Graphs New issue iOS Facebook sharing using Open Graph Share Dialog fails - error Code 102 #7 Closed vividcode opened this Issue Dec 7, 2014 · 3 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 3 participants vividcode commented Dec 7, 2014 I was following FBOGSampleSD for sharing with my open graph http://stackoverflow.com/questions/27324966/ios-facebook-posting-using-open-graph-fails-error-code-102 objects. Initially the code worked fine with stored login in my native iOS FB app but the moment I switched login it stopped working. The error I get is this: (com.facebook.Facebook.platform error 102.)" UserInfo=0x20141c70 {error_code=102, error_description=An error occurred during publishing., app_id=244500685679948, error_reason=The operation couldn’t be completed. (FBAPIErrorDomain error 3506.)} Have posted it here too: http://stackoverflow.com/questions/27324966/ios-facebook-posting-using-open-graph-fails-error-code-102 Please help... vividcode changed the title from https://github.com/facebookarchive/ios-howtos/issues/7 iOS Facebook posting using Open Graph fails - error Code 102 to iOS Facebook sharing using Open Graph Share Dialog fails - error Code 102 Dec 7, 2014 caabernathy commented Dec 16, 2014 It could be that the user you switched to doesn't have permission to test out your open graph action. Is your action approved? If not, is the user you switched to an admin, developer, or tester of the app? sourabh-vvdn commented Jan 9, 2015 @caabernathy - where we will get our action to be approved ??? Thanking you in anticipation. caabernathy commented Jan 9, 2015 Check this link which I believe outlines the process https://developers.facebook.com/docs/opengraph/submission-process In the meantime you can add the user as a tester for your app. caabernathy closed this Jan 9, 2015 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. Reload to refres
have permission for this action17User request limit reached100Invalid parameter102Session key invalid or no longer valid104Incorrect signature190Invalid OAuth 2.0 Access Token200Permission error294Managing advertisements requires the extended permission ads_management and an application that is whitelisted to access the Marketing API2606Unable https://developers.facebook.com/docs/marketing-api/error-reference to display a preview of this ad2607The given currency is invalid for usage https://developers.facebook.com/docs/graph-api/using-graph-api with ads.2615Invalid call to update this adaccount5000Unknown Error Code1349118One or more of the given URLs is not allowed by the Stream post URL security app setting. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains. Read more about Login Security failed to to learn more about app settings related to security.1359036Ad Create Failed - Too Many Ads: The account {account_id} has reached the maximum number of ads {max}1359102Invalid Parameter In Spec: Parameter has invalid value or missing required parameter: {param-value}1487006Invalid Campaign ID: You must specify a campaign, and the campaign specified must belong to the account specified and must not be deleted.1487007Campaign Ended: You can't edit ads in a failed to authenticate campaign that has ended. Please create a new ad within this campaign, update the campaign end time, pick another campaign, or create a new campaign.1487010Ad Bid Too High: Your bid is above the maximum for its type and placement. Please try again with a value below the maximum if you would like to raise your bid.1487013Bid Too Low: Your bid is below the minimum for its placement and type. If you don't want your ad to run at the minimum bid rate, please pause it. Otherwise, please increase the bid to be within the suggested range.1487014Campaign budget was too low. Please increase the daily budget to at least 2 times the amount of the highest CPC ad bid, which is at least {minimum_budget}. You bid {bid}.1487015The ad creative is invalid1487065Ad Missing Targeting Spec: Ad spec needs a targeting spec. Please use targeting field to specify what audience the ad should be shown to. Field 'countries' is required; all others are optional.1487087Ad Create Failed: The Ad Create Failed for the following reason: {reason}1487089Target Spec Invalid: The target spec is invalid: {reason}1487090Ad Edit Failed - Spec Errors: {error}1487108Invalid Cities: Please check that the format in which you are specify the cit
Fotos hochladen und zahlreiche andere Aufgaben ausführen kannst, die eventuell für eine App erforderlich sind. In diesem Leitfaden erfährst du, wie du all dies in der Graph API durchführen kannst.GrundlagenWir behandeln die Grundlagen der Graph API-Terminologie und -Struktur in unserer Graph API-Übersicht. In den folgenden Abschnitten erfährst du mehr über die verschiedenen Vorgänge, die du mit der API ausführen kannst.LesenAlle Nodes und Edges in der Graph API können einfach mit einer HTTP-GET-Anfrage an den jeweiligen Endpunkt gelesen werden. Wenn du beispielsweise Informationen zum aktuellen Nutzer abrufen möchtest, tätigst du wie folgt eine HTTP-GET-Anfrage: GET /v2.5/me HTTP/1.1 Host: graph.facebook.comDie meisten API-Aufrufe müssen mit einem Zugriffsschlüssel signiert sein. In der Graph API-Referenz für den gewünschten Node oder die gewünschte Edge kannst du ermitteln, welche Berechtigungen in diesem Zugriffsschlüssel erforderlich sind. Du kannst auch den Graph API Explorer verwenden, um schnell Schlüssel zu erstellen und die Funktionsweise der API auszuprobieren.Der Node /me ist ein spezieller Endpunkt, der für die user_id der Person (oder die page_id der Facebook-Seite) steht, mit deren Zugriffsschlüssel die API-Aufrufe derzeit ausgeführt werden. Mit einem Nutzerzugriffsschlüssel könntest du wie folgt alle Fotos eines Nutzers abrufen: GET graph.facebook.com /me/photos Die zurückgegebene Antwort ist von den gelesenen Nodes oder Edges abhängig, hat aber im Allgemeinen das folgende Format: { "fieldname": {field-value}, .... }Auswählen von FeldernStandardmäßig werden nicht alle Felder in einem Node oder einer Edge bei einer Abfrage zurückgegeben. Du kannst die gewünschten Felder oder Edges mit dem Abfrageparameter fields auswählen. Dieser eignet sich besonders, um deine API-Aufrufe effizienter und schneller zu machen.Der folgende Graph API-Aufruf https://graph.facebook.com/bgolub?fields=id,name,picture beispielsweise gibt nur die ID, den Namen und das Bild in Bens Profil zurück: GET graph.facebook.com