safe-area-compliance

To find unsafe safe-area overrides, scan SwiftUI and UIKit source files for .edgesIgnoringSafeArea usage, zero insets, and fixed top or bottom constants that hide content behind the notch or home indicator. This generates a prioritized report flagging unsafe layout patterns.

Content gets hidden behind the Dynamic Island or notch when layouts use .edgesIgnoringSafeArea(.all) or hardcoded top insets like 44 points. Scanning for these unsafe safe-area overrides identifies where adaptive constraints and safeAreaInsets should replace fixed values.

Scan iOS source and interface files for fixed top or bottom constants like 44 or 34 points that break on devices with a home indicator. The scan compiles a prioritized report flagging hardcoded insets and guides remediation with safe-area-aware code patterns and measurements.

Yes, you can check both UIKit and SwiftUI layouts across iPhone and iPad for unsafe safe-area suppression patterns. The scan identifies SwiftUI .edgesIgnoringSafeArea usage and equivalent UIKit hardcoded insets, then provides remediation guidance for adaptive constraints.

The best way to fix layouts that ignore safe-area insets is to adopt safe-area-aware layouts, use safeAreaInsets, and apply adaptive constraints. The scan provides code patterns and measurements to guide remediation of flagged unsafe overrides.

You should avoid .edgesIgnoringSafeArea when content must remain visible near the Dynamic Island, notch, or home indicator. Scanning flags these unsafe overrides so you can replace them with safeAreaInsets and adaptive constraints that comply with Apple's Human Interface Guidelines.