Apple如何实现UIActivityViewController？关于其模态展示样式的疑问

Great question—this is one of those UIKit deep dives that reveals how Apple builds system-level components with custom behavior that deviates from standard API docs. Let’s break this down:

First, let’s clarify the discrepancy: Apple’s docs state that UIModalPresentationStyle.popover falls back to fullScreen in horizontal compact environments, but UIActivityViewController clearly shows a bottom-aligned sheet (similar to an action sheet) instead of a full-screen presentation. Here’s how they likely pull this off:

• Custom Adaptive Presentation Logic: Instead of relying on the default popover adaptive behavior, UIActivityViewController uses an internal implementation of UIPopoverPresentationControllerDelegate to override the adaptive style. Specifically, it probably returns a custom adaptive behavior (via private hooks) that forces the popover to render as a bottom sheet in compact environments, rather than switching to full-screen.
• Private Container Controllers: Under the hood, UIActivityViewController wraps its content in private sub-controllers (like _UIActivityGroupViewController, which you can spot via runtime inspection) that handle layout and presentation logic separately. These private components manage the sheet-like appearance, including setting constraints to anchor the view to the bottom of the screen and limit its height, instead of expanding to full screen.
• Overridden Popover Layout: The standard UIPopoverPresentationController allows some customization of source rects and margins, but Apple takes this further with private APIs to modify the popover’s frame directly. They likely adjust the popover’s size and position dynamically based on the trait collection, ensuring it stays as a bottom sheet even when the system would normally switch to full-screen for popovers.

As for whether private features are involved: Yes, almost certainly. Apple reserves these custom presentation behaviors for system components, using internal UIKit APIs that aren’t exposed to third-party developers. If you tried to replicate this with public APIs alone, you’d hit limits—you can customize popover adaptive styles to a degree, but you can’t fully match the seamless, system-native behavior of UIActivityViewController without relying on private code (which would get your app rejected from the App Store).

It’s worth noting that this is part of Apple’s pattern of building polished, context-aware system UI that prioritizes user experience over strict adherence to general API rules. For third-party devs, the best we can do is use UIActivityViewController as intended, since replicating its exact presentation logic isn’t feasible with public tools.

内容的提问来源于stack exchange，提问作者JIE WANG