We have exactly the same issue, but with a different framework with the same configuration essentially. Nothing changed on our side, but a random small update suddenly starts to get this exact error on iOS 18 only.

@Frameworks Engineer This is an absolutely insane change to make in a .1 release. You're changing a long-time documented & established (12+ year) default that many apps rely on for their layout and just change it to something else, breaking essentially everything that uses layoutMargins. If you did this for 27.0 with a big warning and a good explanation why, it could have made a little bit sense, but right now it's just a tiny hidden line in 27.2 release notes (while this change is for 27.1) having massive impact on layout. Also, preservesSuperviewLayoutMargins does something completely else. It seems the only way to fix this mess is to swizzle UIView.init() to set the correct default again.