peterhartmanuk:

When I try to use AshAdmin and navigate to the /admin endpoint I get the error above.

I am using: {:ash, “~> 2.1”}, {:ash_admin, “~> 0.6.1”}, {:ash_phoenix, “~> 1.1”}, {:phoenix, “~> 1.6.14”}, {:phoenix_ecto, “~> 4.4”}, {:phoenix_html, “~> 3.0”}, {:phoenix_live_view, “~> 0.18”},

No doubt it is user error, any idea what I might be doing wrong? Is AshAdmin ok to use with LiveView 0.18?

ZachDaniel:

It should be! Let me try out those same dependency versions and see what happens 🙂

ZachDaniel:

Alright, so while I did find a few small fixes to make, I didn’t see anything that would cause this issue

ZachDaniel:

I set it up to use all the same versions as well

ZachDaniel:

can I see what you have in your router?

peterhartmanuk:

ZachDaniel:

🤔 that looks fine to me

ZachDaniel:

have you tried doing a mix compile --force ? Perhaps its gotten into a weird state somehow?

peterhartmanuk:

No change. 😦

peterhartmanuk:

ZachDaniel:

ohhhh

ZachDaniel:

its the scope

peterhartmanuk:

VeeWeb vs Vee ?

ZachDaniel:

its prefixing the module name that ash_admin is using with VeeWeb

ZachDaniel:

scope "/" do
  pipe_through :browser
  ash_admin "/admin"
end

scope "/", VeeWeb do
  pipe_through :browser
  get "/", PageController, :index
end

ZachDaniel:

That should fix it, moving it to its own scope w/o a module prefix

ZachDaniel:

gotta run to lunch, will check back in afterwards

peterhartmanuk:

🎉

peterhartmanuk:

Thank you so much! Is there some way I can buy you a virtual beer?

ZachDaniel:

You could sponsor the project, IIRC there is the ability to do one time sponsorships 🙂 https://github.com/sponsors/zachdaniel

peterhartmanuk:

Done. Thanks again Zach!

ZachDaniel:

Any time 🙂

ZachDaniel:

And thanks for the sponsorship!