{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifwvt3d2uoycb7wzzryldyagdltrzktijya4bdtsf7lnyo23pvokq",
    "uri": "at://did:plc:34cg4tn4iwemk3v5k3n3adwf/app.bsky.feed.post/3mj67o6p42zl2"
  },
  "path": "/t/f-droid-crash-report-dialog-appearing-during-long-running-test/34265#post_1",
  "publishedAt": "2026-04-10T10:24:53.000Z",
  "site": "https://forum.f-droid.org",
  "textContent": "Dear F-Droid Team,\n\nHello,\n\nWe 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.\n\n* * *\n\n## Background\n\nWe conducted a 4-day continuous test on approximately 200 Android devices.\nDuring this period, 13 devices repeatedly showed the F-Droid crash report dialog.\n\nIt said “F-Droid has crashed”.\n\n* * *\n\n## Device Information\n\n  * Device model: **rockchip px30_evb**\n\n  * Android version: **8.1**\n\n  * F-Droid version: 1.21.1\n\n  * RAM: **1.9 GB**\n\n\n\n\nStorage status:\n\n\n    Filesystem            Size  Used Avail Use% Mounted on\n    rootfs                970M  3.2M  967M   1% /\n    tmpfs                 979M  488K  979M   1% /dev\n    /dev/block/mmcblk1p11 1.4G  1.3G   15M  99% /system\n    /dev/block/mmcblk1p13 350M  335M  3.4M  99% /vendor\n    tmpfs                 979M     0  979M   0% /mnt\n    /dev/block/mmcblk1p14 228M   27M  193M  13% /oem\n    /dev/block/mmcblk1p10 356M  1.7M  343M   1% /cache\n    /dev/block/mmcblk1p12  11M  6.2M  4.7M  58% /metadata\n    /dev/block/mmcblk1p20 3.3G  1.7G  1.5G  55% /data\n    /data/media           3.3G  1.7G  1.5G  55% /storage/emulated\n\n\n* * *\n\n## Logs\n\nWe were only able to capture one relevant log (it is unclear whether other occurrences share the same cause):\n\n\n    java.io.FileNotFoundException:\n    /data/user/0/org.fdroid.fdroid/app_ACRA-unapproved/2026-04-03T02:55:11.654+08:00.stacktrace (No such file or directory)\n\n\n\n\n\n* * *\n\n## Questions\n\nWe would like to understand the root cause category behind the crash dialog behavior (application-level vs. system/hardware-related), specifically:\n\n  1. **Under what conditions is the ACRA crash report dialog triggered in F-Droid?**\nIs it always the result of an actual application crash?\n\n  2. **Regarding the FileNotFoundException above:**\nWhat is the typical cause of this error in ACRA?\nDoes it indicate:\n\n     * a failure to generate the crash report file, or\n\n     * that the file was removed before being accessed?\n\n  3. **Could this issue be related to device or hardware conditions?**\nFor example:\n\n     * storage performance or filesystem behavior\n\n     * memory constraints\n\n     * long-running system stability\n\nOr is it more likely to be purely an application-level issue?\n\n\n\n\n* * *\n\nThank you for your time and support.\n\nBest regards,",
  "title": "F-Droid Crash Report Dialog Appearing During Long-Running Test"
}