#Blank client for v2-beta.24?

5 messages · Page 1 of 1 (latest)

sharp lagoon
#

Anyone seen this behavior before? hard to debug because I can't figure out how to inspect anything....

  • App works as expected when running in Android simulator
  • App ui renders if running cargo tauri dev and opening app in the browser via defined devUrl (http://0.0.0.0:3000); jse due to tauri apis, but the js runs, and stuff renderes, so seems like it's "working"?
  • App renders a black screen for the actual cargo tauri dev window, can't open inspector, and right-click doesn't open context menu. No error logs are being shown in the console.
sharp lagoon
#

hmmm if I comment out all the plugins, and select one at a time, it renders for each one. It's almost like during app run, something is causing a crash that blows everything up, but it causes the inspector to crash as well, and the rust side isn't showing any errors.

occasionally I can open up inspector if I do it quick enough, but then it goes into this unresponsive state. And still only on MacOS; android emulator works fine.

tardy mural
#

Is this still an issue? Could you give us a list of plugins you use?

sharp lagoon
#

@tardy mural
I thought because of how it was crashing that mebbe was something rust-side (db or smthn), but actually I just discovered right now that the issue goes away if I replace my js virtual list dependency (https://github.com/inokawa/virtua) with a for loop. Removing plugins probably just caused jse prevented that code being run.

So the actual issue was probably with that? But the unexpected bit is that it could crash my app so hard that the inspector won't even open. Not sure how easy this will be to reproduce outside the context of my private repo. I can try tmrw, though (almost 10pm here rn).

#

tfw u added virtual list for performance and it instead time bomb explodes your whole app. even when i pin a known working version it crashes, so something in context changed I guess. 😭 it's what i get for taking a vacation from app dev