Closed GoogleCodeExporter closed 8 years ago
Further to the above I'm experiencing an issue where on one device (Samsung
Galaxy S3 running 4.1.2) the user can post to LinkedIn but on another device
(Samsung Galaxy Tab 10 running 4.0.3) the user receives a URL Authentication
error running the same code:
Here's the trace:
05-14 11:28:02.859 D/SocialAuthAdapter(10672): Selected provider is linkedin
05-14 11:28:02.859 D/SocialAuthAdapter(10672): Loading keys and secrets from
configuration
05-14 11:28:02.859 W/WifiStateTracker( 187): getNetworkInfo : NetworkInfo:
type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none),
roaming: false, failover: false, isAvailable: true
05-14 11:28:02.869 I/SocialAuthConfig(10672): Loading application configuration
05-14 11:28:02.869 D/SocialAuthAdapter(10672): Starting webview for
authentication
05-14 11:28:02.869 I/LinkedInImpl(10672): Loading plugins
05-14 11:28:02.869 I/LinkedInImpl(10672): Loading plugin ::
org.brickred.socialauth.plugin.linkedin.FeedPluginImpl
05-14 11:28:02.869 I/OAuth1 (10672): Determining URL for redirection
05-14 11:28:03.619 D/SocialAuthError(10672):
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.
05-14 11:28:03.619 W/ResponseListener(10672): Sharing error
05-14 11:28:03.619 W/ResponseListener(10672):
org.brickred.socialauth.android.SocialAuthError: URL Authentication error
05-14 11:28:03.619 W/ResponseListener(10672): at
org.brickred.socialauth.android.SocialAuthAdapter$3.run(SocialAuthAdapter.java:4
23)
05-14 11:28:03.619 W/ResponseListener(10672): at
java.lang.Thread.run(Thread.java:856)
Any help would be greatly appreciated - thanks!
Original comment by gareth.t...@gmail.com
on 14 May 2013 at 2:26
HI , we have checked on Galaxy Tab 10 and its working fine
Original comment by vineet.a...@3pillarglobal.com
on 22 May 2013 at 11:37
Hi, thanks for getting back to me. We've tested on a variety of devices and
it's working fine. We're putting it down to a problem with that specific device.
Original comment by gareth.t...@gmail.com
on 22 May 2013 at 11:41
Hi, Thanks for feedback , closing this issue.
Original comment by vineet.a...@3pillarglobal.com
on 22 May 2013 at 11:59
Original comment by vineet.a...@3pillarglobal.com
on 22 May 2013 at 11:59
Original issue reported on code.google.com by
gareth.t...@gmail.com
on 8 May 2013 at 10:27