App crashes on launch from DCL via memory error

[An-anonymous-coder]

What

• When using OpenFoodFacts on a GrapheneOS device, restricting DCL via memory will cause the app to crash on launch.

Steps to reproduce the behavior

1. Install OpenFoodFacts on a device running GrapheneOS
2. Go to Settings > Apps > OpenFoodFacts > Dynamic code loading via memory
3. Set the permission to "Restricted"
4. Open OpenFoodFacts

The app will immediately crash on launch with the following error log:

type: memory_DCL
osVersion: google/shiba/shiba:15/AP3A.241105.007/2024110700:user/release-keys
flags: dev options enabled
package: org.openfoodfacts.scanner:1364, targetSdk 34

package: org.openfoodfacts.scanner:1364

DCL denial type: DENY_EXECMEM

Expected behavior

The app should run as intended without the need for DCL via memory.

Why

Dynamic Code Loading is an opt-in security feature, used to protect against exploitation as explained here and here.

Part of

• 🎯 What can I work on ? #525

Screenshot/Mockup/Before-After

Smartphone model

• Device: Google Pixel 8
• OS: Android 15, GrapheneOS version 2024110700
• App Version: Version 4.16.1, Version Code 1364

Additional context

GrapheneOS is a privacy and security focused custom Android distribution. It offers a permission toggle to restrict the use of DCL via memory. Creating an app that does not use Dynamic Code Loading is best-practice.