You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subject: Bug Report: Incorrect File Timestamps After Decompression in ZipXtract
Dear ZipXtract Development Team,
I hope this message finds you in good health and spirits. I am reaching out to report an issue I have encountered with the ZipXtract application on my Android device.
Description of the Bug: Upon using ZipXtract to decompress files, I noticed that the creation timestamps of the decompressed files are incorrect. This discrepancy can lead to confusion regarding the actual time of file creation, which is essential for managing file versions and updates.
Steps to Reproduce the Behaviour:
1. Open the ZipXtract application on my Android device.
2. Navigate to the compressed file I wish to decompress.
3. Select the file and initiate the decompression process.
4. After decompression, check the properties of the decompressed files to observe the incorrect creation timestamp.
Expected Behaviour: The decompressed files should retain their original creation timestamps or, at the very least, have the correct timestamps assigned during the decompression process.
Screenshots: [Screenshots of the issue will be attached here to illustrate the incorrect timestamps.]
Smartphone Information:
Device: Honor 90
OS Version: [Please provide the Android version number here]
Additional Context: I have tested the same operation with ZArchiver, and it correctly maintains the file timestamps after decompression, suggesting that the issue is specific to ZipXtract. I believe addressing this bug will greatly enhance the user experience and reliability of your application.
I am using the latest version of ZipXtract available from your GitHub releases page. [If there are specific version details or build numbers, they should be mentioned here.]
Thank you for your attention to this matter. I am looking forward to a prompt resolution and appreciate your efforts in maintaining the quality of the ZipXtract application.
Best regards,
shijie.chen [email protected]
The text was updated successfully, but these errors were encountered:
Subject: Bug Report: Incorrect File Timestamps After Decompression in ZipXtract
Dear ZipXtract Development Team,
I hope this message finds you in good health and spirits. I am reaching out to report an issue I have encountered with the ZipXtract application on my Android device.
Description of the Bug: Upon using ZipXtract to decompress files, I noticed that the creation timestamps of the decompressed files are incorrect. This discrepancy can lead to confusion regarding the actual time of file creation, which is essential for managing file versions and updates.
Steps to Reproduce the Behaviour:
1. Open the ZipXtract application on my Android device.
2. Navigate to the compressed file I wish to decompress.
3. Select the file and initiate the decompression process.
4. After decompression, check the properties of the decompressed files to observe the incorrect creation timestamp.
Expected Behaviour: The decompressed files should retain their original creation timestamps or, at the very least, have the correct timestamps assigned during the decompression process.
Screenshots: [Screenshots of the issue will be attached here to illustrate the incorrect timestamps.]
Smartphone Information:
Device: Honor 90
OS Version: [Please provide the Android version number here]
Additional Context: I have tested the same operation with ZArchiver, and it correctly maintains the file timestamps after decompression, suggesting that the issue is specific to ZipXtract. I believe addressing this bug will greatly enhance the user experience and reliability of your application.
I am using the latest version of ZipXtract available from your GitHub releases page. [If there are specific version details or build numbers, they should be mentioned here.]
Thank you for your attention to this matter. I am looking forward to a prompt resolution and appreciate your efforts in maintaining the quality of the ZipXtract application.
Best regards,
shijie.chen
[email protected]
The text was updated successfully, but these errors were encountered: