Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exporting logs as ZIP results in a 0-byte file #148

Open
Skaynod opened this issue Nov 3, 2024 · 5 comments
Open

Exporting logs as ZIP results in a 0-byte file #148

Skaynod opened this issue Nov 3, 2024 · 5 comments

Comments

@Skaynod
Copy link

Skaynod commented Nov 3, 2024

When exporting logs as a ZIP file, the resulting file has a size of 0 bytes. I am unable to open the file, as it appears to be empty or corrupted.

Steps I Took to Encounter the Issue:

  1. I selected the logs I wanted to export.

  2. I chose the ZIP export option.

  3. I started the export and downloaded the generated ZIP file.

  4. I noticed that the downloaded ZIP file was 0 bytes and couldn’t be opened.

Expected Behavior:
The ZIP file should contain the exported logs and be accessible without issues.

Current Behavior:
The generated ZIP file is 0 bytes in size and cannot be opened.

Additional Information:

Operating System: Android 10

Logfox Version: v2.0.3 d0ac7d6

Device Model: Xiaomi Redmi Note 9 Pro with MIUI 12.0.3

Root Status: Device is rooted with Magisk 28

Troubleshooting Attempts:

  • Restarted the app and tried exporting again

  • Cleared the app cache and forced stop the app

  • Uninstalled and reinstalled different versions of the app

  • Restarted the phone and retried the export

  • Attempted export with different log sets

MiXplorer

@F0x1d
Copy link
Owner

F0x1d commented Nov 3, 2024

Do you mean these steps?

  1. Select logs in LogFox tab
  2. Click "To recording"
  3. Export created recording as ZIP

If so, then can't reproduce on Pixel 7 with A15. Could you attach a video showing all your steps in the app?

@drogga
Copy link

drogga commented Nov 5, 2024

Can it be the fact that is uses SAF, instead of storage R/W Permission(s) - IDK, but on systems that the "Files" (DocumentsUI) app is missing or disabled/frozen (the later I did on purpose to reproduce and should be addressed as an exception) I get no file at all, LogFox crashes instead, it's easily replaceable, so I didn't grab logs by for example using another app that does also capture crashes.

@F0x1d
Copy link
Owner

F0x1d commented Nov 7, 2024

But the problem is "0 bytes files" and not the crash. But maybe it's also something with ROM and system Files app

@drogga
Copy link

drogga commented Nov 8, 2024

But maybe it's also something with ROM and system Files app

Exactly, IDT my comment is that off-topic, it's kind of on point, but I can delete it if you want...


Here's an off-topic thing, which I certainly have to delete:
The Build Actions Workflow https://github.com/F0x1d/LogFox/actions/runs/11671049563 throws 2 warnings:
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3.
The 'set-output' command is deprecated and will be disabled soon. Please upgrade to using Environment Files.
The artifacts/files are only 4 days old and already expired, you might want to adjust that .yml for that one, the others seem fine ;)

@F0x1d
Copy link
Owner

F0x1d commented Nov 8, 2024

I will probably find some time on weekends to fix these warnings. And also fix ttl for artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants