Saving and loading don't work in Brushworkvr app

[elima]

Configuration

Wolvic version: 0.9.5
Wolvic build ID: f967856 (AC 63.0.0)
Hardware: Oculus Quest 2

Steps to Reproduce

1. Navigate to https://brushworkvr.com/ and enter VR.
2. Save current painting under any name.
3. Close the tab or window.
4. Open again https://brushworkvr.com/ and try to load previously saved painting.

Current Behavior

Cannot load previous painting. The list is empty.

Expected Behavior

The previous painting is listed and can be loaded again.

Comments

Works fine on Oculus Browser.

[svillar]

Reported upstream https://bugzilla.mozilla.org/show_bug.cgi?id=1772872

[svillar]

Some data I got from inspector

Uncaught TypeError: can't access property "width", t is null
    draw paint_head.74387f4764358f6ed61a.js:394
    setPainting paint_head.74387f4764358f6ed61a.js:175
    wrapRender paint_head.74387f4764358f6ed61a.js:687
    setPainting paint_head.74387f4764358f6ed61a.js:175
    onLoadPainting paint_head.74387f4764358f6ed61a.js:1
    loadExistingPainting paint_head.74387f4764358f6ed61a.js:1
    t paint_head.74387f4764358f6ed61a.js:1
    t paint_head.74387f4764358f6ed61a.js:1
    n paint_head.74387f4764358f6ed61a.js:1
    promise callback*s paint_head.74387f4764358f6ed61a.js:1
    n paint_head.74387f4764358f6ed61a.js:1
    promise callback*s paint_head.74387f4764358f6ed61a.js:1
    n paint_head.74387f4764358f6ed61a.js:1
    promise callback*s paint_head.74387f4764358f6ed61a.js:1
    n paint_head.74387f4764358f6ed61a.js:1
    promise callback*s paint_head.74387f4764358f6ed61a.js:1
    n paint_head.74387f4764358f6ed61a.js:1
    promise callback*s paint_head.74387f4764358f6ed61a.js:1
    n paint_head.74387f4764358f6ed61a.js:1
    promise callback*s paint_head.74387f4764358f6ed61a.js:1
    f paint_head.74387f4764358f6ed61a.js:1
    f paint_head.74387f4764358f6ed61a.js:1
    loadExistingPainting paint_head.74387f4764358f6ed61a.js:1
    load paint_head.74387f4764358f6ed61a.js:1
    t paint_head.74387f4764358f6ed61a.js:1
    t paint_head.74387f4764358f6ed61a.js:1
    f paint_head.74387f4764358f6ed61a.js:1
    f paint_head.74387f4764358f6ed61a.js:1
    load paint_head.74387f4764358f6ed61a.js:1
    tick paint_head.74387f4764358f6ed61a.js:1
    Aframe 19

[javifernandez]

The bug is still reproducible in latest main branch (1.5 version code 110)

However, the paintings are actually saved, although I couldn't add a Name. The problem is that when trying to load them, I don't see any name (just N empty boxes) and I can't click on any of them to load it.

[HollowMan6]

However, the paintings are actually saved, although I couldn't add a Name. The problem is that when trying to load them, I don't see any name (just N empty boxes) and I can't click on any of them to load it.

Checked how it works in the Oculus browser, looks like it should display a picture in those empty boxes. So I suspect the culprit is the cache again, something similar to here: #353

[svillar]

However, the paintings are actually saved, although I couldn't add a Name. The problem is that when trying to load them, I don't see any name (just N empty boxes) and I can't click on any of them to load it.

Checked how it works in the Oculus browser, looks like it should display a picture in those empty boxes. So I suspect the culprit is the cache again, something similar to here: #353

I've just checked the Meta Browser and it behaves as Wolvic. I also tried Wolvic with Chromium backend and I still see the empty boxes. I think the problem is the application. Could you @HollowMan6 confirm that this is what you see?

[HollowMan6]

However, the paintings are actually saved, although I couldn't add a Name. The problem is that when trying to load them, I don't see any name (just N empty boxes) and I can't click on any of them to load it.

Checked how it works in the Oculus browser, looks like it should display a picture in those empty boxes. So I suspect the culprit is the cache again, something similar to here: #353

I've just checked the Meta Browser and it behaves as Wolvic. I also tried Wolvic with Chromium backend and I still see the empty boxes. I think the problem is the application. Could you @HollowMan6 confirm that this is what you see?

Now I tried this on the Meta browser again. Looks like the app is broken with empty boxes now even on the Meta browser. I do remember it worked with pictures being displayed in those boxes on the Meta browser at that time...