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.
64 sats \ 11 replies \ @k00b 3 Jul
I wonder what i broke
reply
3206 sats \ 4 replies \ @john_doe 3 Jul
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:
Did you begin using WebAssembly recently with Rust or something?
reply
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!
reply
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
Then reload and it should work
reply
138 sats \ 0 replies \ @kepford 3 Jul
Can confirm this resolves the issue. Appreciate that. Zapped. Thanks
reply
21 sats \ 0 replies \ @siggy47 OP 3 Jul
Thanks very much. That solved it.
reply
21 sats \ 5 replies \ @siggy47 OP 3 Jul
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
54 sats \ 0 replies \ @john_doe 3 Jul
@k00b said he may remove webassembly dependencies but in the meantime you can try this:
#595622
reply
54 sats \ 3 replies \ @k00b 3 Jul
Do you get a āsomething went wrongā error message or anything?
reply
10 sats \ 0 replies \ @dollarparity 3 Jul
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
50 sats \ 1 reply \ @siggy47 OP 3 Jul
No. Nothing like that. The touch screen is just non responsive for zapping and accessing the profile. I can post and reply.
reply
54 sats \ 0 replies \ @WeAreAllSatoshi 3 Jul
maybe some fancy animation issues on the browsers on graphene?
reply
71 sats \ 0 replies \ @kepford 3 Jul
Yep
reply
65 sats \ 4 replies \ @Coinsreporter 3 Jul
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?
reply
54 sats \ 3 replies \ @siggy47 OP 3 Jul
You need a Google pixel to install it. Here's a post I made:
#200175
reply
65 sats \ 2 replies \ @Coinsreporter 3 Jul
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. š
reply
22 sats \ 1 reply \ @siggy47 OP 3 Jul
You can get an older used pixel that is still supported, but I know this isn't for everyone.
reply
65 sats \ 0 replies \ @Coinsreporter 3 Jul
This may not be for everyone but I'm damn sure that this one's for me.
reply
54 sats \ 2 replies \ @BitcoinAbhi 3 Jul
I didn't like Graphene because of it seemed to me so restrictive.
reply
161 sats \ 1 reply \ @siggy47 OP 3 Jul
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.
reply
64 sats \ 0 replies \ @learnportuguese 3 Jul
we find graphene to be far more unrestrictive
No google / apple lock-in
reply
21 sats \ 1 reply \ @siggy47 OP 3 Jul
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.
reply
0 sats \ 0 replies \ @final 13 Jul
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.
reply