iOS Notification Service Extension fails to launch (worked in 9.0.305)

[idenardi]

Apple platform

iOS

Framework version

net9.0-*

Affected platform version

9.0.306

Description

Starting with .NET 9.0.306, an iOS Notification Service Extension (built with .NET MAUI or Microsoft.iOS) fails to launch. The process never starts or crashes immediately. In .NET 9.0.305, the exact same project worked correctly.

This regression breaks push notifications that include mutable-content:1.

Steps to Reproduce

1. Create an iOS (or .NET MAUI) app with a Notification Service Extension:
   1.1. Main app target: net9.0-ios
   1.2. Extension target: net9.0-ios
2. Send a push notification - Push payload includes "mutable-content": 1
3. Build and deploy using .NET 9.0.305:w extension runs as expected, can change the push content
4. Upgrade workloads to .NET 9.0.306.
5. Build and deploy again: extension no longer launches.

Did you find any workaround?

No response

Relevant logs

Here are some warnings from the device console logs, when a push is sent:

• [u 7A54B3F8-81E8-46FB-B5BA-1F458A942393:m (null)] [()] Hub connection error: Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named com.company.dev.notificationextension" UserInfo={NSDebugDescription=connection to service named com.company.dev.notificationextension}
• error: Failed to load AOT module 'Microsoft.iOS' while running in aot-only mode: doesn't match assembly.
• Sandbox: Company.iOS.NotificationExten(90410) deny(1) sysctl-read kern.bootargs
• RBSStateCapture remove item called for untracked item 34-35-608390 (target:[xpcservice<com.company.dev.notificationextension([osservice<com.apple.SpringBoard>:35])>{vt hash: 0}:90445])

[rolfbjarne]

I tried this sample project, and it works for me: https://github.com/dotnet/macios-samples/tree/main/UserNotifications/iOS

• error: Failed to load AOT module 'Microsoft.iOS' while running in aot-only mode: doesn't match assembly.

This typically happens when we a part of the incremental build is not done right - which means the problem should go away if you delete the bin/obj directories (of both the main app and the extension) + manually delete the app from the device as well, and then trying again.

Can you try that and see if it changes anything?

[idenardi]

I ran the test again after deleting the bin and obj folders, but it still didn’t work.
I noticed a new log message:

error: Failed to load AOT module 'UnitsNet' while running in aot-only mode because a dependency cannot be found or it is out of date.

Even after removing the UnitsNet dependency and running again, the error still occurs (but now points to another module).
Do you have any suggestion on what could be causing this?

[ronanj2]

Our notification extension stops working if we deploy using the 9.0.306 workload.
Works fine when deployed using 9.0.305 sdk and workload.

[rolfbjarne]

error: Failed to load AOT module 'UnitsNet' while running in aot-only mode because a dependency cannot be found or it is out of date.

Is this from the main app or the extension?

I'm not aware of any changes in the latest workload that would cause this, so it's somewhat puzzling.

Could you get an MSBuild binlog for both the main app and the extension?