Thanks - can confirm that I can reproduce with that too.
And it's something to do with the device model in the User Agent that is the triggering it.
This in the emulator will see the issue...
Mozilla/5.0 (Linux; Android 12; motorola edge 5G UW (2021)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Mobile Safari/537.36
This won't - all I have done is remove the space between edge & 5G:
Mozilla/5.0 (Linux; Android 12; motorola edge5G UW (2021)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Mobile Safari/537.36
This won't either - I have removed the word edge...
Mozilla/5.0 (Linux; Android 12; motorola 5G UW (2021)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Mobile Safari/537.36
And this won't either - I have added a letter to the word edge...
Mozilla/5.0 (Linux; Android 12; motorola 5G edger 5G UW (2021)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Mobile Safari/537.36
And with that, my theory is that the browser is being detected as the unsupported non-Chromium based version of Microsoft Edge that came out a few years and triggering onwards issues as a result.
And now I am out.