-
Notifications
You must be signed in to change notification settings - Fork 65
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
Build the albumMap even when the server returns a 403 #597
Conversation
The albumMap is used for navigation, so it's important to build it whenever the user enters the app
By analyzing the blame information on this pull request, we identified @jancborchardt to be a potential reviewer |
I have tested it, and it works fine now. No error encountered by me. 👍 |
I too found no errors. 👍 Works correctly. |
Thanks for testing the fix. If I could ask you to keep using this branch to do normal operation to see if there are no side-effects, I would appreciate it as I didn't have time to thoroughly test this:
The same effect will be achieved if I merge this, but a pre-run is always better ;) |
Actually, even better would be for you guys to merge this PR with #593 in your dev environment. Just cherry pick the 2 commits into a new fork of master and use that when playing with Gallery. |
@oparoz I have tested it by merging this with #593 and I have tried to test a few things and they seem to work well 👍
I will continue to test this and get back to you if I find any error. |
Perfect, thank you |
Build the albumMap even when the server returns a 403
Description
Album navigation breaks when the starting point is an empty Gallery and the user moves to the parent folder.
That's because the map we use for navigation is not built when the server returns an error status to a getFiles request.
Steps to reproduce
.nomedia
fileResult before
Result with this PR
No error
Tested on
Reviewers
@tahaalibra @viraj96 @imjalpreet @mbtamuli @rahulgoyal030