You're absolutely right with all your assumptions. AutoDisconnectHandler="False" does not call the DisconnectHandler method in SegmentedControlHandlers (which sooner but rather later leads to memory leaks).
The problem that seems to happen here is that the handler for one of your SegmentedControls gets disconnected too soon. We have to find out what navigation scenario this is and how I can reproduce it in the sample app in this repository.

I'm not familiar with shell apps. Would it be possible to get a very minimal shell app which causes this problem?

The problem that seems to happen here is that the handler for one of your SegmentedControls gets disconnected too soon. We have to find out what navigation scenario this is and how I can reproduce it in the sample app in this repository.

I think the SegmentedControl is not properly checking the modal page stack, likely in HandlerCleanUpHelper.cs:
private static bool CheckIfPageIsUsed(Page targetPage)

I'll try to make a simple app to reproduce.

It is surely a problem is the CheckIfPageIsUsed method. The thing is, this method is growing with more scenarios :)

I wish MAUI would solve this DisconnectHandler problem for us... but at least for .net 8 they don't.

Usage:

• Click "Open Modal Page" from Tab1
• Click "Open Another Modal Page"
• Click "Close Modal Page"
• Observe broken layout. If layout is not broken, click "Open Another Modal Page" again. After a couple of times it should trigger a ui layout.

https://github.com/brendonupson/SegControlTest

Maybe just needs line 79 in HandlerCleanUpHelper.cs changed from:

return pageExists;

to:

if(pageExists) return true;

Then the code will fall through and check further?

Hello @brendonupson , is this PR expected to fix the layout issue with the segmented control on modal pages? #32

cc: @thomasgalliker

Thanks in advance

Important question: How are you registering pages in the DI container? Singleton or transient?
If you register pages and viewmodels as singleton (which I do not recommend) you have to disable to AutoDisconnectHandler feature.

Ok, ignore my question regarding DI registrations. I just had a look at your sample app (very valuable; always in such situations!). There is something wrong in the automatic disconnect logic. SegmentedControlHandler on Modal1Page is (mistakenly) disconnected when Modal2Page is displayed.

There is a fix available for this problem. A new nuget pre-release will be available soon.

Thanks @thomasgalliker for the support, really appreciate it 🙂

@vhugogarcia and @brendonupson can you test Plugin.SegmentedControl.Maui 1.4.25-pre and let me know if it solves the problem? 👍🏻

Looks like it's fixed for me on iOS, yet to test Android

I out of the town today and this weekend, I can help to test on iOS and Android next Monday, I am sorry

Hello @thomasgalliker , I tried the version you provided, however, the issue is still present. Please see the video below. Also, find below the console log:
HandlerCleanUpHelper.AddCleanUpEvent for "SegmentedControl" on page "LocationPage"

I have the project locally cloned, if there is something you want me to try, let me know and I can update the code. I will also give it a try myself to see if I can find out the root cause.

@vhugogarcia I saw your video but it's hard to tell if this is a related problem. I need a sample reproduction app to debug the code, just as @brendonupson has provided one above. In case of @brendonupson, the problem with the HandlerCleanUpHelper could be solved in PR #33. Can you also provide a sample sample app which only demonstrates the problem?