Allow cancelling operation when FilePickerStatus is 'picking'. Useful when picking large cloud files

[vinith]

There doesn't seem to be a way to cancel the operation when user picks large cloud files. It would be nice to have the ability to cancel the operation so user can pick files again.

Right now you get

I/flutter (24311): [MethodChannelFilePicker] Platform exception: PlatformException(already_active, File picker is already active, null, null) when attempting to pick files when the operation is not cancelled and still active.

[miguelpruivo]

Are you experiencing this on Android or iOS?

[vinith]

Android

[miguelpruivo]

Have you managed to fix it?

[vinith]

This isn't a priority for me. I am just building something for fun. It felt like an important feature to have so I suggested it.

[github-actions[bot]]

This issue is stale because it has been open for 14 days with no activity.

[aris-1]

I also need a way to cancel/destroy/restart File picker. I the user gets a large file from the cloud, it can take long. So I give him the option to cancel. The problem is that if he tries to upload another file we get the exception already_active, until the previous file is downloaded from the cloud. Is there a way to restart picker or cancel previous busy one?

[miguelpruivo]

@aris-1 currently there isn’t. But it could make sense to add.

[Kashifalaliwala]

@miguelpruivo Is there any update on this issue?

[ItsYasser]

this feature should definitely be added , is there any updates on how to achieve canceling the operation ?

[riyan-dcosta]

I faced same issue. need to close existing instance. Cloud video was not downloaded and now I cannot re-download it. error : Unhandled Exception: PlatformException(already_active, File picker is already active, null, null)

[BrianMwas]

I am also facing the issue, hopefully it can be fixed

[Pluxury]

I also ran into this problem. In addition, on android < 33, the picker does not open after requesting permissions to access the storage and calling FilePicker.platform.pickFiles() again leads to the mentioned error. The possibility of canceling the task could solve this problem.