I got the 13.2.3 update to the Android app today, and there’s an odd visual glitch that occurs any time I’m on the main page and I select a category, a feed, or a tag (from the tags under Saved Stories). Normally it would nicely fade/slide into the contents of the category/feed. Now this happens:
The contents of the category/feed pop in briefly, full-screen.
Those new contents immediately start sliding from left to right across the screen, going off the screen. (There was no time to read them.) The previous listing is again visible, as if I hadn’t tapped anything.
The screen briefly darkens.
The contents of the category/feed I tapped will then cut in full-screen with no transition, and I can select a story as desired.
This happens every time I tap a category or feed. When I tap a story within a feed, it slides in from bottom to top, as normal. There’s no broken functionality that I can see; it seems to be just graphical.
I just realized another effect of this issue. When I go back from a category/feed to the main menu, there’s a missing transition, which manifests as a delay after hitting the back button. It’s consistent, and makes me think that I didn’t hit back correctly, so I hit it again, but that closes the app. (As with the issue I described above, the transition from an individual item back to the category/feed list is still there and working, it’s just when going back to the main menu.)
@redshift Could you screen record these glitches? It will help a lot with debugging.
Do you see the first reported issue when you switch between feeds by going back and forth to the home page and feed page?
@redshift That is very helpful as I don’t have the same behavior on my primary device. I’ll have to test a few more to see if I can replicate. Do you have the global default animation/transition settings on the phone?
Do you happen to know if under the Dev debug settings you have predictive back enabled? It’s a new Android 14 feature.
It looks like there is a new API that can be used for Android 14 for handling custom transitions and I’m gonna update to it since I couldn’t replicate the glitch from your video on the two phones I have available.
Unfortunately I’m not sure about the timing - I had gotten used to the problem, and I was already used to the correct behavior, so I didn’t notice when it switched back. It may have been before the update, though I’m not sure how that would have happened. In any case, I appreciate your help, and how you fixed things in a good way so it shouldn’t come back.