didierjc / socialauth-android

Automatically exported from code.google.com/p/socialauth-android
0 stars 0 forks source link

LinkedIn - SocialAuthConfigurationException #224

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Login with LinkedIn
2.
3.

What is the expected output? What do you see instead?
Login screen is the expected output. It shows following error log in logcat:

SocialAuthError

org.brickred.socialauth.exception.SocialAuthConfigurationException: Application 
keys are not correct. The server running the application should be same that 
was registered to get the keys.

What version of the product are you using? On what operating system?
socialauth-4.4jar and socialauth-android-3.2.jar.

Please provide any additional information below.

Original issue reported on code.google.com by praveen....@gmail.com on 3 Jun 2015 at 5:49

GoogleCodeExporter commented 8 years ago
This is the logs in logcat.....

06-03 23:15:39.490: D/SocialAuthAdapter(591): Selected provider is linkedin
06-03 23:15:39.540: D/SocialAuthAdapter(591): Starting webview for 
authentication
06-03 23:15:39.640: I/LinkedInImpl(591): Loading plugins
06-03 23:15:39.640: I/LinkedInImpl(591): Loading plugin :: 
org.brickred.socialauth.plugin.linkedin.FeedPluginImpl
06-03 23:15:39.640: I/LinkedInImpl(591): Loading plugin :: 
org.brickred.socialauth.plugin.linkedin.CareerPluginImpl
06-03 23:15:39.640: I/OAuth1(591): Determining URL for redirection
06-03 23:15:41.170: D/SocialAuthError(591): 
org.brickred.socialauth.exception.SocialAuthConfigurationException: Application 
keys are not correct. The server running the application should be same that 
was registered to get the keys.
06-03 23:15:41.180: W/System.err(591): 
org.brickred.socialauth.android.SocialAuthError: URL Authentication error
06-03 23:15:41.180: W/System.err(591):  at 
org.brickred.socialauth.android.SocialAuthAdapter$4.run(SocialAuthAdapter.java:6
53)
06-03 23:15:41.180: W/System.err(591):  at java.lang.Thread.run(Thread.java:856)

Original comment by praveen....@gmail.com on 3 Jun 2015 at 5:51