odd
LiveViewNative compilation error: (CaseClauseError) no case clause matching: :text
Hey!
I can’t get LiveViewNative running
the following error pops up when running mix.
== Compilation error in file lib/live_view_native/component.ex ==
** (CaseClauseError) no case clause matching: :text
(phoenix_live_view 1.0.4) lib/phoenix_live_view/tokenizer.ex:117: Phoenix.LiveView.Tokenizer.tokenize/5
lib/live_view_native/tag_engine.ex:33: LiveViewNative.TagEngine.handle_text/3
(eex 1.17.3) lib/eex/compiler.ex:317: EEx.Compiler.generate_buffer/4
expanding macro: LiveViewNative.Component.sigil_LVN/2
lib/live_view_native/component.ex:315: LiveViewNative.Component.csrf_token/1
could not compile dependency :live_view_native, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile live_view_native --force", update it with "mix deps.update live_view_native" or clean it with "mix deps.clean live_view_native"
I’m running the latest versions of everything.
Thank you!
Marked As Solved
ruslandoga
![]()
Might be related: Track braces state in tokenizer, closes #3613 · phoenixframework/phoenix_live_view@603c8ec · GitHub
Maybe lowering phoenix_live_view version to 1.0.1 would make it work?
Also it might make sense to open an issue on GitHub - liveview-native/live_view_native: A framework for building native applications with Phoenix LiveView · GitHub since they might need to update something to adapt to that {:text, braces} phoenix_live_view commit.
UPDATE: Ah, maybe they already have: LiveView 1.0.2 · liveview-native/live_view_native@ebaa67b · GitHub – are you certain you are using the latest live_view_native?
Also Liked
odd
Oh I see, downgrading to 1.0.1 does work. I’m using the live_view_native versions mentioned in the readme
live_view_native 0.4.0-rc.0
live_view_native_live_form 0.4.0-rc.0
live_view_native_stylesheet 0.3.2
live_view_native_swiftui 0.4.0-rc.0
but it’s behind main, so I don’t have the commit you linked. Anyhow, this solves the issue, thanks a lot!
kklisura
Can you post results of mix deps.tree (without this new change). Is it possible that some other dependency forced some specific version?
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #javascript
- #code-sync
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








