For any SN accounts that use graphene, has anyone noticed an inability to access SN wallet or profile after recent update? I use vanadium browser, but have the same issue with other browsers.
pull down to refresh
pull down to refresh
For any SN accounts that use graphene, has anyone noticed an inability to access SN wallet or profile after recent update? I use vanadium browser, but have the same issue with other browsers.
I wonder what i broke
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 framesDid you begin using WebAssembly recently with Rust or something?
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!
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
Can confirm this resolves the issue. Appreciate that. Zapped. Thanks
Thanks very much. That solved it.
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.
Do you get a “something went wrong” error message or anything?
No. Nothing like that. The touch screen is just non responsive for zapping and accessing the profile. I can post and reply.
maybe some fancy animation issues on the browsers on graphene?
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.
@k00b said he may remove webassembly dependencies but in the meantime you can try this:
#595622
I'm not running it now. I tried to install it in an old phone but just couldn't do it. I also tried to search for proper graphene installation process. Can you please suggest me one?
You need a Google pixel to install it. Here's a post I made:
#200175
I thought we could install it on any Android phone. 🤔 Thanks!! Now I think I first need to buy a +1000k phone for it for the first time ever. 😀
You can get an older used pixel that is still supported, but I know this isn't for everyone.
This may not be for everyone but I'm damn sure that this one's for me.
I didn't like Graphene because of it seemed to me so restrictive.
I have been using it for over a year and really enjoy it. I guess it's not for everyone. I'm sure this is just a minor situation that one of the graphene gurus on SN can explain to me. Overall, I am a big fan of graphene.
we find graphene to be far more unrestrictive
No google / apple lock-in
Yep
Maybe this isn't the best place to post it, but what happened in this discussion is really what makes SN what it is. I'm trying to broaden my knowledge of using graphene, but I'm a long way from understanding it completely. @john_doe quietly solves a problem that was driving me nuts for hours. Thanks again. I now shall zap you some more.
I am a bit late on this but reason this didn't work is because Vanadium has a toggle to block JIT (Just in Time compilation) for code which is on by default. WASM depends on it.
JIT increases attack surface for memory-related vulnerabilities. A large portion of known vulnerabilities from browsers came from the JIT engine. Many Chrome exploits in the wild or bugs discovered in contests are from JIT bugs.
Good piece about it: https://microsoftedge.github.io/edgevr/posts/Super-Duper-Secure-Mode/
Microsoft Edge also has this toggle but has an interpreter to use WASM without JIT, but it's exclusive to them right now.