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
Selecting image from BrowseProviderFragment
only sets the wallpaper once
#673
Comments
It seems to be working fine for me in the latest Muzei 3.4.0 Alpha 3 (available as part of the public beta). Is that not working for you? |
Strange! Just to be on the same page, here is the flow:
I joined the beta program and gathered some additional devices to make sure I am not doing something wrong, or not missing something. Here are the test result.
The "Result" column Here are some logs collected from the Pixel 2 emulator using local Muzei build (I don't see anything obvious here) Section - Click on
|
Ah, I think the title threw me off as that made it sound like setting the wallpaper from the Browse screen never worked, rather than only the first tap working. I was able to reproduce it when tapping multiple times. |
BrowseProviderFragment
does not set the wallpaper (however ArtDetailViewModel#nextArtwork
works)BrowseProviderFragment
only sets the wallpaper once
The fix will be included in the next Muzei 3.4 build, thanks for bringing this to our attention! |
Env
v3.3.0
Issue
When I tap on the wallpaper from the
BrowseProviderFragment
, the wallpaper is set the first time, after that tapping on different items does not change the wallpaper. However, toast is shown about a successful image set.Screen Cast
NOTE: A longer HD screencast video available at an external file host.
Other observations
When setting an image by tapping
>>
icon on ArtDetailFragment.nextArtwork#L228 successfully sets the wallpaper on new image load every time.I have tried to debug the issue, however, I was not able to identify the actual issue as to why it doesn't work from
BrowseProviderFragment
. Tried callingMETHOD_REQUEST_LOAD
, that didn't help much.The text was updated successfully, but these errors were encountered: