F-Droid Crash Report Dialog Appearing During Long-Running Test

1

Dear F-Droid Team,

Hello,

We are observing an issue with the crash report dialog (ACRA) appearing on some devices during long-term testing, and would like to better understand the underlying cause.

Background

We conducted a 4-day continuous test on approximately 200 Android devices.
During this period, 13 devices repeatedly showed the F-Droid crash report dialog.

It said “F-Droid has crashed”.

Device Information

  • Device model: rockchip px30_evb

  • Android version: 8.1

  • F-Droid version: 1.21.1

  • RAM: 1.9 GB

Storage status:

Filesystem            Size  Used Avail Use% Mounted on
rootfs                970M  3.2M  967M   1% /
tmpfs                 979M  488K  979M   1% /dev
/dev/block/mmcblk1p11 1.4G  1.3G   15M  99% /system
/dev/block/mmcblk1p13 350M  335M  3.4M  99% /vendor
tmpfs                 979M     0  979M   0% /mnt
/dev/block/mmcblk1p14 228M   27M  193M  13% /oem
/dev/block/mmcblk1p10 356M  1.7M  343M   1% /cache
/dev/block/mmcblk1p12  11M  6.2M  4.7M  58% /metadata
/dev/block/mmcblk1p20 3.3G  1.7G  1.5G  55% /data
/data/media           3.3G  1.7G  1.5G  55% /storage/emulated

Logs

We were only able to capture one relevant log (it is unclear whether other occurrences share the same cause):

java.io.FileNotFoundException:
/data/user/0/org.fdroid.fdroid/app_ACRA-unapproved/2026-04-03T02:55:11.654+08:00.stacktrace (No such file or directory)

Questions

We would like to understand the root cause category behind the crash dialog behavior (application-level vs. system/hardware-related), specifically:

  1. Under what conditions is the ACRA crash report dialog triggered in F-Droid?
    Is it always the result of an actual application crash?

  2. Regarding the FileNotFoundException above:
    What is the typical cause of this error in ACRA?
    Does it indicate:

    • a failure to generate the crash report file, or

    • that the file was removed before being accessed?

  3. Could this issue be related to device or hardware conditions?
    For example:

    • storage performance or filesystem behavior

    • memory constraints

    • long-running system stability

    Or is it more likely to be purely an application-level issue?

Thank you for your time and support.

Best regards,

2

We’ve answered the email.

Upgrade to 1.23.2, save the actual ACRA stacktrace (send email to yourself, save it).

Your provided logs.rar don’t have the needed info.

How do you test exactly? Automated scripts touch the screen at random?

After upgrading to 1.23.2 try to enable latest Beta (upper menu) and test latest 2.0 which we focus on.

3

Thank you for your response and for the guidance.

We will put the app in the background and leave it there for several days without screen off.

Once we are able to reproduce the issue, we will provide feedback immediately.