All responses are 409 about inertia-laravel

[JIscariot]

Use @inertiajs/inertia-vue3 instead of @inertiajs/vue3

[reinink]

Yes, this is caused by asset versioning. A 409 response is sent when your assets are out of date. You can use this to force an asset update, which is really helpful!

[grantholle]

Does this happen automatically or will I need to include

Inertia::version(function () {
    return md5_file(public_path('mix-manifest.json'));
});

in my AppServiceProvider? This behavior has started relatively recently when it had been working fine. This behavior is good when it's needed, I just don't know why it has started suddenly.

[reinink]

No, it doesn't happen automatically. It should only happen if you're using Inertia::version(). Are you not using this?

[grantholle]

Actually I just realized I had it already. Removing it solves my issue 🤷‍♂️

[reinink]

Okay cool. I would recommend not removing it, as this is very helpful behaviour if you're using code splitting.

[grantholle]

Yes absolutely. I just figured out what is happening.

I've extended Inertia to support API resources (#70), and the middleware isn't using my class, therefore not my version! Adding in the additional version() call resolves everything...

Thanks so much Jonathan!

[marcuschristiansen]

@reinink I have a similar issue but it keeps refreshing every time. What do I do to bring these assets up-to-date?

[yamchinghann]

@reinink I have a similar issue but it keeps refreshing every time. What do I do to bring these assets up-to-date?

i have similar your issue as well but i have solved it by modifying this code line at HandleInertiaRequests.php file
public function version(Request $request): ?string { //return parent::version($request); return ''; }

[marcuschristiansen]

@reinink I have a similar issue but it keeps refreshing every time. What do I do to bring these assets up-to-date?

For me this was an issue with the fact that we have a load balancer in place. Using sticky sessions resolved it for us.