Unable to parse state from OAuth query about meteor-accounts-linkedin

[PoBuchi]

Hi,
I am on the road atm, i will take a look tomorrow

[landland]

hi @PauliBuccini have you had a chance to look at this?

[wulfmeister]

Getting this error as well.

[rrova]

I'm getting this error also.

[gwendall]

+1

[wulfmeister]

It works for me after adding the code in this PR: PoBuchi/meteor-linkedin#2

[rrova]

That worked for me also.

[wulfmeister]

Great! I'm glad :)

[0o-de-lally]

This still happens occasionally on local env. It will work after >meteor reset

Packages:
accounts-facebook 1.0.4 Login service for Facebook accounts
accounts-google 1.0.4 Login service for Google accounts
accounts-ui-unstyled 1.1.7 Unstyled version of login widgets
houston:admin 2.0.3 A zero-config Meteor Admin
iron:router 1.0.7 Routing specifically designed for Meteor
meteor-platform 1.2.2 Include a standard set of Meteor packages in your app
pauli:accounts-linkedin 1.1.2 Accounts service for LinkedIn accounts
service-configuration 1.0.4 Manage the configuration for third-party services

[PoBuchi]

Hi @keyscores ,
well it is a bit strange, currently I am on the road and hitting deadlines on some work, but hopefully within week, I go through package and will look for any inconsistencies.

[0o-de-lally]

Thanks for the help. I'm seeing an issue with production as well, and it's failing silently (no console logs).

Click login -> Sends to Linkedin -> back to page without having logged in (or any db inserts).

Are there any logs anywhere?

[timmakken]

The comment from @wulfmeister helped me getting access to login with linkedin however as @keyscores is saying the login on the app does not actually work after logging in with linkedin.

[wulfmeister]

The package has since been updated beyond my PR. I'm using the normal atmosphere version now, and it's working great. Are you using an older version with my PR?

[timmakken]

Just tested , and it works with the new update 👍 Great job , and i am very happy to see this package is kept up to date!

[wulfmeister]

👍

[0o-de-lally]

I haven't had this issue in a long time. Been trying to replicate, but never produced the error again.
From my point of view this ticket can be closed.