iOS Extensions

[VladislavAntonyuk]

Is it possible to create iOS Extensions with .NET MAUI?
(https://docs.microsoft.com/en-us/xamarin/ios/platform/extensions-with-xamarinforms)

[nor0x]

i'm also very interested in the story for iOS extensions with .NET MAUI. i couldn't find anything in the wiki @davidortinau

[kiddailey]

Also casting my vote for this. I cannot migrate from Xamarin to Maui until iOS Extensions are supported. Edit: I've tried digging to find out if this is on the roadmap, but must have missed it if so. Would love for anyone on the team to simply reply and confirm if this is part of the plan or not. Otherwise, I will need to consider moving off of Xamarin/Maui :(

[jfversluis]

According to @davidortinau this should be possible today: https://twitter.com/davidortinau/status/1529970664467226625

Looks like this is the PR that David is referring to: #5218 and it has some instructions on how to use it

[VladislavAntonyuk]

That seems like not exactly what I mean:

the link is about embedding .NET MAUI in platform apps (.NET for Android, .NET for iOS)

[peter-bozovic]

Did anyone find a solution for this ?
Can't find any documentation anywhere on how to implement service notifications on iOS with MAUI :(
Also asked here but with no solution yet:
https://docs.microsoft.com/en-us/answers/questions/889401/how-to-use-service-extension-for-unnotificationser.html

[VladislavAntonyuk]

It doesn't work with MAUI. Use Xamarin

[peter-bozovic]

I'm building Blazor hybrid app, so can't use Xamarin :(

[brandonward34]

This is also the biggest issue holding us back from migrating to Maui as well. iOS extensions are a big part of our applications

[SaqibS]

Adding my +1 - this is our biggest blocker toupgrading, and I don't see this on the .Net 7 roadmap either. We specifically use an "action extension".

[thisisthekap]

The lack of ios extensions blocks everyone from updating to MAUI who is using pictures in ios notifications (using a notification service extension).

[VladislavAntonyuk]

I found a solution, I will publish a solution in the morning!

[VladislavAntonyuk]

https://vladislavantonyuk.azurewebsites.net/articles/Extend-.NET-MAUI-application-with-iOS-Extensions

[kimdohyung1]

Does the above solution from the link work? I've tried the same steps as the repo but wasn't able to build with the notification extension project reference added to the main project file.

[jjustinm4]

Official templates are not created. I created all iOS extension templates for .net MAUI. You can use it from here: https://www.nuget.org/packages/VladislavAntonyuk.DotNetTemplates

Dear @VladislavAntonyuk i tried to create a project using your solution but im having an errror "dotnet new ios-broadcast-upload-extension -n MyProjectName --applicationId com.vladislavantonyuk.myapp.myapp-BroadcastUploadExtension
No templates or subcommands found matching: 'ios-broadcast-upload-extension'.

To list installed templates similar to 'ios-broadcast-upload-extension', run:"

[VladislavAntonyuk]

@jjustinm4 did you install the Nuget package?

[jjustinm4]

@jjustinm4 did you install the Nuget package?

I am actually using command lien from visual studio , so nuget is already a part of it , isnt it ?

[jjustinm4]

@jjustinm4 did you install the Nuget package?

im really new to .NET and IOS so can i run these command just from a CMD window so that i can have a project ?

[VladislavAntonyuk]

In your cmd you need to install NuGet tool, after that all templates will appear. Run the command that you see in NuGet.org: dotnet tools install …

[hetcmnten]

Did anyone success with Notification Service Extension? I tried every link I can find but no success

[jesse-mta]

Same here. Can someone kindly post a sample .NET MAUI iOS app with Notification Service Extension implementation.

[ssbssb-cmd]

same

[TobiasBuchholz]

For me it doesn't work as well unfortunately.

The attached RichPushNotifications.zip contains a sample project, that demonstrates the issue. I've just created a new .Net Maui app and added the notification service extension project via the template provided by @VladislavAntonyuk. The extension project seems to get included in the build process, because when I'm changing the CFBundleIdentifier in the extensions Info.plist to something that isn't prefixed with the actual package name, the app won't get deployed on the device. Nevertheless the NotificationService.DidReceiveNotificationRequest doesn't seem to get called or at least the notification title doesn't get modified as it should be. I'm migrating a Xamarin.Forms app to .Net Maui and the XF app works just fine, so the setup of provisioning profiles etc shouldn't be the issue since I'm using the exact same setup for the .Net Maui app.

Is there something I could have missed?

[TobiasBuchholz]

FYI, adding the following PropertyGroup to the extension projects .csproj file fixes my problem:

<PropertyGroup>
    <Registrar>static</Registrar>
</PropertyGroup>

Seems to be an issue with .net9, see dotnet/macios#21606

[KSemenenko]

Because of this issue, I had to switch from MAUI to Xamarin, and now to ReactNative. it is a pity that MS did not have time to make the tools. I hope that in .NET8 this will be fixed.

[VladislavAntonyuk]

Did you try the template I created?
I created all iOS extension templates for .net MAUI. You can use it from here: https://www.nuget.org/packages/VladislavAntonyuk.DotNetTemplates

[KSemenenko]

I appreciate all the work you do. However we needed an iOS extension for screen sharing and a binding for video streaming native sdk, and it didn't work on maui at all.
The video worked in xamarin, but the iOS extensions still didn't work.

[VladislavAntonyuk]

got it, I haven't ported Broadcast Upload Extension. I had some issues with including it in my library template.
I will back to it later

[seangifford]

got it, I haven't ported Broadcast Upload Extension. I had some issues with including it in my library template. I will back to it later

Did you ever get a chance to come back to the Broadcast Upload Extension? Do you have any guidance you can share how we can utilize this Extension from MAUI?

[nejis]

Is there any way to integrate a Share Extension in an Android and Ios Project without spliting theam?

[yevgeny-sotnikov]

This is native APIs, you cannot implement it in cross-platform way

[LogeshM05]

@VladislavAntonyuk Please do one video on how to add service extension and content extension..it will be helpful for many

[fady-intelligencex]

@VladislavAntonyuk (or anyone). I have implemented this and it works, but I do not get the shared url or text in the receiving app. Not even in the share does the debug breakpoint is hit. I have created IDs for both the main app and the extension in the apple developer portal and also created a group and assigned both of them to it.

I have uploaded the solution here: https://ix-pubshare.s3.us-west-2.amazonaws.com/testapp1solution.zip

Basically, I want the main app to be able to receive share Urls and text from other apps through the iOS share function.

[VladislavAntonyuk]

Treat iOS extension as a separate application. It has its own logic. As a suggestion you can run your main app from share extension logic.

[devperson]

The ditto error comes when compile with Visual Studio in the Windows but it compile ok with Visual Studio Code in the Mac

[IgorStrekha]

Today I finished developing and successfully published my app on TestFlight, containing two Wallet iOS extensions. The app only works with .NET 8. I downgraded my project to .NET 8. The second key point: you need to use the Rebuild button instead of Publish (Visual Studio-Windows). After a successful Rebuild, open the bin folder and locate the IPA file. Finally, I uploaded the IPA using ios-uploader-win.exe. That's all. My app contains two internal iOS extensions.

[PeterCR20]

Has anyone updated to .NET 9 and found that extensions stopped working on physical devices? I had .NET 8 with MAUI 8.0.92 and updated to .NET 9 with MAUI 9.0.90 since Google (Android) now requires API 35, but when I select an action, nothing happens. I can see the extensions, but they don’t do anything. I have a Console.WriteLine in ViewDidLoad but it never reaches that point. On iOS emulators (18.5/18.4) it works fine. I have an iPhone 8 with iOS 16.7.11 and an iPhone 14 with iOS 18.5, and on neither of them does it work.

Some tests:

• NET 8 + MAUI 8.0.92 = works on physical and emulator
• NET 9 + MAUI 8.0.92 = physical: installs, shows extensions but they do nothing; emulator: works
• NET 9 + MAUI 9.0.90 = physical: installs, shows extensions but they do nothing; emulator: works

For now, I could keep using .NET 8, but it’s really time to start moving to .NET 9.

[baaaaif]

Have you been able to accomplish or find out anything here? I'm currently facing the same problem with a NotificationExtension.

Yes I have!

in the .csproj of the extension in the Release Section I've added these:

  <PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
…
    <PublishTrimmed>true</PublishTrimmed> 
    <MtouchLink>SdkOnly</MtouchLink> 
    <MtouchExtraArgs>--registrar:static</MtouchExtraArgs>
    <MtouchNoSymbolStrip>true</MtouchNoSymbolStrip>
    <UseInterpreter>true</UseInterpreter>
…  
</PropertyGroup>

(maybe it works with UseInterpreter false too but I had not time or nerves to test every possible combination)

Then in the ShareViewController.cs I added this attribute:

    [Preserve(AllMembers = true)]
    public partial class ShareViewController : UIViewController 
{
…
}

now it works - I have such Share-Extension in two Apps and both are working now. The linker is trimming / kicking out essential parts of the code which has to be some bug/problem but I cannot wait for a fix … I don't even know who would fix and test this? If someone know which team is responsible for such things, feel free to send them my findings and lets hope for a fix in the near future … until then I hope that this workaround will work for your Notification-Extension too.

Thanks for your suggestions. It didn't work for me right away, but fortunately it put me on the right track.

Copilot then gave me the final hint I needed.
I need

<MtouchExtraArgs>--registrar:dynamic</MtouchExtraArgs>
<UseInterpreter>false</UseInterpreter>

<UseInterpreter>true</UseInterpreter>
I also tried it. Unfortunately, it doesn't work for me.

nochmals danke :)

[baaaaif]

As a test, I've added a simple log output to the constructor:

public NotificationService(NativeHandle handle) : base(handle)
{
    Console.WriteLine("NotificationService constructor");
}

With <UseInterpreter>true</UseInterpreter> I can't seem to even get there / there is no log output.

I'm glad it works now using <MtouchExtraArgs>--registrar:dynamic</MtouchExtraArgs>, but I'd actually prefer UseInterpreter to be false.
@rolfbjarne Is this a familiar problem with extensions, and do you have any suggestions?

[rolfbjarne]

This seems new, could you please file an issue at https://github.com/dotnet/macios/issues?

[PeterCR20]

After a long time using two branches, net9 (Android/Huawei) and net8 (iOS), today we've taken some time to use only net9. Upon closer inspection, we noticed a change that had already been made that we hadn't seen before: Fix iOS Extension not running on real device
Once we added that tag and updated the NuGet packages to the latest version, it worked for us. If it doesn't work for you, I recommend checking the templates.

Changes you should check in net9 (our project uses the Xamarin separate projects structure): Shared Project: We only updated the MAUI NuGet packages to 9.0.120. iOS Project: We only updated the MAUI NuGet packages to 9.0.120. Also, if you're using OpenURL, check that the AppDelegate is configured like this:

AppDelegate:

[Register("AppDelegate")]`
public class AppDelegate : MauiUIApplicationDelegate
{
    protected override MauiApp CreateMauiApp()
    {
        return MauiProgram.CreateMauiApp();
    }

    public override bool FinishedLaunching(UIApplication application, NSDictionary launchOptions)
    {
        // Methods
        return base.FinishedLaunching(application, launchOptions);
    }

    public override bool OpenUrl(UIApplication application, NSUrl url, NSDictionary options)
    {
        try
        {
            // Methods
            App theApp = App.Current as App;

            switch (url.Host)
            {
                case "method1":
                    theApp?.Method1();
                    break;
                case "method2":
                    theApp?.Method2();
                    break;
            }
        }
        catch (Exception ex)
        {
            ...
        }

        return true;
    }

...

ActionViewController:

public partial class ActionViewController : UIViewController
{
    public ActionViewController(ObjCRuntime.NativeHandle handle) : base(handle)
    {
    }

    public override void DidReceiveMemoryWarning()
    {
        base.DidReceiveMemoryWarning();
    }

    public override async void ViewDidLoad()
    {
        base.ViewDidLoad();
        // Methods
ExecuteApp();
    }


    private void ExecuteApp()
    {
        NSUrl theUrl = new NSUrl("app://method1/file://doc");
        NSDictionary options = new NSDictionary();
        Action<bool> theAction = null;
        UIApplication.SharedApplication.OpenUrl(theUrl, options, theAction);
        ExtensionContext.CompleteRequest(ExtensionContext.InputItems, null);
    }

    partial void DoneClicked(NSObject sender)
    {
        // Return any edited content to the host app.
        // This template doesn't do anything, so we just echo the passed-in items.
        ExtensionContext.CompleteRequest(ExtensionContext.InputItems, null);
    }
}

iOS project:

<Project Sdk="Microsoft.NET.Sdk">
	<PropertyGroup>
		<TargetFrameworks>net9.0-ios</TargetFrameworks>
		<OutputType>Exe</OutputType>
		<UseMaui>true</UseMaui>
		<SingleProject>false</SingleProject>
		<RootNamespace>...</RootNamespace>
		<SupportedOSPlatformVersion>13.0</SupportedOSPlatformVersion>
		<ImplicitUsings>true</ImplicitUsings>
		<ApplicationTitle>...</ApplicationTitle>
		<ApplicationId>...</ApplicationId>
		<ApplicationDisplayVersion>2</ApplicationDisplayVersion>
		<ApplicationVersion>1</ApplicationVersion>
	</PropertyGroup>
	<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
		<IsPublishable>True</IsPublishable>
		<CreatePackage>false</CreatePackage>
	</PropertyGroup>
	<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
		<IsPublishable>True</IsPublishable>
		<CreatePackage>false</CreatePackage>
	</PropertyGroup>
	<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|net9.0-ios|AnyCPU'">
		<CodesignProvision>Developer ...</CodesignProvision>
		<CodesignKey>Apple Development: ...</CodesignKey>
		<MtouchLink>SdkOnly</MtouchLink>
	</PropertyGroup>
	<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net9.0-ios|AnyCPU'">
		<CodesignProvision>Distribution ...</CodesignProvision>
		<CodesignKey>Apple Distribution: ...</CodesignKey>
	</PropertyGroup>

	<ItemGroup>
		<ProjectReference Include="..\...Ext1\..Ext1.csproj">
			<IsAppExtension>true</IsAppExtension>
			<IsWatchApp>false</IsWatchApp>
		</ProjectReference>
		<ProjectReference Include="..\...Ext2\..Ext2.csproj">
			<IsAppExtension>true</IsAppExtension>
			<IsWatchApp>false</IsWatchApp>
		</ProjectReference>
		<ProjectReference Include="..\...Ext3\..Ext3.csproj">
			<IsAppExtension>true</IsAppExtension>
			<IsWatchApp>false</IsWatchApp>
		</ProjectReference>
		<ProjectReference Include="..\...\...csproj" />
	</ItemGroup>
	<ItemGroup>
		<PackageReference Include="Microsoft.Maui.Controls" Version="9.0.120" />
		<PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="9.0.120" />
	</ItemGroup>
</Project>

Extension:

<Project Sdk="Microsoft.NET.Sdk">
	<PropertyGroup>
		<TargetFramework>net9.0-ios</TargetFramework>
		<OutputType>Library</OutputType>
		<SupportedOSPlatformVersion>13.0</SupportedOSPlatformVersion>
		<ApplicationId>...</ApplicationId>
		<ApplicationDisplayVersion>2</ApplicationDisplayVersion>
		<ApplicationVersion>1</ApplicationVersion>
		<Registrar>static</Registrar>
	</PropertyGroup>

	<PropertyGroup>
		<IsAppExtension>True</IsAppExtension>
		<IsWatchExtension>False</IsWatchExtension>
	</PropertyGroup>

	<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
		<CreatePackage>false</CreatePackage>
		<CodesignProvision>Developer ...</CodesignProvision>
		<CodesignKey>Apple Development: ...</CodesignKey>
		<MtouchLink>SdkOnly</MtouchLink>
	</PropertyGroup>
	<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
		<CreatePackage>false</CreatePackage>
		<CodesignProvision>Distribution ...</CodesignProvision>
		<CodesignKey>...</CodesignKey>
	</PropertyGroup>
</Project>

IPA created on two different Macs and they work (I have a post on how I did it, it's just a matter of changing net8 to net9) Run/IPA with Visual Code):
Mac1 (Virtual con VMware): SDK: 9.0.303, workload: ios 18.5.9207/9.0.100, maui 9.0.51/9.0.100, macOS: Sequoia 15.5, XCode: 16.4 + iOS 18.5
Mac2: SDK: 9.0.306, workload: ios 26.0.9752/9.0.100, maui 9.0.111/9.0.100, macOS: Tahoe 26.1, XCode: 26.0 + iOS 26.0

Tested on iOS 26.0 emulator, iPhone 14 iOS 18.5, iPhone 14 iOS 26.0, iPhone 8 iOS 16.7.11

Everything works flawlessly.

[bnSonic]

i think in the extension project this one is the key: <Registrar>static</Registrar>
👍

[hflexgrig]

Appstore just approved my MAUI dotnet 9 app with share extension. My app critically needed this functionality, especially when taking screenshot and sending to my app for AI OCR scanning.

I'm so excited!

ScreenRecording_08-06-2025.00-26-07_1.mp4

[gardea]

@hflexgrig @VladislavAntonyuk tried versioning, applied cleaning of all Xamarin folders (basically starting from scratch, I had to redo all provisioning). I tried with latest VS Code and .NET Meteor, on .NET version 9.0.304 but I couldn't get over a new kind of error, which relates to the SayHello task timing out. When doing the same from VS 2022, everything works just fine, if I remove the reference to the share extension project.

One thing to notice is that on the latest versions mentioned above, the projects wouldn't even compile unless these two MSBuild properties are set up.

<DotNetRuntimePath>/Users/{username}/Library/Caches/Xamarin/XMA/Runtimes/dotnet/dotnet</DotNetRuntimePath> <_DotNetRootRemoteDirectory>/Users/{username}/Library/Caches/Xamarin/XMA/SDKs/dotnet/</_DotNetRootRemoteDirectory>

The first requires a custom install of .NET runtime on the MAC

dotnet-install.sh --install-dir '/Users/{username}/Library/Caches/Xamarin/XMA/Runtimes/dotnet' --runtime dotnet --version 9.0.5 --architecture '<auto>' --no-path

And then the .dotnet folder under /Users/{username}/needs to be manually configured for r/w, otherwise the compiler fails while trying to create the file 9.0.304.toolpath.sentinel in that folder.

For now, I am reverting to use CFBundleDocumentTypes in Info.plist. I needed the share extension to be able to register the app to process screenshots, which is not covered by CFBundleDocumentTypes.

[hflexgrig]

Your project is in Xamarin? not migrated to MAUI?

[gardea]

@hflexgrig my project is pure MAUI. As for the share extension, I simply took the extension project from @VladislavAntonyuk 's MAUI samples (basically "the template"), fixed the Entitlements.plist and Info.plist, and incorporated it in my existing solution. Not sure why you assumed is in Xamarin; if it's the paths and the tooling, then that's just the way MAUI tooling is under the cover (old Xamarin).

[hflexgrig]

Just some weird configuration there, I don't have of those in my projects. Then maybe you could try just add global.json file configuration in your user's root folder?

{ "sdk": { "version": "9.0.303", "allowPrerelease": true } }

[RickEpworth]

@gardea - I have been running into the same issue but for an iOS CallDirectory extension, looks like there's a problem with building ios app extensions remotely from Windows.

I switched to the free 30 day trial of Rider on the MAC and can now compile ios app extensions. Note, I did not try building the samples provided by Vlad but your issue is identical to mine.

dotnet/macios#23516

[hflexgrig]

In iOS 26 looks like share extension project crashing, investigating why...

[Mooogler88]

Is anyone getting FileProviderExtension working.
I have the issue that the .appix file created but it is not bundled into the .ipa
Is there any sample where FileProviderExtension works so that the app appears in the "Locations" area on iOS

Edit: We got it now appearing in locations

Both the DocumentPickerExtension And the DocumentFileProviderExtension must be included. This is mentioned nowhere and shows that Apple is the worst company.

When I tab on it, a white screen with a silly apple spinner pops in and disappears after 1 second.
Now the next is how do we get a simple "Hello.txt" to appear.

Is there any working sample to look into

[Mooogler88]

Update:
I got a sample working showing 2 simple hello world files on iOS. It requires just the DocumentFileProviderExtension WITHOUT the DocumentPickerExtension!

It took 2 weeks to get it working. Unfortunately my employer prohibit me from sharing how to set it up :(

[rmorin04]

Are you building the app with xcode 26? We had a working solution when our app was built against 16.4, but with 26 it completely stopped working

[Mooogler88]

I am using XCode 16.3 and Visual Studio Code as environment. Sadly I am not allowed to share much.
What I can share is how I got it working:

I got it working by reverse engineering this sample in swift and convert it to C#:
https://www.kodeco.com/697468-ios-file-provider-extension-tutorial

[jho123456]

I've tried to follow Vladislav's template but when I build and have a look inside my folder:

E:\Dev\Projects\Maui\MyApp.ShareExt.StripDown\ShareExtension.iOS\bin\Debug\net9.0-ios\ios-arm64\ShareExtension.iOS.appex

All the files contained within have 0 bytes.

Below are my host and extension project files. I've checked the following multiple times over and can confirm they are correct.

• certs
• identifiers
• profiles
• devices
• info.plist's
• Entitlements.plist's

Any ideas as to why this is happening?

MyApp.csproj

<Project Sdk="Microsoft.NET.Sdk">

	<PropertyGroup>
		<TargetFrameworks>net9.0-ios</TargetFrameworks> 

		<OutputType>Exe</OutputType>
		<RootNamespace>MyApp</RootNamespace>
		<UseMaui>true</UseMaui>
		<SingleProject>true</SingleProject>
		<ImplicitUsings>enable</ImplicitUsings>
		<Nullable>enable</Nullable>

		<!-- Display name -->
		<ApplicationTitle>MyApp</ApplicationTitle>

		<!-- App Identifier -->
		<ApplicationId>com.MyCompany.MyApp</ApplicationId>

		<!-- Versions -->
		<ApplicationDisplayVersion>1.0</ApplicationDisplayVersion>
		<ApplicationVersion>1</ApplicationVersion>

		<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">12.2</SupportedOSPlatformVersion>
		<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'maccatalyst'">13.1</SupportedOSPlatformVersion>
		<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'android'">21.0</SupportedOSPlatformVersion>
		<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'">10.0.17763.0</SupportedOSPlatformVersion>
		<TargetPlatformMinVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'">10.0.17763.0</TargetPlatformMinVersion>
		<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'tizen'">6.5</SupportedOSPlatformVersion>
		<AssemblyVersion></AssemblyVersion>
		<FileVersion></FileVersion>
	</PropertyGroup>


	<PropertyGroup>
		<!-- Other properties -->
		<!-- https://stackoverflow.com/questions/47727884/build-xamarin-android-project-unsucessfully-error-xa4212 -->
		<AndroidErrorOnCustomJavaObject>false</AndroidErrorOnCustomJavaObject>
	</PropertyGroup>

	<!-- This group suggested by Copilot to allow compatibility with different size emulators, e.g. youtube 3-4 aspect ratios -->
	<PropertyGroup>
		<AndroidPackageFormats>aab;apk</AndroidPackageFormats>
		<AndroidSupportedScreenDensities>ldpi;mdpi;hdpi;xhdpi;xxhdpi;xxxhdpi</AndroidSupportedScreenDensities>
		<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
	</PropertyGroup>


	<!-- *********************   SHARE EXTENSION   ********************** -->

	<ItemGroup Condition="'$(TargetFramework)' == 'net9.0-ios'">
		<ProjectReference Include="ShareExtension.iOS\ShareExtension.iOS.csproj">
			<IsAppExtension>true</IsAppExtension>
			<IsWatchApp>false</IsWatchApp>
			<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
		</ProjectReference>
	</ItemGroup>

	<!-- ============ -->
	<!-- Provisioning -->

	<PropertyGroup Condition="'$(TargetFramework)'=='net9.0-ios'">
		<ProvisioningType>manual</ProvisioningType>
	</PropertyGroup>

	<!-- Development -->
	<PropertyGroup Condition="'$(TargetFramework)'=='net9.0-ios'">
	  <CodesignKey>Apple Development: My Name (ABC1234567)</CodesignKey>
	  <CodesignProvision>Development MyApp</CodesignProvision>
	  <CodesignEntitlements>Platforms\iOS\Entitlements.plist</CodesignEntitlements>
	</PropertyGroup>
	
	<!-- ============ -->

	
	<ItemGroup>
		<!-- ======
		
		Lots of Resource and code file declarations
		
		====== -->
	</ItemGroup>
</Project>

ShareExtension.csproj

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net9.0-ios</TargetFramework>
    <OutputType>Library</OutputType>
    <ApplicationId>com.MyCompany.MyApp.ShareExtension</ApplicationId>
    <Nullable>enable</Nullable>
    <ImplicitUsings>true</ImplicitUsings>
    <SupportedOSPlatformVersion>12.2</SupportedOSPlatformVersion>

    <RuntimeIdentifier>ios-arm64</RuntimeIdentifier>
   
		<UseMaui>true</UseMaui>

    <TrimMode Condition="'$(Configuration)' == 'Release'">full</TrimMode>
  </PropertyGroup>

  <PropertyGroup>
      <IsAppExtension>true</IsAppExtension>
      <IsWatchExtension>false</IsWatchExtension>
      <ProvisioningType>manual</ProvisioningType>
  </PropertyGroup>

  <!-- ************ -->
  <!-- Provisioning -->

  <!-- Development -->

	<PropertyGroup Condition="'$(TargetFramework)'=='net9.0-ios'">
      <CodesignKey>Apple Development: My Name (ABC1234567)</CodesignKey>
      <CodesignProvision>Development MyApp Ext</CodesignProvision>
      <CodesignEntitlements>Entitlements.plist</CodesignEntitlements>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="9.0.82" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Update="Microsoft.Maui.Controls" Version="9.0.82" />
  </ItemGroup>

</Project>

[bnSonic]

Well - I’m using shareExtension in two of my Maui apps on iOS. I’ve read your struggle but I have no idea what is going wrong.

I’m working in a Mac. I have installed the .net9 framework from Microsoft. Installed VSCode with the csharp extension. With the dotnet command installed the workloads for Maui etc

a possible difference: my apps are migrated Xamarin apps. So every app has 3 projects (the main/shared Maui one, the iOS specific one and the specific Android project) - plus the sharedExtension project which is iOS specific too.

I remember a bit of a struggle with the options in the csproj file of the extension to make it work but at least with the .net9 / Maui 9.0.120 projects it’s working.
for company privacy reasons I cannot share the full code - and it’s very unclear what exactly is not fitting in your environment so I have a hard time offering specific help :/

one thing I still have:
I build the releases from the command line. The app builds and the shareExtension is build too automatically (shure, it’s in the solution and it’s used by the app)
BUT I have to build the iOS App TWICE to make it work :)) if I build just once, Apple would report some weird error when I try to upload the app to TestFlight.

[jho123456]

Thanks for you reply @bnSonic.

I was working dotnet9, no luck. Upgraded to dotnet10 recently, same problem.

I also build from the Mac command line, though I am able to succeed on my first build. (For Android I have to build twice).

I have also ported from Xamarin. In fact, I think I may have copied the info.plist files directly across without change.

[bnSonic]

OK, I opened my solution and here are the parts of the .csproj (shareExtension project and iOS-Application project) and some other files around it. Plus the info.plist and some files inside the share extension
I think other code-files inside the extension are not relevant for the extension to at least show up in the share-sheet (but only 90% sure about that)

I Remember that I struggled some time and I've read here and some other parts of the internet to stick together all properties in the .csproj files. Later my biggest problem not to let my extension show up in the share sheet but to really move some files over to my app and OPEN my app from within the extension - but I seems your problem is way more basic so I hope this one helps you.

If you read some parameter and say: "na, I don't this one…" - think twice or at least try it … for example set the Watch-Thing to "false" was needed IIRC

ShareExtension .csproj (most part of it)

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
    <DeviceSpecificBuild>false</DeviceSpecificBuild>
    <ProvisioningType>manual</ProvisioningType>
    <LangVersion>latest</LangVersion>
    <GenerateAssemblyInfo>false</GenerateAssemblyInfo>
    <TargetFramework>net9.0-ios</TargetFramework>
    <UseMaui>True</UseMaui>
    <SupportedOSPlatformVersion>13.0</SupportedOSPlatformVersion>
    <ImplicitUsings>enable</ImplicitUsings>
	  <!-- Maui: Add to fix builds on Windows OS -->
	  <ApplicationId>de.company.app.Share</ApplicationId>
  </PropertyGroup>
  <PropertyGroup>
    <!-- Maui: Register as app extension -->
    <IsAppExtension>true</IsAppExtension>
    <IsWatchExtension>false</IsWatchExtension>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
    <DeviceSpecificBuild>false</DeviceSpecificBuild>

    <!-- Symbole behalten für Crash-Symbolikation -->
    <DebugType>portable</DebugType>

    <OutputPath>bin\iPhone\Release</OutputPath>
    <WarningLevel>4</WarningLevel>
    <CodesignEntitlements>Entitlements.plist</CodesignEntitlements>
    <ConsolePause>false</ConsolePause>
    <CodesignExtraArgs />
    <CodesignResourceRules />

    <!-- Diagnose: alles so wenig wie möglich weglinken/trimmen -->
    <PublishTrimmed>true</PublishTrimmed> 
    <MtouchLink>SdkOnly</MtouchLink> 
    <MtouchExtraArgs>--registrar:static</MtouchExtraArgs>
    <MtouchNoSymbolStrip>true</MtouchNoSymbolStrip>
    <UseInterpreter>true</UseInterpreter>

    <CodesignKey>MyDistributionKeyName</CodesignKey>
    <CodesignProvision>MyDistributionProvisioningProfileForTheExtensionDifferentThanForTheAppItself</CodesignProvision>
    <MtouchUseLlvm>true</MtouchUseLlvm>
    <RuntimeIdentifier>ios-arm64</RuntimeIdentifier>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(RunConfiguration)' == 'Default' ">
    <AppExtensionDebugBundleId />
  </PropertyGroup>
  <ItemGroup>
    <ProjectReference Include="other.csproj" />
    <ProjectReference Include="yetanother.csproj" />
  </ItemGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.Maui.Controls" Version="9.0.120" />
    <PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="9.0.120" />
  </ItemGroup>
</Project>

ShareExtension Entitlements (not sure if this is needed for ShareExtension alone but we have it anyway)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>keychain-access-groups</key>
    <array>
      <string>$(AppIdentifierPrefix)de.company.Shared</string>
    </array>
    <key>com.apple.security.application-groups</key>
    <array>
      <string>group.de.company.Shared</string>
    </array>
  </dict>
</plist>

ShareExtension Info.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CFBundleDevelopmentRegion</key>
	<string>de</string>
	<key>CFBundleDisplayName</key>
	<string>my project name</string>
	<key>CFBundleIdentifier</key>
	<string>de.company.app.Share</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>my project name Share Extension</string>
	<key>CFBundlePackageType</key>
	<string>XPC!</string>

	<key>CFBundleSignature</key>
	<string>????</string>
	<key>MinimumOSVersion</key>
	<string>13.0</string>
	<key>NSExtension</key>

	<dict>
		<key>NSExtensionAttributes</key>
		<dict>
			<key>NSExtensionActivationRule</key>
			<dict>
				<key>NSExtensionActivationSupportsFileWithMaxCount</key>
				<integer>30</integer>
				<key>NSExtensionActivationSupportsImageWithMaxCount</key>
				<integer>30</integer>
				<key>NSExtensionActivationSupportsMovieWithMaxCount</key>
				<integer>30</integer>
				<key>NSExtensionActivationSupportsWebPageWithMaxCount</key>
				<integer>30</integer>
			</dict>
		</dict>
		<key>NSExtensionMainStoryboard</key>
		<string>MainInterface</string>
		<key>NSExtensionPointIdentifier</key>
		<string>com.apple.share-services</string>
	</dict>

	<key>LSApplicationQueriesSchemes</key>
	<array>
		<string>myscheme</string>
	</array>

</dict>
</plist>

MainInterface.storyboard

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<document type="com.apple.InterfaceBuilder3.CocoaTouch.Storyboard.XIB" version="3.0" toolsVersion="6150.1" systemVersion="13D65" targetRuntime="iOS.CocoaTouch" propertyAccessControl="none" useAutolayout="YES" useTraitCollections="YES" initialViewController="j1y-V4-xli">
    <dependencies>
        <plugIn identifier="com.apple.InterfaceBuilder.IBCocoaTouchPlugin" version="6148"/>
    </dependencies>
    <scenes>
        <!--Share View Controller-->
        <scene sceneID="ceB-am-kn3">
            <objects>
                <viewController id="j1y-V4-xli" customClass="ShareViewController" customModuleProvider="" sceneMemberID="viewController">
                    <layoutGuides>
                        <viewControllerLayoutGuide type="top" id="8bI-gs-bmD"/>
                        <viewControllerLayoutGuide type="bottom" id="d5i-Ba-RvD"/>
                    </layoutGuides>
                    <view key="view" opaque="NO" contentMode="scaleToFill" id="wbc-yd-nQP">
                        <rect key="frame" x="0.0" y="0.0" width="480" height="480"/>
                        <autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
                        <color key="backgroundColor" white="0.0" alpha="0.0" colorSpace="calibratedWhite"/>
                        <simulatedOrientationMetrics key="simulatedOrientationMetrics" orientation="landscapeRight"/>
                    </view>
                </viewController>
                <placeholder placeholderIdentifier="IBFirstResponder" id="CEy-Cv-SGf" userLabel="First Responder" sceneMemberID="firstResponder"/>
            </objects>
            <point key="canvasLocation" x="539" y="97"/>
        </scene>
    </scenes>
</document>

.csproj of the iOS App (part of it)

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <DeviceSpecificBuild>false</DeviceSpecificBuild>
    <ProvisioningType>manual</ProvisioningType>
    <TargetFramework>net9.0-ios</TargetFramework>
    <UseMaui>True</UseMaui>
    <SupportedOSPlatformVersion>13.0</SupportedOSPlatformVersion>
    <PackageId>company.app.iOS</PackageId>
    <Configurations>Debug;Release</Configurations>
    <Platforms>AnyCPU</Platforms>
  </PropertyGroup>
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <IPhoneResourcePrefix>Resources</IPhoneResourcePrefix>
    <SccProjectName>SAK</SccProjectName>
    <SccLocalPath>SAK</SccLocalPath>
    <SccAuxPath>SAK</SccAuxPath>
    <SccProvider>SAK</SccProvider>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
    <AssemblyTitle>company.app.iOS</AssemblyTitle>
    <Copyright>Copyright ©  2014</Copyright>
    <AssemblyVersion>1.0.0.0</AssemblyVersion>
    <FileVersion>1.0.0.0</FileVersion>
    <!-- Maui: Use .NET HTTP client instead of iOS HTTP client, to make signalr work -->
    <!-- Consider downsides: https://github.com/xamarin/xamarin-macios/issues/18635#issuecomment-1725058814 -->
    <UseNativeHttpHandler>false</UseNativeHttpHandler>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
    <Optimize>true</Optimize>
    <ErrorReport>prompt</ErrorReport>
    <warninglevel>4</warninglevel>
    <langversion>latest</langversion>

    <DebugSymbols>true</DebugSymbols>
    <DebugType>portable</DebugType>
    <CodesignKey>MyDistributionKeyName</CodesignKey>
    <CodesignEntitlements>Entitlements.plist</CodesignEntitlements>
    <CodesignProvision>MyDistributionProvisioningProfileForAppDifferentThanForTheExtension</CodesignProvision>
    <BuildIpa>true</BuildIpa>
    <RuntimeIdentifiers>ios-arm64</RuntimeIdentifiers>
    <MtouchNoSymbolStrip>true</MtouchNoSymbolStrip>
    <UseInterpreter>false</UseInterpreter>
    <MtouchLink>SdkOnly</MtouchLink>
    <MtouchUseLLVM>true</MtouchUseLLVM> 
    <MtouchFastDev>false</MtouchFastDev>
    <EnableAotCompilation>true</EnableAotCompilation> 
  </PropertyGroup>

  <ItemGroup>
    <ProjectReference Include="..\company.app.ShareExtension.iOS\company.app.ShareExtension.iOS.csproj">
      <IsAppExtension>true</IsAppExtension>
      <IsWatchExtension>false</IsWatchExtension>
    </ProjectReference>
    <ProjectReference Include="..\company.app\company.app.csproj" /> <!-- reference to the main maui project -->
  </ItemGroup>
</Project>

[bnSonic]

I build on Mac with this command line

dotnet publish -f net9.0-ios \                                                                            
  -c Release \
  -p:ArchiveOnBuild=true

[jho123456]

@bnSonic Thanks so much for sharing, very generous of you. I'll take a careful look through this and try it out.

[Rhywden]

Is it possible to create iOS Extensions with .NET MAUI? (https://docs.microsoft.com/en-us/xamarin/ios/platform/extensions-with-xamarinforms)

@VladislavAntonyuk Yeah, no. At least not with Visual Studio 2026 - as Xamarin does not exist anymore. Also, this "solution" has the problem that the other targets will complain because a project reference to an iOS extension is incompatible with Android, Windows and MacOS Catalyst.

I find this lack of an official solution very ... disturbing.

[VladislavAntonyuk]

It is possible, you can use templates I created. The one important thing, you need to use macOS to build your project. It doesn't work well if you build from windows.
You can reference the project only for iOS target framework. Other platforms are not affected.

[MarkMcCormackSF]

Background: We've managed to make a small MAUI iOS & Android application to wrap a PWA (.net 9.0-ios).

I started looking into supporting images with our push notifications on iOS a few days ago, as I noticed it was apparently possible. But we had to make a "Service Extension". My heart sank, as iOS is always the most problematic side of the mobile coin for us.

TLDR, I really appreciate this thread, there was a lot of great information posted. I did however get the bottom and notice now that ".. you need to use macOS to build your project. It doesn't work well if you build from windows." My heart sank further ..

Although after hacking around and using bits of info from here ..

dotnet/macios#24052
+
VladislavAntonyuk/vladislavantonyuk.github.io#72

.. I've managed to build the extension as a sub-project into my main MAUI application, looking into the main application deployment cache it now exists in a /Plugins/NotificationServiceExtension.appex directory! (which I found out is the same structure as is used for macOS extensions).

UPDATE: 27/02/2026 OMG .. it started working!! The final issue was the build process ...
#3289 (reply in thread)

If I can actually get this into a production solution I'll write the entire thing up!

[jho123456]

Hi @MarkMcCormackSF , completely agree, the iOS side of Maui is very painful.

I'd like to ask, what do you get from this post:

dotnet/macios#24052

Was it the changes to Xamarin.Shared.targets that helped you?

I tried to make the same changes, albeit modified to account for .net10.0, but it's still not working for me.

[MarkMcCormackSF]

Hi @jho123456,

I think the changes here as part of #24052 will not help you are it looks like you are building the extension OK now. But for reference, and for anyone else who finds this thread the changes ..

dotnet/macios#24052 (comment)

Fixes the build of the extension I was getting via a hard-exit error, this is as I'm using Windows Visual Studio remote build to mac.

[jho123456]

I've had another go at my project, trying to incorporate ideas from @VladislavAntonyuk and @bnSonic into my csproj files.

I'm now working fully on VS Code Mac. The Share Extension is now working on the simulator, but not on a release build I deployed to TestFlight.

When I look in the Release bin folder, I can't see any Plugin folder, nor appex file.

Any ideas?

(Btw I also tried the suggestion from @MarkMcCormackSF , trying out MtouchExtraArgs, UseInterpreter..etc. to no avail)

Here is my latest host csproj file:

<Project Sdk="Microsoft.NET.Sdk">

	<PropertyGroup>
		<TargetFrameworks>net10.0-ios</TargetFrameworks> 

		<OutputType>Exe</OutputType>
		<RootNamespace>MyApp</RootNamespace>
		<UseMaui>true</UseMaui>
		<SingleProject>true</SingleProject>
		<ImplicitUsings>enable</ImplicitUsings>
		<Nullable>enable</Nullable>

		<!-- Display name -->
		<ApplicationTitle>MyApp</ApplicationTitle>

		<!-- App Identifier -->
		<ApplicationId>com.MyCompany.MyApp</ApplicationId>

		<!-- Versions -->
		<ApplicationDisplayVersion>1.0</ApplicationDisplayVersion>
		<ApplicationVersion>1</ApplicationVersion>

		<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">12.2</SupportedOSPlatformVersion>
		<AssemblyVersion></AssemblyVersion>
		<FileVersion></FileVersion>
	</PropertyGroup>


	<PropertyGroup>
		<!-- Other properties -->
		<!-- https://stackoverflow.com/questions/47727884/build-xamarin-android-project-unsucessfully-error-xa4212 -->
		<AndroidErrorOnCustomJavaObject>false</AndroidErrorOnCustomJavaObject>
	</PropertyGroup>

	<!-- This group suggested by Copilot to allow compatibility with different size emulators, e.g. youtube 3-4 aspect ratios -->
	<PropertyGroup>
		<!-- Compiler says this is deprecated, remove it-->
		<!-- <AndroidSupportedAbis>armeabi-v7a;x86;arm64-v8a;x86_64</AndroidSupportedAbis> -->
		<AndroidPackageFormats>aab;apk</AndroidPackageFormats>
		<AndroidSupportedScreenDensities>ldpi;mdpi;hdpi;xhdpi;xxhdpi;xxxhdpi</AndroidSupportedScreenDensities>
		<!-- Added when using rhythm pcm buffers in iOS, you can see the 'unsafe' tag in code-->
		<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
	</PropertyGroup>

	<!-- *********************   SHARE EXTENSION   ********************** -->

	<ItemGroup Condition="'$(TargetFramework)' == 'net10.0-ios'">
		<ProjectReference Include="ShareExtension.iOS\ShareExtension.iOS.csproj">
			<IsAppExtension>true</IsAppExtension>
			<IsWatchApp>false</IsWatchApp>
		</ProjectReference>
	</ItemGroup>

	<!-- ============ -->
	<!-- Provisioning -->

	<!-- Development -->
	<!-- <PropertyGroup Condition="'$(TargetFramework)'=='net10.0-ios'">
	  <CodesignKey>Apple Development: My Name (ABC1234567)</CodesignKey>
	  <CodesignProvision>Development MyApp</CodesignProvision>
	</PropertyGroup> -->
	
	<!-- Distribution-->
	<PropertyGroup Condition="'$(TargetFramework)'=='net10.0-ios'">
	  <MtouchUseLlvm>False</MtouchUseLlvm>
	  <AotAssemblies>True</AotAssemblies>          
	  <CodesignKey>Apple Distribution: MY COMPANY (ABC1234567)</CodesignKey>
	  <CodesignProvision>Distribution MyApp</CodesignProvision> 
	</PropertyGroup> 

	<PropertyGroup Condition="'$(TargetFramework)'=='net10.0-ios'">
		<CodesignEntitlements>Platforms\iOS\Entitlements.plist</CodesignEntitlements>
	</PropertyGroup>
	<!-- ============ -->

	
	<ItemGroup>
		<!-- ======
		
		Lots of Resource and code file declarations
		
		====== -->
	</ItemGroup>
</Project>

and here is the ShareExt csproj file:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net10.0-ios</TargetFramework>
    <OutputType>Library</OutputType>
    <ApplicationId>com.MyCompany.MyApp.ShareExtension</ApplicationId>
    <Nullable>enable</Nullable>
    <ImplicitUsings>true</ImplicitUsings>
    <SupportedOSPlatformVersion>12.2</SupportedOSPlatformVersion>

 		<UseMaui>true</UseMaui>

  </PropertyGroup>

  <PropertyGroup>
      <IsAppExtension>true</IsAppExtension>
      <IsWatchExtension>false</IsWatchExtension>
  </PropertyGroup>

  <!--copied from Vlad-->
	<PropertyGroup>
		<Registrar>static</Registrar>
	</PropertyGroup>

  <!-- ************ -->
  <!-- Provisioning -->

  <!-- Development -->
<!-- 
	<PropertyGroup Condition="'$(TargetFramework)'=='net10.0-ios'">
      <CodesignKey>Apple Development: My Name (ABC1234567)</CodesignKey>
      <CodesignProvision>Development MyApp Ext</CodesignProvision>
  </PropertyGroup> -->

  	<!-- Distribution-->
	<PropertyGroup Condition="'$(TargetFramework)'=='net10.0-ios'">
	  <MtouchUseLlvm>False</MtouchUseLlvm>
	  <AotAssemblies>True</AotAssemblies>          
	  <CodesignKey>Apple Distribution: MY COMPANY (ABC1234567)</CodesignKey>
	  <CodesignProvision>Distribution MyApp Ext</CodesignProvision> 
	</PropertyGroup> 

    <!--copied from Vlad-->
	<ItemGroup>
		<None Include="Entitlements.plist" />
	</ItemGroup>

	<!-- ENTITLEMENTS - May need to add this manually-->
	<PropertyGroup Condition="'$(TargetFramework)'=='net10.0-ios'">
		<CodesignEntitlements>Entitlements.plist</CodesignEntitlements>
	</PropertyGroup>


</Project>

[jho123456]

Thanks for your reply @bnSonic, you're right it was just an anonymizing error, will correct it above.

What I'm also noticing is that the ShareExtension bin and obj folders have Debug subfolders, but none for Release. The extension project seems to not even be being built.

[MarkMcCormackSF]

At the moment I have only got my extension building and running in 'Debug', this week I was going to try and get something into our final production build and upload to TestFlight.

If I can actually get this into a production solution I'll write the entire thing up!

Which is what I mean by this comment, as it's no good it only working in Debug. I need to see it build in Release, pass upload via Apple Transporter, pass validation on Apple Connect and appear in TestFlight, install back onto my device and THEN still actually work correctly with the extension.

At a glance your project files look OK, I will mention (probably unrelated to where you are now) this code block was essential for me to get the extension actually hooked into the iPhone, I'm use a real device.

  <PropertyGroup>
    <PublishTrimmed>true</PublishTrimmed> 
    <MtouchLink>SdkOnly</MtouchLink> 
    <MtouchNoSymbolStrip>true</MtouchNoSymbolStrip>
    <MtouchExtraArgs>--registrar:dynamic</MtouchExtraArgs>
    <UseInterpreter>false</UseInterpreter>
  </PropertyGroup>

This is for the extension project and I'm going to test more, but I expect it is probably the removal of symbol stripping that is the fix.

[jho123456]

Thanks for your reply Mark. Just added the PropertyGroup you mentioned to both Host and Extension csproj. Still not able to generate a Release appex.

Will keep searching for other options. Cheers

[MarkMcCormackSF]

Thanks for your reply Mark. Just added the PropertyGroup you mentioned to both Host and Extension csproj. Still not able to generate a Release appex.

By the way, with the PropertyGroup above I only ever got the extension to work 50% of the time, so every other notification would result in an "Object" registration failure that I could see by using the mac Console application connected to my phone over USB (and the notification would be without image and with the non-modified notification content).

This is my latest section for that and [1] this seems to have the extension working 100% of the time and [2] it has been allowed upload via Transporter to App Store Connect and works via TestFlight. I still can not guarantee that it will get into a full App Store release OK, I have yet to attempt a new application version.

<PropertyGroup>
  <PublishTrimmed>true</PublishTrimmed> 
  <MtouchLink>SdkOnly</MtouchLink> 
  <MtouchExtraArgs>--registrar:dynamic</MtouchExtraArgs>
  <MtouchNoSymbolStrip>true</MtouchNoSymbolStrip>
  <UseInterpreter>true</UseInterpreter>
  <MtouchUseLlvm>true</MtouchUseLlvm>
  <RuntimeIdentifier>ios-arm64</RuntimeIdentifier>
</PropertyGroup>

You are saying you "Still not able to generate a Release appex." ..

The only thing I can think of is to check your solution file, is that correctly setup for your "Release" build?

[MarkMcCormackSF]

Also, you can check the content of any generated IPA archive easily to see if the "/Plugin/extension.appex" directory and contents is in there using 7zip.

[jho123456]

After months of returning to this issue time and time again, only to repeatedly fail, I believe I have finally solved the problem.

The command line I have been using to publish my app is this:

• dotnet publish -f net10.0-ios -c Release

For some reason it wasn't generating the extension binaries for the release build.

By changing it to:

• dotnet publish MyApp.csproj -f net10.0-ios -c Release

...it finally works in TestFlight and, though I don't want to speak too soon and jinx it, hopefully it will work in production too.

Thanks to all the contributors above, every bit of information helped get me at least one step closer to the final answer. I hope my contributions here can also be of some help to others who have been facing the same problems.

This is the final piece of the puzzle in my port from Xamarin to Maui. It's taken around a year for my Maui app to finally achieve par with its Xamarin predecessor, and I have to say, it has been an extremely painful experience, and one which I feel shouldn't have been so hard.

In light of this, I'd like to leave a final word to the Maui team. I know you guys work hard on the framework, and there have been some amazing things you have done to get it to where it is today. I also follow your YouTube channels and love the enthusiasm you bring to evangelizing Maui and letting us all know about ways the framework can best be used.

But at the same time, if official support was provided for features like this shared extension, which I feel is baseline iOS functionality, it would have saved me, and I'm sure a large number of other developers a lot of pain. It has been disappointing that at least 3 years after Maui's official release, there is still no official pathway to port such a feature from Xamarin.

Features like this, which directly affect an app's users, are far more important than new features that can make a developer's life easier, but which give no tangible benefit to the end user.

Anyway just my two cents.

Thanks again to all.

[SPNGUK]

I'm using the iOS broadcast template provided by @VladislavAntonyuk with .NET 10 and VS Code, after I struggled for few weeks, I finally can get my extension runs on my ipad. But the ProcessSampleBuffer function getting call with video data every 6 seconds +. I can see a lot of these messages from Console.

default 08:34:19.121418+0000 replayd <<<< FigVirtualDisplayProcessor >>>> fvdp_ensureWritebackPixelBuffer: frame size:
default 08:34:19.121743+0000 replayd <<<< FigVirtualDisplayProcessor >>>> writebackCacheAllocateBuffer: writeback pool capacity exceeded
default 08:34:19.121774+0000 replayd <<<< FigVirtualDisplayProcessor >>>> writebackCacheAllocateBuffer: 1515: got error -6689
default 08:34:19.121799+0000 replayd <<<< FigVirtualDisplayProcessor >>>> fvdp_ensureWritebackPixelBuffer: 4074: got error -6689
default 08:34:19.138025+0000 replayd <<<< FigVirtualDisplayProcessor >>>> fvdp_ensureWritebackPixelBuffer: frame size:
default 08:34:19.138220+0000 replayd <<<< FigVirtualDisplayProcessor >>>> writebackCacheAllocateBuffer: writeback pool capacity exceeded
default 08:34:19.138298+0000 replayd <<<< FigVirtualDisplayProcessor >>>> writebackCacheAllocateBuffer: 1515: got error -6689
default 08:34:19.138323+0000 replayd <<<< FigVirtualDisplayProcessor >>>> fvdp_ensureWritebackPixelBuffer: 4074: got error -6689
default 08:34:19.141566+0000 BroadcastExt [INFO] -[RPBroadcastSampleHandler _processPayloadWithAudioSample:type:]:180 Broadcast extension received audio payload from replayd
default 08:34:19.142009+0000 replayd [INFO] -[RPSystemBroadcastSession notifyExtensionOfAudioSampleBuffer:withType:]_block_invoke_2:652 Sending 2 audio payload to broadcast extension...

I have tried to build the same with swift, the extension just works fine and no such message appears. Would anyone experienced on this and help?

[hflexgrig]

I just did full trimming on my extension project, and reduced 40mb of size

<MtouchLink>Full</MtouchLink>
<EnableTrimAnalyzer>true</EnableTrimAnalyzer>

[bulubuloa]

For anyone who ends up facing this issue:

I have an iOS Call Directory extension, which is more constrained than other extensions because it has a strict 12MB memory limit.

After upgrading my project to .NET 9, I encountered many issues—the extension kept crashing or failing to connect.

Using <UseInterpreter>true</UseInterpreter> helped resolve many cases, but not all of them. The extension was still unstable.

Eventually, I switched
<MtouchExtraArgs>--registrar:dynamic</MtouchExtraArgs> to static, which fixed the remaining issues.

Here is my final configuration:

<PublishTrimmed>true</PublishTrimmed>
<MtouchLink>SdkOnly</MtouchLink>
<MtouchExtraArgs>--registrar:static</MtouchExtraArgs>
<MtouchNoSymbolStrip>true</MtouchNoSymbolStrip>
<UseInterpreter>true</UseInterpreter>
<MtouchUseLlvm>true</MtouchUseLlvm>

Hope this help!

[bnSonic]

I think with „static“ you should be able the remove the interpreter „true“ option again. It can help to improve the runtime speed and maybe it’s even a bit smaller/lighter?

[jonmdev]

FYI, for anyone investigating this, the appex system is now broken in VS2026 and .NET 10. I previously had mine working with the advice in this thread in VS2022 and .NET 9, but as soon as switched to .NET 10 & VS2026 it broke. This is a known issue as per:

dotnet/macios#25666

No word yet on when it might be fixed it seems.

[jonmdev]

Workaround was provided there by Microsoft and fix is incoming.

[bulubuloa]

FIY: For anyone who ends up dealing with this, I decided to rewrite all iOS extensions in native Swift and embed them into the MAUI projects. This approach works with any kind of extension, is faster, provides native support, and avoids getting stuck with issues like this.

Trade-off: Of course, it’s not C#, and you can’t reference shared projects. However, I don’t think this will be an issue for most of our use cases.