claudiodangelis / qrcp

:zap: Transfer files over wifi from your computer to your mobile device by scanning a QR code without leaving the terminal.
https://qrcp.sh
MIT License
9.89k stars 524 forks source link

zip flag have a bug #317

Closed ilaoyao closed 4 months ago

ilaoyao commented 7 months ago

I'm opening this issue because:

qrcp folder will zip the current folder and transfer to the mobile.but with qrcp ver 0.11.0, I found a bug like:

A. conclusion

B. Scene reenactment

1) if the folder is the Same level directory

11

when i ran qrcp ..\333, then i used my phone to scan this , transfer was right, but the zip-file will look like blow( i user alzip app), it has been insert a sub-folder name __ : Screenshot_2023-12-16-09-12-23-772_com estsoft alzip_看图王 but it can be extracted normally.

when i use the rootexplore app to extract it, RE app show error! Screenshot_2023-12-16-09-12-43-121_com speedsoftware rootexplorer_看图王 Screenshot_2023-12-16-09-12-56-019_com speedsoftware rootexplorer_看图王

when i send this zip file back to my computer, and i extract it with 7-Zip, it look blow: 231

the folder and the filename has been changed all.

2)if the folder is a sub directory

222

when i ran qrcp 333, then i used my phone to scan this , transfer was right, and the alzip app work right.

when i use the rootexplore app to extract it, RE app show error again! Screenshot_2023-12-16-09-17-57-746_com speedsoftware rootexplorer_看图王

Screenshot_2023-12-16-09-18-06-824_com speedsoftware rootexplorer_看图王

when i send this zip file back to my computer, and i extract it with 7-Zip, it look blow: 333

the folder and the filename has been changed all.

I mean this --zip flag maybe do something wrong when before the transfer (in version 0.11.0) .

I run the version 0.10.1 and it works all fine, and all the errors above are not exist and the structure of the folders shows all correctly.

claudiodangelis commented 7 months ago

Hello @ilaoyao , a new version is out 0.11.1 and it will solve the issue you are experiencing. Thanks a lot for reporting the issue and thanks to @vincenzoAiello for fixing it right away!

Please let me know if we can close this issue.