huggy That's because there isn't currently a solution. The links I've provided are from the GitHub issue tracker. The primary purpose of the issue tracker is to track new feature requests and also to track bugs like this one. It looks unfortunately like this bug is an upstream one from AOSP, which is probably why it hasn't yet been resolved.
It's useful to know that you've identified a workflow which reproduced this issue. If you're happy to, you could comment in the issue tracker on GitHub with the steps you took to reproduce this issue. Other users would be able to test the same steps themselves, which could go a long way to helping the developers identify the root cause of this issue.