reply on: Graphene Issue Accessing SN? \ stacker news ~tech

pull down to refresh

3206 sats \ 4 replies \ @john_doe 3 Jul \ parent \ on: Graphene Issue Accessing SN? tech

I am unsure if it is your fault or our fault, but anyway here is the error message I get by debugging from the desktop:

ReferenceError: WebAssembly is not defined
    at 8713 (index.js:2:172136)
    at r (index.js:2:198243)
    at index.js:2:198464
    at index.js:2:198464
    at index.js:2:65
    at 34503 (index.js:2:230)
    at __webpack_require__ (bootstrap:21:1)
    at 36872 (lnbits.js:210:1)
    at __webpack_require__ (bootstrap:21:1)
    at 22413 (user-popover.js:49:1)
Promise.then (async)		
__webpack_require__	@	bootstrap:21
__webpack_require__.O	@	chunk loaded:25
l	@	jsonp chunk loading:73
(anonymous)	@	main-ae7fbb58e20fc278.js:1
Show 7 more frames

Did you begin using WebAssembly recently with Rust or something?

21 sats \ 3 replies \ @k00b 3 Jul

There are a few packages we use that rely on web assembly. I'll try and see if I can make it optional. Thanks for finding it!

2392 sats \ 2 replies \ @john_doe 3 Jul

Ah I see. siggy47 said below there was an update as well from GrapheneOS. Apparently JavaScript JIT is disabled and we need to add an exception. So solution: Open Vanadium -> Settings -> Site Settings -> Scroll around the middle and under Content go to JavaScript JIT -> Add site exception -> add Stacker.news