Getting exactly the same issue

Finally, it's now working properly, nothing changed from our side :/ seems like Apple fixed the issue suddenly. what about you guys ?

We also wasted our nerves besides two days and delayed a release because of this problematic api. We also reached Apple via the Feedback assistant, but no answer yet.