-
Notifications
You must be signed in to change notification settings - Fork 124
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
cannot require 'firebase' after bundle install gem 'firebase' #30
Comments
+1 |
What happens when you run |
Thanks for now we switched to a different online database and cache. [email protected] On Sun, Dec 21, 2014 at 7:17 AM -0800, "Steven Petryk" [email protected] wrote: What happens when you run bundle show firebase? — |
Did you restart your Rails server? |
I'm having the same issue. Here's my output:
Can anybody help with this? |
I've tried the same with RVM and the latest stable ruby 2.2.0p0 and I still get the error but with more information:
But they are installed correctly:
|
Loading development environment (Rails 4.2.2)
[1] pry(main)> require 'firebase'
=> false
[2] pry(main)> Firebase::Client
=> Firebase::Client → irb
irb(main):001:0> require 'firebase'
=> true
irb(main):002:0> Firebase::Client
=> Firebase::Client It works in local development and test envs, but when i run build in GitLab CI it fails with |
Hi!
rails test environment:
All working locally. But in GitLab-CI with GitLab-CI-multi-runner:
So, |
Added
But in test:
|
If i run specs with Guard on my machine there is also appears that error
|
@esergion still seeing this problem? Any chance you could help us reproduce with a simpler set of instructions? I'm unaware of |
NameError: uninitialized constant Firebase::Client I can able to load fiebase gem through console I appreciate any answers |
Try this:
Don't forget to use That's it! It works for me. |
Hi, I have a Gemfile with:
gem 'firebase'
after bundle install, when I type:
require 'firebase'
I get:
This process works for other gems....am I missing something?
The text was updated successfully, but these errors were encountered: