Closed gjedeer closed 7 years ago
Thanks for reporting this, I will take a look
Hi @gjedeer, the issue is fixed with https://github.com/frostwire/frostwire-jlibtorrent/commit/186221eb15e2c393a34ef5810cb3cbb6a6c1c7b9.
Now you will get the default replacement character defined by the java framework (and not an unexpected exception or crash). If you want to get to the low level in order to manually decode invalid UTF-8 characters in the torrent file, you can go to the native .swig()
object and get the byte[]
. But remember, this is only for UI display, there is still UTF-8 decoding at the OS level for actual file system creation of files, and the characters there could be different, android OS does not support another encoding iirc.
1.2.0.9-RC4
is out for testing
Thank you @aldenml !
Looks like a similar issue to https://github.com/frostwire/frostwire-jlibtorrent/issues/144 - this time, the same thing happens in FileStorage.fileName().