DeletedUser48 There's already an issue open for this: https://github.com/simplex-chat/simplex-chat/issues/4810. I've tried it as well and I also get the same errors and the app also crashes for me sometimes.
Ultimately, they will need to fix it on their end.
Can anyone confirm if this issue still exists? I turned off DCL via Memory and DCL via Storage for SimpleX, which previously always resulted in a crash, but it is not crashing anymore.
Edit: nevermind, DCL via Storage crash occurred again.
doesn't seem to be resolved yet. crashes in couple seconds.
Onlyfun doesn't seem to be resolved yet.
That would be consistent with the issue that @other8026 provided the link to.
I believe the situation could be summarized as:
People using SimpleX on GrapheneOS might want to allow DCL via storage via the toggle, and might also want to check back on the linked SimpleX issue every few months to find out if it's safe to switch the toggle back.
de0u It's worth noting blocking dynamic code loading is opt-in for user installed apps. People are choosing to enable it. When users enable blocking it by default, we also have automatic exceptions for apps using Google Play services until they move away from the old style dynamite modules requiring it. People can still opt-in to disabling it for those apps.
GrapheneOS It's worth noting blocking dynamic code loading is opt-in for user installed apps. People are choosing to enable it.
Thanks for the clarification! I just turned on blocking to see what it might turn up.
de0u You can also see that it doesn't turn on the DCL via Storage blocking for apps depending on Google Play services without manually doing it for each of those. It will work for some of those but not others, depending on if they use any dynamite modules not yet converted to split APKs. Our plan is to remove that automatic exception once Google phases out the older approach but that might take years.
de0u thank you for clarification.
I assume gos implemented DCL blocking for a good reason. for me having to use a 'pixel' device is a major price to pay for ability to use gos. and breaking gos safety with some messenger acting in a malicious manner is nonsense imo.
i'll rather keep it disabled and check if the issue is fixed from time to time per your advice.
Onlyfun breaking gos safety with some messenger acting in a malicious manner is nonsense imo.
Malicious? Based on what SimpleX's lead developer said in this comment, it sounds like they're doing it this way to keep the apk small. He said:
We might be able to stop using DCL at the cost of increasing the downloadable app size to ~200mb.
I'm not sure what they're loading, or how they're verifying the integrity of what the app is downloading. Regardless, I don't think the word "malicious" is warranted here.
GrapheneOS depending on if they use any dynamite modules not yet converted to split APKs. Our plan is to remove that automatic exception once Google phases out the older approach but that might take years
I know Chrome uses isolated splits (aab). I haven't been paying attention, but what's the new approach? And is Chrome/Chromium/Vanadium using those already?
other8026 Malicious?
my bad, 'malicious' is not the right word here, I meant 'potentially harmful' since there is a
warning about app's exploit protection weakening when allowing the DCL both memory/storage.
so far there are 2 apps requiring DCL to function, and which I cannot replace but at the same time need them only a couple times a month, hence the DCL permission can be granted/revoked each time they're used or even whole app enabled/disabled.
i'm glad GOS allows such precise security control, while keeping compatible with apps.
