-
Notifications
You must be signed in to change notification settings - Fork 285
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
Rails 6 load fail with 1.13.1 #377
Comments
Hi @itsterry. Thanks for reporting this. Let me set up an environment similar to yours so that I can reproduce this. |
Here are my Gemfile and Gemfile.lock (NB: I had to add .txt to the filenames so Github would accept them) |
Thanks for providing that @itsterry. I see you're using the external activestorage-cloudinary-service and I suspect it clashing with the native ActiveStorage support that was added by Cloudinary with the gem in version 1.12.0+ onwards. That would explain why when downgrading to 1.11.* it works as that gem version didn't have ActiveStorage support yet. Would you be able to test this by upgrading to 1.13.1, temporary removing the external active storage gem and using the native one as part of the newer gem version; does that work? You can find the Cloudinary gem ActiveStorage documentation here - https://cloudinary.com/documentation/rails_activestorage |
Upgrading to 1.13.1 without removing activestorage-cloudinary-service - breaks (as expected - just verifying) Upgrading to 1.13.1 having removed activestorage-cloudinary-service - also breaks (Stack Trace below) Verifying that the activestorage-cloudinary-service gem has gone:
Verifying that we have activestorage in there:
Running Puma with (
Apologies for the long stack trace!! |
Thanks, @itsterry, appreciate you trying this. One of my colleagues was also trying to reproduce this, but with no avail. To get to the bottom of it quickly without going back and forth too much, I suggest if possible for you to share a minimal working rails app with as few dependencies as possible. We'll then be able to just replace the Cloudinary account credentials and all other config/code can remain so that we can reproduce and find the cause of this. |
+1 getting this error too, but on a SpreeCommerce (Rails 6) app. Reproduce steps: 1) grab the latest copy of Spree, spin up a new controller, try and run any |
Hi @jessehanley . Thanks for sharing this, I'll try it out with SpreeCommerce. Can you reproduce it without any dependencies apart from this Gem? Also, are you using the Cloudinary as an ActiveStorage service? |
I solved this issue on Rails 6 by changing the docs recommended: |
Hi there
Upgraded to 1.13.1 and get the following error on Puma boot with Rails 6.0.2.1
/Users/terry/.rvm/gems/ruby-2.6.3/gems/cloudinary-1.13.1/lib/cloudinary/helper.rb:358:in '<top (required)>': Cannot load 'Rails.config.active_storage.service': (NameError)
Reverting to 1.11.1 solves the issue.
Stack trace below.
Do let me know what else would be useful to give you
The text was updated successfully, but these errors were encountered: