@ehill27 Seems like a current bug that was reported on GitHub:
And it already has a merged fix (though I can’t tell, if it will make it into the next Android release 2025.8.0):