自定义交互式视图控制器转场与滚动视图处理问题咨询

Hey Jeff, I get it—working through custom transitions with UIPresentationController, UIPercentDrivenInteractiveTransition, and the rest of the transition APIs feels great when basic functionality clicks, but those edge cases that tutorials skip are the real headache. Let’s dive into the most common unaddressed scenarios and how to handle them properly:

Scenario 1: Resetting View State After Canceling an Interactive Transition #

One super common oversight is failing to reset your presented view’s position or state when the user cancels an interactive dismiss (like dragging a modal down halfway and letting go). If you don’t handle this, the view might stick in a partial position instead of snapping back to full screen.

Fix: #

Override the cancelInteractiveTransition() method in your UIPercentDrivenInteractiveTransition subclass, and trigger a reverse animation to reset the view. You can also hook into the transition coordinator to run cleanup code:

class CustomInteractiveTransition: UIPercentDrivenInteractiveTransition {
    var isInteractive = false
    
    override func cancelInteractiveTransition() {
        super.cancelInteractiveTransition()
        // Trigger a smooth snap-back animation
        completeTransition(false)
    }
    
    // You can also use the transition coordinator in your presented VC
    func setupTransitionCoordinator(in presentedVC: UIViewController) {
        presentedVC.transitionCoordinator?.notifyWhenInteractionChanges { context in
            if context.isCancelled {
                // Reset any custom state (e.g., alpha, frame)
                presentedVC.view.alpha = 1.0
                presentedVC.view.frame = presentedVC.view.superview?.bounds ?? .zero
            }
        }
    }
}

Scenario 2: Supporting Multiple Trigger Gestures for Transitions #

Most tutorials focus on a single gesture (like a pan gesture to dismiss), but real-world apps often need to support multiple triggers—like tapping the dimmed background to dismiss and dragging the modal down.

Fix: #

Add multiple gesture recognizers to your presentation controller’s dimming view or presented view, and link them to your interactive transition. Make sure to handle gesture conflicts (e.g., ignore taps if a pan is already active):

class CustomPresentationController: UIPresentationController {
    private let dimmingView = UIView()
    private var panGesture = UIPanGestureRecognizer()
    private var tapGesture = UITapGestureRecognizer()
    weak var transitionDelegate: CustomTransitionDelegate?
    
    override func presentationTransitionWillBegin() {
        super.presentationTransitionWillBegin()
        
        // Setup dimming view
        dimmingView.backgroundColor = UIColor.black.withAlphaComponent(0.5)
        containerView?.insertSubview(dimmingView, at: 0)
        
        // Add gestures
        panGesture.addTarget(self, action: #selector(handlePan(_:)))
        tapGesture.addTarget(self, action: #selector(handleTap(_:)))
        dimmingView.addGestureRecognizer(tapGesture)
        presentedViewController.view.addGestureRecognizer(panGesture)
        
        // Resolve gesture conflicts
        panGesture.require(toFail: tapGesture)
    }
    
    @objc private func handlePan(_ gesture: UIPanGestureRecognizer) {
        transitionDelegate?.startInteractiveDismiss(gesture: gesture)
    }
    
    @objc private func handleTap(_ gesture: UITapGestureRecognizer) {
        presentedViewController.dismiss(animated: true)
    }
}

Scenario 3: Managing View Controller Lifecycle During Interactive Transitions #

Another tricky scenario is ensuring your view controllers behave correctly during interactive transitions—like not loading data or updating UI while the transition is in progress, or cleaning up resources if the transition cancels.

Fix: #

Use the UIViewControllerTransitionCoordinator to check transition status in your view controllers. You can also override methods in UIPresentationController to hook into transition phases:

class PresentedViewController: UIViewController {
    override func viewWillAppear(_ animated: Bool) {
        super.viewWillAppear(animated)
        // Only load data if the transition isn't interactive/cancelled
        if let coordinator = transitionCoordinator, coordinator.isInteractive {
            coordinator.notifyWhenInteractionChanges { context in
                if !context.isCancelled {
                    self.loadData()
                }
            }
        } else {
            loadData()
        }
    }
    
    private func loadData() {
        // Your data loading logic here
    }
}

// In your PresentationController:
override func dismissalTransitionWillBegin() {
    super.dismissalTransitionWillBegin()
    // Notify presented VC to pause ongoing tasks
    (presentedViewController as? PresentedViewController)?.pauseOngoingTasks()
}

If your specific scenario isn’t covered here, feel free to share more details, but these three are the ones I see developers struggle with most when building custom interactive transitions.

内容的提问来源于stack exchange，提问作者Jeff C.