After upgrading to CarrierWave 1.0+, need to reload model for file not to be nil

[cgriego]

After upgrading CarrierWave to 1.0.0.beta or higher, tests using Cloudinary + CarrierWave started failing because model.image.file were nil until the model was reloaded.

I think this person ran into the same issue.
https://stackoverflow.com/questions/46271081/carrierwave-cloudinary-image-upload-works-but-null-values-returned-right-after-u

[shirlymanor]

I apologize for the very late reply.
Unfortunately, it's a known bug in carriwave (there are a couple of open issues on GH). A workaround will be to reload as you mention.

[bbugh]

@cgriego did you make any progress with this other than forcing the model to reload? I can't find any issues in carrierwave referencing this either. Thanks!

[cgriego]

I still have the model reload workaround in place.

[shirlymanor]

Closing this issue due to the time elapsed. Please feel free to either re-open the issue, contact our support at http://support.cloudinary.com or create a new ticket if you have any additional issues.

[cgriego]

I can confirm this issue is not happening with carrierwave 1.3.1 and cloudinary 1.11.1.

[cgriego]

Sorry, yes this issue does still happen with the latest gem versions mentioned above. Please reopen.

[aceunreal]

Could this be re-opened?

[momoip]

Hi,
I have raised an internal ticket and our Dev team will be looking at this issue.
Thanks,
Mo

[david-zw-liu]

Any update?

# same here

gem 'carrierwave', '~> 2.2.2'
gem 'cloudinary', '~> 1.22.0'

[aleksandar-cloudinary]

Hi, @david-liu-950627 - Thanks for following up on this and for creating the PR. I have added one of my colleagues as a reviewer.