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

Crashes after restore with SwiftBackup #1757

Open
4 tasks done
razhterize opened this issue Mar 7, 2024 · 4 comments
Open
4 tasks done

Crashes after restore with SwiftBackup #1757

razhterize opened this issue Mar 7, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@razhterize
Copy link

razhterize commented Mar 7, 2024

Steps to reproduce

  1. Backup Neko with SwiftBackup (including Data, Media, Expansion, and Ext. Data)
  2. Factory Reset (or install different ROM in my case)
  3. Restore Neko with SwiftBackup
  4. Open Neko

Expected behavior

Opened Library page

Actual behavior

Crashes with provided logs below

Crash logs

neko_crash_logs.txt

Neko version

2.16.2 (3)

Android version

Android 14 (Derpfest Custom ROM)

Device

Redmi 10C

Other details

Phone is rooted with Magisk Delta 26.4 (Kitsune Mask)
The crash only happens IF I restore it with SwiftBackup or similar backup apps with /data recovery. Usually those that requires root to use.
Oh and regular backup/restore does work. no issue with that
I have previous Neko (previous Custom ROM) download folder in /sdcard/Neko

EDIT:
I think it will happen if I restore with any downloaded chapters in previous Neko. Need further confirmation for this one

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I have updated the app to the newest version Latest.
  • I have filled out all of the requested information in this form.
@razhterize razhterize added the bug Something isn't working label Mar 7, 2024
@master-bob
Copy link
Contributor

I think something went wrong. When I download the crash log it's a 0B file.

@nonproto
Copy link
Collaborator

Without a crash log I won't be able to do anything

@razhterize
Copy link
Author

I'll see if I can reproduce it as I lost the original crash like logs

@razhterize
Copy link
Author

neko_crash_logs.txt
here's what I got. it seems like on normal operation it wont trigger the crash

so far, there's 3 conditions I was able to confirm

  1. Before backup, Neko must have downloaded titles in library
  2. Restore backup (with SwiftBackup) must include data, and ext_data
  3. Library has to be set to Downloaded for it to crash. Otherwise it will continue to operate like normal
    image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants