I have been creating a really small facebook app and I have just realized that the settings page in FB's dev section has changed. The options remained tho, so I went ahead and filled in the most important things (the required ones). When I got to these:
App domain
Site URL
Now for local testing I always fill localhost and that is ok. However, before, I could put the site url like this:
http://localhost:8872/myapp/
Now this doesn't work anymore, it simply refuses to take it and shows me: Something went wrong. We're working on getting it fixed as soon as we can. Hm.
If I change the site url to this:
http://localhost/myapp/
It is saved without problems. It makes my wonder - did Facebook change something and it will stay so, is it indeed their bug and will be fixed, or am I doing something wrong? Please note that it works alright without the port! However, I really need the port there. Thanks!
Related
I've read quite a few question on stack overflow about that. this one and this one and quite a few others...
I've tried with and without encoding the redirect URI in the address bar . With and without https. With and without the final slash. And every combination of the above. I've triple checked the client ID.
encode/decode:
http%3A%2F%2Flocalhost%3A9000%2F
http://localhost:9000/
https://www.facebook.com/dialog/oauth?client_id=272730539567323&redirect_uri=http%3A%2F%2Flocalhost%3A9000%2F
At some point, my code worked, And I logged in with it! Then I tried to change the redirection urls, and it never worked again, even after going back.
The worst is that I'm already logged in and you can see my name and profile picture on the screen !!!
I'm running out of ideas...
Note: I'm not including the actual code as I think it is irrelevant to the question and scala/play specific would only reduce the number of people trying to answer.
Solution:
I'm not sure why, I had been able to login before because I do not remember having ever set/unset the above settings in "settings->advanced tab-> Client OAuth settings".
But if you encounter this problem, here lies the answser.
I've placed two identical files on two different servers to test how the thumbnails work when sharing in FB. Other domain works, the other doesn't. FB debugger gives 503 and scraper says "Document returned no data".
Works:
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.muikkumedia.fi%2Ffacebook%2F
Doesn't work (other provider):
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fartblog.pa-la.fi%2Ffacebook%2F
As there is dash (-) in other domain's (& server's) name, I was thinking it might be the "dash-bug", but debugger can find info from the root domain, so that doesn't seem to be the problem either. I'd give the link ready here too, but I don't have enough reputation for this system here.
Anyway, server provider's answer is: "I'd suggest you contact facebook's support on this issue, as everything looks ok on our end with the info they provide."
Any ideas?
Changed the provider, works now.
When I like an URL on the company website:
http://guidepal.com/escape/10
The link that gets liked into the timeline looks like this:
=">http://guidepal.com/escape/10?fb_action_ids=10151400567746110&fb_action_types=og.likes&fb_source=timeline_og&action_object_map=%7B%2210151400567746110%22%3A10151100366393350%7D&action_type_map=%7B%2210151400567746110%22%3A%22og.likes%22%7D&action_ref_map=%5B%5D&code=AQB2NUbRhNvppL1HOqmJM6CBGQa1N3vUoK9QrPNNm516895czzIFYn93tiT4HWmBcCCrjK8tYvHqUPLAbu4mhk-xT3w17UMeTITQGnJXW3_NuyYc1Aa7FHl0nTwyuYzDS05x761boSwsGNoOpcL-ulsmiiVObacATa2NQEjLtQFrygJ81fHrSyr7pF5WWlPsf9w#=
The URL is there but there seems to be a problem, since it's adding some more stuff (which I really hope is not an access token there somewhere :P).
I'm guessing there is something wrong with the meta tags, but I have no idea what since everything seems to be okay.
Any ideas?
I've actually investigated this a bit further and this actually is because what is happening on the server side. I'm not responsible for the web-page here, but the one who is, explained that there are some bits of code that handles integer at the end of an url, he would not thought it would be a problem.
Weirdly enough it works by pressing the image instead of the URL in the recent activity.
And a hard problem to know when you are not responsible for both.
I've just liked it, and the URL came up correctly on my Timeline.
It also looks like the meta tags are set up correctly - you can check them on the linter tool that Facebook provides
I have just created a new facebook application to use in a page tab. When I check for the signed_request it is empty.
So I checked another app that I have done in the past. It is on the same server and the only difference in the setup is the dir name.
http://example.com/app1/ works
and
http://example.com/app2/ doesn't
So I tried swapping the tab URLs in the apps over and app1 still works with app2s URL.
This lead me to believe there must be a problem with the way I have set up the application.
So I went through all the settings and made sure they were the same. They all are, except there are 2 that are not available on the app I just setup. They are "Encrypted Access Token" and "Requests 2.0 efficient" neither of which seem to relate to the problem.
I seem to remember in the past there was an option to pass through the signed request to canvas page, but I can no longer find it.
Has signed request been deprecated? I couldn't see any mention of that in the docs.
Any help/comment appreciated. Otherwise I am going to have to go back and re-use old apps with new content in them, and I only have about 15 more before I run out.
Cheers
Alex
No, it wasn't deprecated.
There can be 2 issues that could cause this
You must have a trailing slash or a specific file on your page tab url.
http://myapp.com/app/
http://myapp.com/app/index.php
Your server for the second app is redirecting the request which causes it to lose the POST variables.
You should check if there aren't any redirects which usually occur form mod_rewrite. (.htaccess and such)
This seems to have been resolved now, I can no longer replicate it with new applications.
I added a like button to my site pages. It seems to work, but the debugger is giving me errors. When I try out the URL in the Object Debugger it gives the error below:
Object Base Domain Not Allowed Object at URL 'http://www.gdiy.com/projects/visiting-paris/index.php' of type 'website' is invalid because the domain 'www.gdiy.com' is not allowed for the specified application id '279134608772109'.
When I try adding the domain name in the facebook developer apps settings (https://developers.facebook.com/apps/) it is not sticking.
I enter "gdiy.com" as the domain and press enter -> then save. If I refresh the page now the domain doesn't exist anymore.
Debugger results page:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.gdiy.com%2Fprojects%2Fvisiting-paris%2Findex.php
What's wrong here? I even tried "www.gdiy.com" and that didn't work either. I also waited a couple hours before trying.
I was having the same issue. I waited a day, came back, and it seemed to be fixed. I'm not sure if this was a Facebook bug that they fixed, or if there was something else weird going on. However, time seemed to do the trick this time.
I use Chrome and doesn't work, and I try with Firefox and work it!