Skip to content
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

Please update the rubygems.org version to the latest version. #52

Open
zanloy opened this issue Mar 17, 2017 · 11 comments
Open

Please update the rubygems.org version to the latest version. #52

zanloy opened this issue Mar 17, 2017 · 11 comments

Comments

@zanloy
Copy link

zanloy commented Mar 17, 2017

I spent quite a while trying to figure out why my response was coming back nil before I realized the version on rubygems.org is like a year old. As soon as I pointed it to this repository, it worked great. This might help a lot more people in the future who don't want to add a bunch of github repos directory in their Gemfile.

@JustLey
Copy link

JustLey commented Mar 20, 2017

@zanloy I recent went through the issues/PRs on this repo and read somewhere that @kmrshntr will be dealing with this gems issues and release in the next weeks when he has some free time. Can't remember where, but I guess we'll have to wait. I advise you to use :github => 'kmrshntr/omniauth-slack', :ref => 'commit_number' if you need some updated code (I personally use this commit

Edit: I don't reccomend using it if you use other authentication providers because it's on version 1.3.1 of omniauth-oauth2 (I use it because I had some errors when I updated to the latest commit and Slack is my only provider)

@mauriciosouto
Copy link

Hi @zanloy

Can you share your gemfile? or any other tip.
I'm trying to use this repo (can't get user email with rubygem repo) and the only thing I can get is Could not authenticate you from Slack because "Invalid credentials".

Thanks

@zanloy
Copy link
Author

zanloy commented Mar 22, 2017

@mauriciosouto I actually forked this repo because I couldn't wait for the PR to fix a common error. But here is the line in my Gemfile:

gem 'omniauth-slack', git: 'https://github.com/zanloy/omniauth-slack.git'

@mauriciosouto
Copy link

Thanks @zanloy
I got the email working with your fork...

@adrianotadao
Copy link

I think the better is to have a new version of the gem. If we use the master, we can have problems =(

@kmrshntr could you please generate a new version? 💟

@dkniffin
Copy link

dkniffin commented Jul 3, 2017

I'd also like to see the rubygems version get bumped. @kmrshntr: it looks like you're not very active on github anymore. I don't know much about omniauth, but I have managed some ruby gems in the past. I'd be happy to help maintain this one, if you're interested.

@adrianotadao
Copy link

I can help too @dkniffin ... I have a fork here but I world like to use the rubygem version

@kevinelliott
Copy link

What is going on with this?

@alfredvaa
Copy link

I got nil as uid in the response when using this gem. Turns out I had to add the github reference in my Gemfile to make it work: gem 'omniauth-slack', github: 'kmrshntr/omniauth-slack'

It would be nice if a new version of the gem is released with the latest stuff.

@dkniffin
Copy link

Judging from @kmrshntr's activity, we might be looking at abandonware here...

@alfredvaa
Copy link

@dkniffin Yes, it looks like that. I really just wanted to leave the solution here if anyone else was wondering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants