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
Related
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.
I am facing strange problem, I have created two facebook apps, one about 2-3 months back and one recently 4-5 days back.
The strange problem is when I try to use graph api feed method to post to one of my pages from my old app (or default graph api of facebook) it works fine and post message to my page wall, but when I try the same with my new app it gives this error
An unexpected error has occurred. Please retry your request later.
I searched for it and found that this error comes sometimes and goes away automatically, so I waited but it is keep on coming while old app is still working on the same time.
I am using the same set of permission on both the apps
Any idea?
I want to integrate facebook api to help in the registration process in my website. It was working fine before - the standard fb login button appears, the pop-up window to login to fb was working, some of the user data are obtained. However after several trials with me modifying the code as the feature isnt fully integrated yet in my site, whenever I press the login button what replaces the fb login page is "This webpage is not available." I already retracted the modifications I made to the point that it was back to the version wherein it was working before. I also created another app and replaced the app id and secret key, still it displays the same message. I do not know what is wrong. Please help.
Update:
I uploaded the project files to another hosting site and it works! Could it be that the previous domain is now blocked?
Please read the other posts, dude... we're all waiting for the FB to fix the issue...
I'm not sure whether my fb-app is banned by automated bot. Currently with PHP-SDK, getUser() returns 0 no matter what. It all used to be working fine till a few days before. I'm getting an access token but since getUSer() is always returning NULL, the app is not working. I didn;t have much of code changes except for opengraph meta-tags, like button and google +1 button in my webpage.
Is there any way i could check if my app is not banned?
I haven't got any mail yet regarding this.
It doesn't show up in my list of apps even though i have used it recently.
But it shows up ins search.
Log into Facebook with an account that is an administrator of your app
Then navigate to: https://developers.facebook.com/apps or more directly you could go to
https://developers.facebook.com/apps/{yourAppId}/summary
I'm using the official FBConnect library for iOS and trying to get it working in my iPad app. Here's what's strange: when my friend logs in using the call to authorize:permissions:delegate, everything works fine: the dialog asks for his authorization to connect to Facebook, the fbDidLogin delegate method gets called, all is well.
However, when I try to login, the dialog never changes. The keyboard is dismissed, the password field is cleared and it just sits there. The issue is the same in both the simulator and on the device.
Here are the things I've checked and triple checked:
My login name and password are correct. If I do put in the wrong password, an "invalid username/password" message appears, and that isn't happening.
The application is not in sandbox mode.
The Application ID is correct (my friend can login without problems).
Some additional information:
Original application was created by my friend.
I created a second FB app and put in the new Application ID
My friend can login with the new Application ID
I can log in to neither.
This appears to suggest that there is something different about my friend's account, rather than the app itself.
We've been banging our heads together on this for a couple of days now. What could be causing this behaviour? Why isn't an error being generated?
Edit: It seems there are a lot of people affected by this, so in the interest of trying to find an answer, I've added a bounty.
There appears to be a server-side problem with Facebook logins as noted here:
http://github.com/facebook/facebook-ios-sdk/issues#issue/95
People have said that if they change their password on Facebook they are subsequently able to log in using the Facebook-iOS-SDK downloaded from github. Obviously that is a poor long-term solution and would be unacceptable in an app released through the App Store. On the bright side, there seem to be reports of similar login problems logging in from apps on other platforms as well.
Update: Facebook has a bug filed on this subject that can be viewed here:
http://bugs.developers.facebook.net/show_bug.cgi?id=13199