Root Cause

When Navigation.RemovePage() is used to remove a page from the navigation stack, the handler associated with the removed page is not disconnected. In contrast, methods like PopAsync() or PopModalAsync() trigger proper cleanup, including handler disconnection.

The RemovePage() method modifies the navigation stack without initiating any disposal or disconnection logic for the page's handler. As a result, the Handler property of the removed page remains assigned after removal, which can retain references to platform-specific resources.

Platform implementations do not consistently handle this scenario. On iOS, handler disconnection occur through ShellSectionRenderer.DisposePage() for some scenarios only, but this is not invoked as part of RemovePage(). On Android and Windows, no corresponding cleanup is performed when removing a page in this way.

Description of Change

This change ensures that when a page is removed from the navigation stack using RemovePage()—and the page is not currently visible—its handler is properly disconnected. The fix is implemented in NavigationProxy.OnRemovePage(), which provides a centralized and platform-agnostic location for handling page removal. This approach ensures consistent behavior across iOS, Android, and Windows, and correctly manages the page lifecycle by disconnecting the handler at the appropriate time.

Issues Fixed

Fixes #29923

Tested the behaviour in the following platforms

• Android
• Windows
• iOS
• Mac

Screenshots