I had a heck of time getting Avo 3.16 or later working from 3.15, it turned out to be the addition of the Config gem dependency which adds a Settings object and we had conflicting controllers using the same name. Hope this helps anyone else with the same issue 🙂 https://world.hey.com/jclarke/upgrading-avo-from-3-15-to-3-17-and-fun-with-the-config-gem-7b0e07ba

I just noticed that the

config

gem is a dependency for

universalid

, which was added last week: [avo.gemspec - Line 51](https://github.com/avo-hq/avo/blob/main/avo.gemspec#L51) Your experience doesn't sound so fun, thanks for sharing!

Hmmm. Yup. Not cool. Let’s see if we can do something about that.

Ah yeah that might fix it as well. I just left the office so can’t try it at the moment.

I wonder why universalid needs Config. 🤔 will ask Nate

yeah. Actual gem configuration

So … I think this should be a note in the docs

I imagine it’s not easy, but a gem so “low-level”, I would expect not to have that

Look: https://github.com/hopsoft/universalid/issues/39

Thanks for looking into that

Thanks for digging into this guys! I’m sure there will be others that run into this as well since Settings is a popular name to use 😀

Yeah. For sure! I use the config gem a lot and really like it and that’s why I didn’t think it would be a problem. But you have a point.

@lemon-wall-20836 So this does appear to fix it as well, created an initalizers/config.rb: Config.setup do |config| config.const_name = 'ConfigSettings' end

Thanks for the confirmation!