How to downgrade phoenix liveView js asset version to 0.20.17?

Questions & Help Questions
,
1

I am currently seeing the following log in the the browser console:

LiveView assert version mismatch. Javascript version 1.0.0-rc.6 vs. server 0.20.17. To avoid issues, please ensure that your assets use the same version as the server.

How do I downgrade the javascript assets version to 0.20.17?

2

What LiveView version do you have in your mix.exs? A clean build/redeploy should realign your asset version.

3

The mix file has version 0.20.17

{:phoenix_live_view, "~> 0.20.17"},
4

I’d do a mix deps.get to make sure your dependencies under /deps are aligned with mix.exs, and then a mix assets.build to rebuild your JS bundle.

If that’s not enough, clean potentially stale files from /_build using mix clean --deps.

5

Another thing that might be at play is browser cache. If you’re developing your app, you can clear the cache for localhost or open the dev tools in your browser and disable cache.

6

Also make sure whatever bundler you’re using is not caching the js of phoenix code somewhere.

7

@rhcarvalho Thank you for your suggestions but none of them work.

@LostKobrakai I am using the default esbuild installed by phoenix.

8

Fixed by specifying the path to the phoenix live view import.
Replaced

import {LiveSocket} from "phoenix_live_view"

with

import {LiveSocket} from "../../deps/phoenix_live_view"
9

Had this problem but in the other way around, upgraded to lv 1.0.3 and javascript was complaining about being on 0.20.17. Fixed it by just deleting the files inside /priv/assets/ and rebuilding assets by mix assets.build in case anyone has the same problem.

10

Hello, i know this is an old thread but i want to add another item to look at. I got the same message on completely new upgraded version of Phoenix with clean and new project. However still got the

asset version mismatch. JavaScript version 1.0.10 vs. server 1.1.17. To avoid issues, please ensure that your assets use the same version as the server.

The issue was with deploying it to already present nginx configuration where i had caching enabled. After i removed the caching then error disappeared. So another item to watch is your proxy and if any caching is set along the way.