iOS crash choosing image

[LinKav20]

Crush in iOS in kotlin multiplatfrom project. I use this code in common feature module to select image
val image = FileKit.openFilePicker(type = FileKitType.Image)
I have image in my phone. Also my phone has icloud sync. But I can select this file in file picker and my app will crush.

I guess that happen some sync error and photo dont loaded to device from icloud. I can see and select the photo because the system displays all files that are in iCloud, regardless of whether they are downloaded or not. The crash occurs because the actual file is not present on the device.

lib version: 0.13.0
ios version: 26.3

Uncaught Kotlin exception: kotlin.IllegalStateException (message=null)
Thread: main (dispatch_main_queue)
at 4  MyApp.debug.dylib  0x10f70c453
    kfun:io.github.vinceglb.filekit.dialogs.callPhPicker$1...
    callPhPicker...invoke#internal + 695
at 5  MyApp.debug.dylib  0x10f70c8f7
    kfun:...$<bridge-DNNN>invoke(platform.Foundation.NSURL?; platform.Foundation.NSError?){}#internal + 127
    // callback signature: (NSURL?, NSError?)
at 7  MyApp.debug.dylib  0x10f70c07b
    .../filekit-dialogs/src/iosMain/kotlin/.../FileKit.ios.kt_knbridge177 + 231
at 8  PhotosUI  0x1e266d1c7  <redacted> + 383
at 9  PhotosUI  0x1e266e137  <redacted> + 191
at 11 libdispatch.dylib _dispatch_call_block_and_release + 31

[vinceglb]

Hi @LinKav20, thanks for reporting this!

I was able to reproduce the issue on the iOS gallery picker path.

The crash was happening when PHPicker failed to provide a temporary file for a selected asset. FileKit was not handling that failure correctly, especially with iCloud-backed media.

I fixed it in #536:

• picker load failures are now propagated explicitly instead of crashing or being treated like a cancellation
• Single / Multiple picker modes now throw a typed FileKitPickerException
• SingleWithState / MultipleWithState now expose a dedicated FileKitPickerState.Failed state

I also updated the sample app to handle this new failure state correctly.

openFilePicker(...) now distinguishes between user cancellation and picker load failures.
So in your case, if you call FileKit.openFilePicker(...) directly, you should also catch FileKitPickerException. This is useful because a cancelled picker still returns null, but a selected iCloud asset that cannot be downloaded or resolved is now reported as a real error instead of crashing or being treated like a cancellation.

The improvements will be available in the next FileKit release ✅