-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Bug, issue when refreshing library #119
Comments
what does the report says when u hit refresh? how many new tracks it tells? |
It says 0 new tracks even though I added 18 new tracks. As I said, when I killed the app and then re opened it, it worked fine. This is not the first time this has happened. It happened maybe 3 or 4 times before. |
@z9xx7o0 i really cant reproduce this, everything just works fine
i got no clue how couldnt the files get detected, everything should be working fine |
It might be an android 14 thing. It doesn't happen often, but it did happen multiple times. And it's not a big issue. All I have to do is close the app, and if it works fine. |
@z9xx7o0 checked again on Android 14 and everything is fine. |
Well, all I did was organise some of my files, move here to there, delete, add new files, etc. I go to see if my tracks have been updated in Namida, but when i refresh, it hasn't detected any change. I tried multiple times, and there were still no changes, so I closed the app, reopened it, refreshed, and then it worked fine. If you can't recreate this, don't bother wasting anymore time. it's a small bug. It isn't going to affect the user experience. If it happens again, I will record if it might help with something. |
@z9xx7o0 it turns out the issue was that directories weren't force re-scanned, i was basically forcing it only when folders change from indexer folders, thanks again for pointing out. |
Sometimes, when I download new tracks and refresh the library, namida doesn't notice them, I have to kill the app and then refresh, and the tracks get added to the library.
The text was updated successfully, but these errors were encountered: