App crashes with ANR ~30 seconds after filePicker.launch()`on Android 15

[mishbanya]

Description

After calling filePicker.launch(), the app consistently crashes with an ANR after approximately 30 seconds. The crash occurs regardless of whether the user has already selected a file or is still in the file picker dialog.

Environment

• FileKit version: 0.13.0
• Android version: 15 (AP3A.240905.015.A2) (Xiaomi HyperOS 2.0.6.0) / The issue seems to not occure on anything but this version, might be even a device problem

Steps to Reproduce

1. Use with FileKitType.File() and FileKitMode.Multiple() rememberFilePickerLauncher
2. Call launch() on the launcher
3. Wait ~30 seconds (with or without selecting files)
4. App crashes

Code to Reproduce

val filePicker = rememberFilePickerLauncher(
type = FileKitType.File(),
mode = FileKitMode.Multiple(),
onResult = { files ->
files?.let {
// handle selected files
}
}
)

// Trigger the picker
filePicker.launch()

Observed Behavior

IF user pickes a file ActivityThread logs:
fail in deliverResultsIfNeeded java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.os.Bundle.getString(java.lang.String)' on a null object reference

Regardless of what user's doing, the system's ActivityManager reports an ANR in com.google.android.providers.media.module with reason "ContentProvider not responding". The media provider process consumes ~100% CPU (96% user + 3.9% kernel) before the ANR is triggered.
Key observations from logs:

• The ANR originates in the MediaProvider system module, not in the app itself
• The app's own CPU usage is minimal (~0.9%)
• Logs are not consistently reproducible in terms of output
• Total system CPU load is only ~14%, so this is not a general system resource issue — it's isolated to the media provider process

[vinceglb]

Hi @mishbanya, thanks for the detailed report!

I tried to reproduce this but I’m not able to reproduce the crash on my side.

From the logs you shared, the ANR seems to come from Android’s MediaProvider (com.google.android.providers.media.module) and not directly from FileKit. The app CPU usage is also very low, while the media provider process is consuming almost all the CPU, so this looks more like a system/provider issue or a device/ROM-specific behavior.

To investigate further, could you please provide a minimal dedicated reproducer project that crashes consistently on your device? Ideally with only FileKit, the rememberFilePickerLauncher setup, and the smallest code needed to trigger the issue.

With that, I’ll be able to check if FileKit is doing something wrong or if this needs to be reported upstream to Android/Xiaomi