-
Notifications
You must be signed in to change notification settings - Fork 157
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
Comments
@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) |
Hi @zanloy Can you share your gemfile? or any other tip. Thanks |
@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' |
Thanks @zanloy |
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? 💟 |
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. |
I can help too @dkniffin ... I have a fork here but I world like to use the rubygem version |
What is going on with this? |
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: It would be nice if a new version of the gem is released with the latest stuff. |
Judging from @kmrshntr's activity, we might be looking at abandonware here... |
@dkniffin Yes, it looks like that. I really just wanted to leave the solution here if anyone else was wondering. |
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.
The text was updated successfully, but these errors were encountered: