There is some change done in viewdidlayoutsubviews in iOS 13 that is causing it to be called later in the life cycle of the View Controller once it has finished its first callings (on changing frame). This is creating some weird effects in the apps.
What I have observed is that before iOS13 changing frames do not call viewdidlayoutsubviews while in new iOS 13 it gets called.
Is this some kind of new feature by Apple or some bug? Any suggestions on how to stop this behavior?
I'm facing that issue only for an UIViewController
which will be added as a child of a Container View Controller. The device was not rotated - these are just the methods which will be called if the UIViewController
was initial added to the hierarchy:
iOS 12:
iOS 13:
For me, that's not a feature hence it does not make sense calling viewDidLayoutSubviews
after viewDidAppear
(if the device was not rotated). Looks like a bug on iOS 13.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With