while posting, it is giving an error like "your message couldn't be sent because it includes content that other people on Facebook have reported as abusive" this thing is happening from today it self. Before it is worked fine with same code. I tried to resolve but no luck.
Can any body help me to resolve this thing!
]1
You can use the appeal form for blocked content.
What is the url that you are trying to share?
Related
Issue with downloading Apple Pass on an iPhone device using Chrome and Firefox. It works fine on Safari. On Chrome for iOS it says:
Sorry, your Pass cannot be installed to Passbook at this time.
For Firefox it says:
Failed to Add Pass An error occurred while adding the pass to Wallet. Please try again later.
I tried just downloading the Apple Pass from a desktop browser and it downloads and I can install it fine on an iPhone/simulator which I'm assuming is not a problem with the pass itself but maybe rather something I'm missing in the response.
Here is the code I'm using to return the Apple Pass.
private void ReturnResponse(byte[] applePass)
{
Response.Clear();
Response.AddHeader("content-disposition", string.Formate("attachment; filename={0}", "sample.pkpass"));
Response.ContentType = "application/vnd.apple.pkpass"
Response.BinaryWrite(applePass);
Response.End();
}
Expected result:
Apple Pass opens and allows the user to add it to their Apple Wallet.
I realise this is question is over a year and a half old, but this is still an issue as of March 2021. After a lot of trial and error we managed to get it working on Chrome & Firefox. Our specific issue was that the request has to be a GET, and we had a form before the Pass was downloaded that submitted as a POST. Once we change the form to submit a GET the issue was resolved.
We tried to keep the POST and return a 201, which feels correct, but the issue persisted.
Changing our request method from a POST to a GET when serving the pkpass made it possible to download the pass using Google Chrome for Mobile on an iOS device.
This is untested, but I have found this link which I feel might be related:
https://github.com/eymengunay/php-passbook/issues/73
It says that the anchor you using to link to the pass should contain the this attribute:
target="_system"
I have not tested this resolution myself.
I just bought 20 access passes from a website. The site had the option to "add to apple wallet". It worked fine for 19 of them and then on the very last one I got this same error.
I did not do anything different when trying to add the 20th one.
Wondering if there is a limitation with the number of passes you can add?... but why would it be limited to a random number like 19?
I have tried like below in my app delegate. Can you please tell me what's going wrong here:
Flurry.setDebugLogEnabled(true)
Flurry.setLogLevel(FlurryLogLevelDebug)
Flurry.setEventLoggingEnabled(true)
Flurry.setBackgroundSessionEnabled(true)
Flurry.setCrashReportingEnabled(true)
Flurry.setShowErrorInLogEnabled(true)
Flurry.startSession("KEY")
As stated in this post please check with the support from Flurry first, to make sure that this isn't normal behaviour. The post also states that it can take up to 8 hours for a crash to appear in the dashboard.
Flurry support page : https://developer.yahoo.com/flurry/support.html
Make sure to include your API-key in the email, so they can actually check on your problem.
I am using iOS FB SDK (baked in Parse F/W) to send app request invites using
[facebook dialog:#"apprequests" andParams:params andDelegate:nil];]
The requests are being sent correctly and also appear on the invitee's account.
When I click on the request, the Facebook app correctly starts my app.
At this point, I am checking for incoming URL to process and get request_ids etc.
The sample code on FB (http://developers.facebook.com/docs/tutorials/ios-sdk-games/requests/) says the incoming URL should be of following format
fb480369938658210://authorize&expires_in=3600&access_token=xyz&target_url=http://m.facebook.com/apps/friendsmashsample?fb_source=notification&request_ids=abc&ref=notif&app_request_type=Duser_to_user
However, I am receiving it like this
fb123456789123456://authorize?expires_in=86400&access_token=BAADiMgKGSZB8BAD3ZCeZAGNkm7d8tGuNZAKuq5nThbNTdiZA1ZBFcp1bhIKp1cFvwDsOPZCZBIgowSwRkBnZARF5tBsyWHk0yLukZAK8ubNZA4ZCbkyQg619cg9v0SMqsaBzgwNbQZCdPZBSLoYwZDZD&
target_url=http%3A%2F%2Fwww.facebook.com%2Fappcenter%2F123456789123456
So there are missing components here like request_ids, ref=notif etc.
Does anything obvious looks to be missing here?
Please help.
Thanks.
For future users, I had to set up the Mobile Site URL as per this bug filed with Facebook - https://developers.facebook.com/bugs/465760136778889/
Ridiculous, but it works. Hope this is resolved. Not sure why they have this dependency.
Quite simply unable to make a post with just the text and NSURL object. I can do it with just the post, or with the post, NSURL and image, but ideally I'd just like to provide the link with the post.
It simply states "Cannot post to Facebook" as "The post cannot be sent because the connection to Facebook failed."
Is there anything I can do? I'm not using the Facebook SDK at the moment, but perhaps I might have to?
Many thanks
We just started running in to this issue with code that was working correctly yesterday. Googling shows a lot of people having this issue sharing from other Apple apps today via native integration. I actually think this is an issue on Facebook's end.
I tried sharing a URL from Mobile Safari and it too fails with the same error. Can you confirm that Mobile Safari also fails to share?
Well for now I'm able to leave the image part nil (still include the method, just leave the argument nil) and it will show the text and link only.
My app uses a custom URL scheme so i send a link to my users in an email which when clicked, launches my app installed on their devices. This was working seamlessly till iOS 6 came into picture.
Now when the users click on the link or even type the address manually in the safari they get an error saying "Safari cannot open the page because it is a local file."
Wondering if anyone else encountered the same or if someone has any pointers in this regard !!
Any help much appreciated...
Update: it works if I only give my app's custom url without any parameters.. e.g. if I do "reader-app://" it launches my app but if i do "reader-app://doc=xyz" it doesn't !
try: reader-app://?doc=xyz (add a question mark after //) this way you'll specify a query string. It works for me, but it presents an alertdialog asking the user if she wants to open the url with my application
Try to remove the - sign from reader-app://.
My URL was not working until I removed underscore sings from URL.
Ex:
my_app:// is not working.
myapp:// is working.
That is just a guess.