Hi Miljan, I assume this could be solved with a next TestFlight release?
Yes, this has been fixed and will be included in the next TestFlight release.