undefined method `attachment_reflections' for nil:NilClass when removing an entry with Active Storage with variants from console

[juansecaro]

Steps to reproduce

Building a scaffold with an Active Storage image and at least 1 variant in a view throw this error when destroy.

In console it happens everytime, in the browser I have this error 1 time but I haven't been able to reproduce.

All images are still found after destroy in the system

Expected behavior

After detroy the image and its variants should be removed silently and without throwing any error.

Actual behavior

An error is thrown and all the images are still in the folder storage

System configuration

Rails version: 6.1.0

Ruby version: 2.7.2

[josh-m-sharpe]

Ah - it's because you're using UUID primary keys and the ActiveStorage relations default to integers.

See this issue and my fix at the bottom: #40986

[josh-m-sharpe]

[filipjakubowski]

I had attachment_reflections errors for Nil class as well using rails 6.1. Error was not on deleting but processing variant.

gem 'rails', '~> 6.1.0'
gem 'image_processing', '~> 1.2'

updating imagemagic solved problem (MAC)
brew upgrade imagemagick ( or install if you have not done it before )

[juansecaro]

I have this version (1.2) of image_processing and the problem keep going. It looks like @josh-m-sharpe is right and it's related to having UUID as a primary id. It's good to know that not using UUID is a work around, but I wonder if there is an easy fix to this.

[korkey128k]

I've fixed this with a migration to remove the record_id column from active_storage_attachments and add it back with the :uuid option.

class ChangeActiveStorageRecordReferencesToUuid < ActiveRecord::Migration[6.1]
  def change
    remove_column :active_storage_attachments, :record_id
    add_column :active_storage_attachments, :record_id, :uuid, null: false
  end
end

You could also fix this by adding type: :uuid to the record_id reference in the initial migration.
This seems to work fine, but not fully confident it wouldn't have side effects. YMMV.

[juansecaro]

I have decided to stick to default BigInt, but thanks for your help guys. Knowing the reason and an alternative solution is enough for me, but I don't feel 100% safe knowing it could be a source of pain and incompatibilities in the future win gems and integrations so I will take this time the safe road.

[rails-bot]

This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails team are limited, and so we are asking for your help.
If you can still reproduce this error on the 6-1-stable branch or on main, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.

[ahanel13]

This is still an issue as of today

[zzak]

Related to #40986

[donmb1]

add_column :active_storage_attachments, :record_id, :uuid, null: false

this solved it for me. But what if we have one model using ActiveStorage which has Integer as primary key and one has uuid? Seems like it cannot be mixed but its a common usecase.

[reinaldonunes]

I've fixed this with a migration to remove the record_id column from active_storage_attachments and add it back with the :uuid option.

class ChangeActiveStorageRecordReferencesToUuid < ActiveRecord::Migration[6.1]
  def change
    remove_column :active_storage_attachments, :record_id
    add_column :active_storage_attachments, :record_id, :uuid, null: false
  end
end

You could also fix this by adding type: :uuid to the record_id reference in the initial migration. This seems to work fine, but not fully confident it wouldn't have side effects. YMMV.

I had the same problem just now, I applied your resolution and it worked perfectly o/