I started to receive problems with sharing from LinkedIN last week. Prior to last week shares were working fine. When I try to share an article, their share program appears to go into a loop. The linkedIN share page comes up but it just spins and spins and spins.
This is the url – encoded url and encoded title.
https://www.linkedin.com/shareArticle?mini=true&url=http%3A%2F%2Fmydomain.com%2Fcs%2F24912%2F39%2Fnull%2F93538%2F&title=Is+There+Still+a+Place+for+Print+Marketing%3F
When I look in the developer tools on chrome it appears that the page is in some kind of loop. As it keeps loading the following share page over and over…
https://www.linkedin.com/sharing/share?url=http%3A%2F%2Fmydomain%2Ecom%2Fcs%2F24912%2F39%2Fnull%2F93538%2F&title=Is+There+Still+a+Place+for+Print+Marketing%3F&trk=LI_BADGE_OLD
So I do the exact same call, just change the url to google
And it works.
I also have an app that is behaving the same way – when I post using the app – with rw permissions, I get an internal service error if I use my domain but I can post successfully using google.
Any help would be greatly appreciated.
This problem was resolved. The domain was listed in SPAMHAUS DBL (incorrectly, but that's a subject for another day). De-listed it and things are back to normal. LINKEDIN It would be great to return the real error versus an internal server error. For anyone that runs into this problem, check SMAPHAUS DBL listing.
Related
We are using LinkedIn from past few months and every thing works fine since their last API upgrade on 12th March.
Our mobile apps open linkedIn in browser every thing works fine the clients gets Authenticated and login Successfully , once they login the contacts list shows blank and error returned unauthorized
could any one know whats the reason/solution of it?
Thanks
Have Checked the new API updates that LinkedIn activated as if yesterday?
If you are pulling anything apart from Basic profile .. Location or not using the new w_share permission it will most likely be responded as a Bad request. Check the developer.LinkedIn.com for more reference
My application is running within an IFrame and has been running fine for month. Since last week, the main page keeps refreshing because it looks lie the parameters auth_token and fb_sig_session_key are not provided to my iframe content anymore.
Has anything changed on the platform lately with that regard ?
Many thanks for your support.
Jonathan.
According to the Facebook Signed Request, you are only provided oauth_tokenalong with some other data, but nothing that looks like fb_sig_session_key. Try looking through the tutorial on the signed request, as well as the other authorization tutorials on Facebook. They provide the most up to date information.
If you are still using the Legacy Canvas Auth, you'll want to read the passage there about migrating. Instead of fb_sig_session_key, you should use Use the oauth_token for all API calls.
I have a web site that gets quite a bit of traffic from Facebook. I've never had any problems sharing links to it on my Facebook page, but starting this afternoon, whenever I post a link to my web site from my facebook page, the post disappears from all users' feeds after 2-3 hours. This has happened 3 times now and I can't understand why. At first I thought it was my page itself, but it seems to be my domain because when I share from a different page (the same domain), it also disappears.
It worked fine this morning but not now. What is going on? Is this a glitch or is it some kind of system FB has in place now? This is really hurting traffic and clicks out from FB to my site.
Thank you.
Edit: looking back, it seems this may have started happening around Tuesday. Is there some kind of system in place now to limit the amount of clicks out you can get from a post? I can't see any other reason it's happening...
There are several possible causes:
Links that you use is a dynamic link which at times can be changed, use the static link. Example your link like this: http://www.domain.com/page.php?var=xxxxxxxx, where the parameter xxxxxxxx values on the links can change at any time may be due to activity updates. This will cause facebook can not find a link that has been logged.
Bandwidth & server connection you less stable.
If I may suggest, avoid links / URLs dynamically & use the SEO Friendly link/URL like this page URL http://stackoverflow.com/questions/8529022/why-are-my-links-to-my-site-disappearing-from-feeds-after-2-3-hours
I am working on implementing sharing an image via Twitter in my application and I have come across this page.
When I run my app in my simulator I can no longer log into Twitter. I get a page stating that "This page is no longer valid. It looks like someone already used the token information you provided."
I have gone to Twitter and to the Applications page and removed this application to try again. I still get this warning page though.
When I try to run the app on my device it crashes when I tap the Twitter Button.
Has anyone found a solution to this?
Or if someone could point me to a solid Twitter/TwitPic reference tutorial that actually works that would be great as well.
Check these sample twitter apps source codes, will lead you for smooth implementation,
https://github.com/bengottlieb/Twitter-OAuth-iPhone
https://github.com/luciuskwok/HelTweetica
https://github.com/takuma104/ntlniph
http://code.google.com/p/tweetero/
http://jaanus.com/post/1451098350/an-example-iphone-twitter-app
I got this problem.
Woah there!
This page is no longer valid. It looks like someone already used the
token information you provided. Please return to the site that sent
you to this page and try again. It was probably an honest mistake.
Turns out the fix for this was simple although it took some hunting down!
The date/time on the server running the app had somehow become a day behind.
Twitter checks the time sync when using the API, and if the client doesn’t have the correct time, it’ll report the above error.
Maybe you've got some loop or a method that is being called twice?
I'm trying to implement my first Facebook application, and I'm stuck on the very first coding step.
I created an application on the Facebook website, I got my application ID and I'm doing an ASP.NET app to test the authentication. It has just one line:
Response.Redirect(
"https://www.facebook.com/dialog/oauth?client_id=MYAPPID&redirect_uri=localhost");
When I run it, it redirects to facebook and I get:
An error occurred with MYAPPNAME. Please try again later.
It fetches the app name, so the ID is correct and there is very little else that I could have got wrong :-)
I also tried using other URLs instead of localhost, and I'm currently arranging for a VPS to try it with a publicly deployed web app in case it doesn't work with a local one.
Searching only found me lots of posts complaining about similar issues - but not the same one. I found this question that looks quite similar, but the confirmed answer speaks about editing FB.init() which is I guess part of some SDK, so not applicable for me.
Your redirect uri must be a url that is within the domain that you configured in your application set up. As noted in the documentation.
"The redirect_uri must be within the same domain as the Site URL you specify in Web site tab of the Developer App"