Why is PushManager registered 4 times to handle iOS IOnFinishedLaunching?

[jmichas]

I am using shiny.notifications, shiny azure notification hubs, shiny 3.3.4, .net9, testing in simulator and on device. I am also using the deprecated shiny framework 4.1.0, but really that is just used for startup window init and navigation service.
On start in my logs I see:

2025-12-02 11:04:27.440817-0500 MyApp.Mobile[84800:63685017] [INF] Shiny.Push.PushManager handling lifecycle event for Shiny.Hosting.IIosLifecycle+IOnFinishedLaunching
2025-12-02 11:04:27.441571-0500 MyApp.Mobile[84800:63685017] [INF] Shiny.Push.PushManager handling lifecycle event for Shiny.Hosting.IIosLifecycle+IOnFinishedLaunching
2025-12-02 11:04:27.441880-0500 MyApp.Mobile[84800:63685017] [INF] Shiny.Push.PushManager handling lifecycle event for Shiny.Hosting.IIosLifecycle+IOnFinishedLaunching
2025-12-02 11:04:27.442144-0500 MyApp.Mobile[84800:63685017] [INF] Shiny.Push.PushManager handling lifecycle event for Shiny.Hosting.IIosLifecycle+IOnFinishedLaunching

I am not sure why this is the case. It causes push notifications to get processed 4 times on a cold start when tapping the OS notification.

I do register these in my AppDelegate because when I tested removing them my pushes stopped triggering my delegate and I wasn't getting a ANH token.

[Export("application:didRegisterForRemoteNotificationsWithDeviceToken:")]
public void RegisteredForRemoteNotifications(UIApplication application, NSData deviceToken)
{
global::Shiny.Hosting.Host.Lifecycle.OnRegisteredForRemoteNotifications(deviceToken);
}

[Export("application:didFailToRegisterForRemoteNotificationsWithError:")]
public void FailedToRegisterForRemoteNotifications(UIApplication application, NSError error)
{
global::Shiny.Hosting.Host.Lifecycle.OnFailedToRegisterForRemoteNotifications(error);
}
[Export("application:didReceiveRemoteNotification:fetchCompletionHandler:")]
public void DidReceiveRemoteNotification(UIApplication application, NSDictionary userInfo,
Action<UIBackgroundFetchResult> completionHandler)
{
global::Shiny.Hosting.Host.Lifecycle.OnDidReceiveRemoteNotification(userInfo, completionHandler);
}

I am coming from the v1 shiny stuff or something at least few major versions ago, so I am not sure what the updated proper way is to register lifecycle events in Shiny.

Also if I inspect my services as the app is built I see only one entry for typeof(IIosLifecycle.IOnFinishedLaunching) in builder.services.

[jmichas]

Also, if it helps, before the logs in my original post this happens:

2025-12-02 11:03:09.314024-0500 MyApp.Mobile[84800:63685017] [INF] Startup Binding for Shiny.Push.AzureNotificationHubsPushProvider
2025-12-02 11:03:09.314808-0500 MyApp.Mobile[84800:63685017] [INF] Success: Shiny.Push.AzureNotificationHubsPushProvider to store: settings
2025-12-02 11:03:09.315234-0500 MyApp.Mobile[84800:63685017] [INF] Startup Binding for Shiny.Push.PushManager
2025-12-02 11:03:09.315689-0500 MyApp.Mobile[84800:63685017] [INF] Success: Shiny.Push.PushManager to store: settings
2025-12-02 11:03:09.316686-0500 MyApp.Mobile[84800:63685017] [INF] Component Start: Shiny.Notifications.ChannelManager
2025-12-02 11:03:09.316937-0500 MyApp.Mobile[84800:63685017] [INF] Starting iOS channel manager
2025-12-02 11:03:09.344451-0500 MyApp.Mobile[84800:63685017] [DBG] Channel manager initialized successfully
2025-12-02 11:03:09.346828-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Hosting.IosLifecycleExecutor' ran successfully
2025-12-02 11:03:09.350381-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Hosting.IosLifecycleExecutor' ran successfully
2025-12-02 11:03:09.350782-0500 MyApp.Mobile[84800:63685017] [WRN] UNUserNotificationCenter is already set.  Shiny will not be able to run its notification delegates
2025-12-02 11:03:09.350983-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Jobs.Infrastructure.JobLifecycleTask' ran successfully
2025-12-02 11:03:09.351939-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Jobs.JobManager' ran successfully
2025-12-02 11:03:09.352890-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Hosting.IosLifecycleExecutor' ran successfully
2025-12-02 11:03:09.353217-0500 MyApp.Mobile[84800:63685017] [WRN] UNUserNotificationCenter is already set.  Shiny will not be able to run its notification delegates
2025-12-02 11:03:09.353387-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Hosting.IosLifecycleExecutor' ran successfully
2025-12-02 11:03:09.353711-0500 MyApp.Mobile[84800:63685017] [WRN] UNUserNotificationCenter is already set.  Shiny will not be able to run its notification delegates
2025-12-02 11:03:09.353914-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Jobs.Infrastructure.JobLifecycleTask' ran successfully
2025-12-02 11:03:09.354244-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Jobs.JobManager' ran successfully

You can see that the IosLifecycleExecutor ran 4 times, so maybe this is the cause of the issue?
I just don't know what triggers the IosLifecycleExecutor to run.

[aritchie]

I would need to see all of the startup code to give you an idea of a direction to take here.

[jmichas]

So, I should expect to see only one of each these lines though right?

2025-12-02 11:04:27.440817-0500 MyApp.Mobile[84800:63685017] [INF] Shiny.Push.PushManager handling lifecycle event for Shiny.Hosting.IIosLifecycle+IOnFinishedLaunching

2025-12-02 11:03:09.346828-0500 MyApp.Mobile[84800:63685017] [DBG] Startup task 'Shiny.Hosting.IosLifecycleExecutor' ran successfully

I'll see if I can cleanup my startup code, but really there isn't much of it that is that odd. I mean just the stuff I do for shiny framework and container registration. I am calling UseShiny, but should I be if I have use Shiny.Framwork also?

UseShiny()
.UseShinyFramework(new DryIocContainerExtension(), prism =>
{
 ....
    prism.CreateWindow(....);
    prism.OnInitialized(....);
});

Is there a easy/better way for me to phase out the Framework stuff and still use Prism nav service?
Where would I do the prism.CreateWindow stuff and the prism.OnInitialized container registration if I removed Framework?

[aritchie]

UseShinyFramework initialized/called UseShiny, so you might be getting two registrations there. Just have UseShiny and follow what Prism requires to initialize: https://docs.prismlibrary.com/docs/current/platforms/maui/

You may have multiple lifecycle managers, not multiple push managers

[jmichas]

Yup, that was it. As soon as I wrote my response I went in and tried commenting out UseShiny and got only the one line for the executor and push reg. Thanks for getting me thinking more about it. I will work to remove framework since it isn't really providing much more than a convenience at this point.
I think when I was updating from forms to Maui and then maybe between maui versions I ended up thinking I needed UseShiny and Framework because something was not getting registered.
Anyway, all good now thanks!