Yep - that bug was introduced with the March 2025 update. It has been fixed on other platforms by the subsequent ‘hotfix’ (several weeks after the update). However - Xbox has not yet been able to receive that hotfix (presumably a certification issue, maybe 
). Once you do receive that hotfix, then this issue should be resolved by it.
For more details (basically there aren’t any…), you can see the announcment here