-
Notifications
You must be signed in to change notification settings - Fork 20
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
Database doesn't import and causes a crash #268
Comments
that db isn't loading |
Woah thanks for pointing that out, I didnt realise it backed that up too |
Here's a new db with the same problem: |
Funny thing is that I already considered something like this would happen with Piped accounts, yet still I haven't changed anything about the way this works. Maybe something for a separate issue ticket? |
Now for the error, I guess this has something to do with the fact that I update the Room dependency every now and then, which may cause some unexpected behavior like this. I'll try to find out why this is after my final exams, because this seems a bit complicated. |
I am also unable to restore data from vitune db file, on 1.0.4 Also I hope to see a system which allows vitune db to be compatible with other vimusic forks (if possible) - I believe it can be done by letting the user choose what data to backup at the time of backup instead of backing up all data |
Interesting idea, I think letting users export for ViMusic v0.5.4 and calling it 'compat mode' should do the trick, no? |
yeah and also i suggest to remove the piped credentials from the db. |
Yeah, I think that'll work. |
Hi, I don't know if it's relevant but thought I'd share: Had the same problem on a new install. Then (after trying around for a while) I first cleared all app data in android settings and then played a random suggested song for a few seconds and tried importing again. Then importing worked flawlessly. Both versions of the app (export and import side) were 1.0.4. Maybe playing a song initialized someting somewhere...? Anyway hope it helps. |
Didn't worked for me, recently i did a fresh install and tried to restore from nightly build backup db, app just closes and nothing happens after reopening Also i tried to do setup again, with a fresh backup db and tried to restore that, same results |
Steps to reproduce the bug
Expected behavior
Database imports songs and playlists from stable to nightly build.
Actual behavior
App crashes, db not imported
Screenshots/Screen recordings
No response
Logs
FATAL EXCEPTION: arch_disk_io_2
Process: app.vitune.android.nightly, PID: 26244
android.database.sqlite.SQLiteDatabaseCorruptException: database disk image is malformed (code 11 SQLITE_CORRUPT)
at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native Method)
at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:1030)
at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:838)
at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:145)
at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)
at M2.r.J(SourceFile:37)
at Q2.v.a(SourceFile:13)
at Q2.v.e(SourceFile:43)
at r0.v.run(SourceFile:27)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
ViTune version
1.0.3
What kind of build are you using?
Nightly (F-Droid)
Android version
Android 13
Device info
Oppo A54 5g, running ColorOS 13
Upstream reproducibility
No response
Additional information
This issue has been reported already in #61 and #250, but hopefully the logs will help
Checklist
The text was updated successfully, but these errors were encountered: