[BUG] DCL via memory and storage in Grapheneos

[A4alli]

Which app is your issue for

Document Scanner

Version

https://discuss.grapheneos.org/d/19610-i-am-looking-for-a-scanning-app
please look into this bug, which cause the app to open in grapheneos

What platform are you using?

No response

OS Version

Android 16

What happened?

A bug happened!

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[farfromrefug]

@A4alli You talk about the memory permission thing ?
I think it is necessary because of the tech used to build the app (Nativescript).
Not sure i can do anything. If the grapheneos team has advice we can improve Nativescript to make it work better in grapheneos

[A4alli]

I have forwarded the concern to GrapheneOS community

[A4alli]

here the want me to share with you
https://developer.android.com/privacy-and-security/risks/dynamic-code-loading
https://kalpeshchandora12.medium.com/dynamic-code-loading-in-android-dea83ba3bc85

The second link is examples of how it can be used, maybe they followed one of those methods and they can then recognize what DCL they implemented in their app.

This link may also be helpful
https://matrix.to/#/!RRBRTYDtVLmqKAYJwn:grapheneos.org/$HCkp3d7ClQckP-RteIDFM6SsyN3qcZ4Qw6V4AOosVZ4?via=grapheneos.org&via=matrix.org&via=tchncs.de