Does not work with Telegram flatpak - file is empty and cannot be sent

[ArtikusHG]

This does not happen when drag and dropping from nautilus or any other app.

[RoNiN-shadow]

Hi! I use ripdrag reqularly and I'd love to look into this issue as my first contribution.

I think this is related to Flatpak's sandbox permissions. It may lack specific MIME type like text/uri-list or an incorrect URI format compared to what Nautilus sends.

I'll try to reproduce this locally. Let me know if you have any pointers on where drag-n-drop payload is constructed in the codebase.

[ArtikusHG]

Sadly I'm just a user too. Not even a regular user - I was just playing around with yazi and decided to test whether ripdrag integration works well, and it didn't with one of the main apps I use.

I'm pretty sure it's the permissions, too, but what's weird is it's only Telegram - other (also flatpak!) apps like GIMP work fine.

If you need testers, I'd be happy to help, and good luck in your research!

[RoNiN-shadow]

I managed to reproduce and fix this issue!

The root cause:

1. In generate_content_provider, the app was using ContentProvider::for_bytes("text/uri-list", ...). Sending raw bytes bypasses the xdg-desktop-portal, so Flatpak sandboxed apps (like Telegram) are never granted file access permissions.

The solution:
I switched File::for_path to File::for_uri and replaced the raw byte provider with GTK's native gdk4::FileList. This properly triggers the desktop portal, and Telegram now accepts the files perfectly.

I will open a PR shortly. Note: Using FileList::from_array required bumping the gtk crate feature from v4_6 to v4_8 in Cargo.toml. Hope that's an acceptable bump!"