Fixed
Status Update
No update yet.
Comments
il...@google.com
Information redacted by Android Beta Feedback.
ap...@google.com
Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
il...@google.com
Upon more testing myself, it looks like an additional home button press is being invoked when swiping home. You can verify this within Nova Launcher by setting a "Home button" action in Nova Settings > Gestures and inputs. Observe that the additional action you set will also be activated occasionally when you swipe home. In the attached screen recording, I've set the extra home button action to open the Google Assistant.
Tapping the screen during the return-to-home transition on the past couple Android releases would cancel the animation and you'd instantly end up on your home screen. It looks like that's what is happening here as well -- the extra invocation of the home button press is cancelling the transition animation (and with Nova, running the action you set if any). I couldn't say whether or not that's related to the content flat out not appearing though.
https://drive.google.com/file/d/1_pmlVTs78SbuiTBatk4Q_KDx88nCrKoX/view?usp=drive_web (screen-20230413-004652.mp4)
Tapping the screen during the return-to-home transition on the past couple Android releases would cancel the animation and you'd instantly end up on your home screen. It looks like that's what is happening here as well -- the extra invocation of the home button press is cancelling the transition animation (and with Nova, running the action you set if any). I couldn't say whether or not that's related to the content flat out not appearing though.
Description
Component used: fragment-testing
It would be great to have a
FragmentScenario.withFragment()extension function which has equivalent capabilities toActivityScenario.withActivity()(return value, caching and rethrowing of exceptions).If it's helpful, I have added this to one of my tests
ActivityScenario.withActivity(), so I'm not sure if I'm missing any fragment-specific considerations, but it has been working for my use case.