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?
reply
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!
reply
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
Then reload and it should work
reply
Can confirm this resolves the issue. Appreciate that. Zapped. Thanks
reply
Thanks very much. That solved it.
reply
I'm not sure it's an SN issue. Graphene had an update yesterday too. I tried different browsers. SN works fine on stock Android.
reply
@k00b said he may remove webassembly dependencies but in the meantime you can try this: #595622
reply
Do you get a “something went wrong” error message or anything?
reply
I’ve had similar problems when using iOS on Lockdown mode. It also doesn’t allow you to post images. But I suppose that’s a feature not a bug in that case, but could help narrows down what is going on with Graphene.
reply
No. Nothing like that. The touch screen is just non responsive for zapping and accessing the profile. I can post and reply.
reply
maybe some fancy animation issues on the browsers on graphene?
reply