Well, the reverted version works as you say. I’ve just now rechecked for you as requested.
I’ve made the change below, but at this point in time it doesn’t seem to make any difference which of the versions below I use (though I’ll stick to my modified version).
So, it seems to work (reverted) with or without AsyncBoundsUpdater - but the version with coordinator animateAlongsideTransition (which doesn’t use AsyncBoundsUpdater ) is the one that looks most “iOS safe” to me, so I’ll stick with that approach in my own builds for now…!
My change: from this:
// On some devices the screen-size isn't yet updated at this point, so also trigger another
// async update to double-check..
if (boundsUpdater != nullptr)
[coordinator animateAlongsideTransition: nil completion: ^void (id<UIViewControllerTransitionCoordinatorContext>)