-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this gem still maintained? #268
Comments
There is a ticket somewhere basically saying that this gem isn’t supported
much anymore.
You can always submit a PRThough if you find an issue that you want to fix.
-Matt
…On Wed, Jan 10, 2018 at 12:28 AM Sasha Cooper ***@***.***> wrote:
I tried installing it and setting up an application on LinkedIn's website,
but
a) the terminology doesn't quite match the docs here (eg there I have a
'Client ID' and a 'Client Secret' vs the 'your_consumer_key',
'your_consumer_secret' placeholders in the examples here; and
b) When I call client.profile or client.network_updates using those
values anyway, I get a LinkedIn::Errors::NotFoundError: (404): Not Found
error (not a 401 as I'd expect if I'd just entered the wrong auth)
Am I doing something wrong, or is the gem out of date now? If the latter,
could you update the ReadMe with a note to that effect?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#268>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIdDnu8GzKu-8wQ1t35Xsp5UokW8m1eks5tI6GqgaJpZM4RYLUu>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried installing it and setting up an application on LinkedIn's website, but
a) the terminology doesn't quite match the docs here (eg there I have a 'Client ID' and a 'Client Secret' vs the 'your_consumer_key', 'your_consumer_secret' placeholders in the examples here; and
b) When I call
client.profile
orclient.network_updates
using those values anyway, I get aLinkedIn::Errors::NotFoundError: (404): Not Found
error (not a 401 as I'd expect if I'd just entered the wrong auth)Am I doing something wrong, or is the gem out of date now? If the latter, could you update the ReadMe with a note to that effect?
The text was updated successfully, but these errors were encountered: