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?

[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.

[vikher]

I'm encountering a challenge while attempting to generate an IPA build locally using the dotnet publish command within a .NET MAUI project that involves an iOS extension. As .NET MAUI expects a single project structure, managing the requirements of two distinct projects (main app and iOS extension) becomes tricky, particularly concerning provisioning profiles.

The current command I'm using is:

dotnet publish -f $(iOSVersion) -c $(BuildConfiguration) /p:ArchiveOnBuild=true /p:RuntimeIdentifier=ios-arm64 /p:EnableAssemblyILStripping=false /p:CodesignKey=$(CodesignKey) /p:CodesignProvision=$(CodesignProvision)

Challenge:
The problem arises as the dotnet publish command seems to accept only one provisioning profile. However, for the successful build of the iOS extension, it requires a separate provisioning profile distinct from the main app.

Query:
Is there any guidance or workaround available to handle the requirement of multiple provisioning profiles, specifically catering to the iOS extension, within the context of a unified .NET MAUI project structure? How can this limitation of the dotnet publish command be addressed to successfully build the project encompassing both the main app and the iOS extension, each with its respective provisioning profile?

Any insights, suggestions, or best practices to manage this scenario would be greatly appreciated. Thank you!

[b12kab]

Just in case it might help someone; don't compile your extensions alone (as I did above) just do the publish on the main project of the app:

dotnet publish -f net8.0-ios -r ios-arm64 -c Release -p:PublishTrimmed=true -p:ArchiveOnBuild=true src/app.csproj

[deyupopp]

did you find any solution for this? i'm encountering the same

[devperson]

I have the same issue. Are there any workarounds for this?

[IgorStrekha]

I have two Extensions (UI + NONUI) . Wallet needs it. I try to Publish it. And only one main App builds.

[devperson]

In case anyone has an issue with building an iOS app with an extension via the publish command:
In the main iOS project, replace\add the code signing attribute with the following variables (in <PropertyGroup>):

<CodesignKey>$(MAIN_SIGNING_ID)</CodesignKey>
<CodesignProvision>$(MAIN_PROV_UUID)</CodesignProvision>

Do the same for the iOS extension project with different variables:

<CodesignKey>$(NOTIFICATION_EXT_SIGNING_ID)</CodesignKey>
<CodesignProvision>$(NOTIFICATION_EXT_PROV_UUID)</CodesignProvision>

The final publish command will look like this:

- task: InstallAppleCertificate@2
      inputs:
        certSecureFile: 'Cert.p12'
        certPwd: '123456'
        keychain: 'temp'   

- task: InstallAppleProvisioningProfile@1
      displayName: Install Notification extension provisioning profile
      inputs:
        provisioningProfileLocation: 'secureFiles'
        provProfileSecureFile: 'NotificationProfile.mobileprovision'   

    - task: InstallAppleProvisioningProfile@1
      displayName: Install Main App provisioning profile
      inputs:
        provisioningProfileLocation: 'secureFiles'
        provProfileSecureFile: 'adhocProfile.mobileprovision'       

dotnet publish -f net8.0-ios -c Release /p:MAIN_SIGNING_ID='$(APPLE_CERTIFICATE_SIGNING_IDENTITY)' /p:MAIN_PROV_UUID='$(APPLE_PROV_PROFILE_UUID)' /p:NOTIFICATION_EXT_SIGNING_ID='$(APPLE_CERTIFICATE_SIGNING_IDENTITY)' /p:NOTIFICATION_EXT_PROV_UUID='8b494e74-6fcf-4705-b5d5-12d192e20159'

To find the UUID of the provisioning profile for iOS extension: open the provisioning profile with notepad++ editor and find the Guid value that starts with <key>UUID</key>, for me it was <string>eb3536c2-5de2-4084-a0ae-ef1a6398e8ca</string>. You can make the same for the main provisioning profile or use '$(APPLE_PROV_PROFILE_UUID)', which always returns the last installed provisioning profile.
Also, this workaround works with two-three extension projects as well, just add the variables for the projects as well

[unamed000]

One of the biggest challenge i'm facing is we developed a Share extension using Xamarin.Forms.

Do we have a way to build the Share extension by using MAUI Xaml yet? Otherwise we can't migrate from Xamarin -> MAUI

[yevgeny-sotnikov]

As .NET MAUI expects a single project structure, managing the requirements of two distinct projects (main app and iOS extension) becomes tricky, particularly concerning provisioning profiles.

@vikher I'll slightly sweeten the pill: Was added support for Multi-Headed MAUI projects (same structure as for Xamarin.Forms):
#7426 (comment)

[Chandrakalavaprani]

@vikher : I am facing the same issue, Have a Notification Service Extension project , therefore two provisioning profiles, Did you find a solution for the publish command issue?

[yevgeny-sotnikov]

I don't have extensions in my project

[AmanGoyal009]

Hello @brandonward34 ,

Did u found any solution of showing Share Extension in MAUI for iOS. As in my case my app name is visible in the extension but when I am trying to open the app then it's not opening and even controls are also not hitting in ShareViewController class.

Please help me if you found some solution . It will help me.

Thanks in advance :)

[FlavioGoncalves-Cayas]

Did anyone get App Groups to work between the host app and the app extension with @VladislavAntonyuks template?
Edit: Nevermind, it works now. Forgot to assign the App Group in the identifier for the extension.

[Vignesh5690]

I have implemented (@VladislavAntonyuk Net Template) iOS Share extension. My app is now displayed in the Photos App and Safari Share Sheet. After clicking the post button, the main app did not receive the shared content. Open URL method is not hitting.

[FlavioGoncalves-Cayas]

Hi @Vignesh5690
your ViewController in the ShareExtension project should appear when selecting your app in the share sheet. From there you can link to your main app.

public override void ViewDidAppear(bool animated)
{
    base.ViewDidAppear(animated);

    CompleteRequest();
}

private void CompleteRequest()
{
    OpenMainAppWithUrl();
    ExtensionContext?.CompleteRequest([], null);
}
    
private static void OpenMainAppWithUrl()
{
    var url = new NSUrl($"<your CfBundleUrlScheme configured in Info.plist>://some/path");
    UIApplication.SharedApplication.OpenUrl(url, new NSDictionary(), null);
}

[PeterCR20]

If u run the app + extension on Visual Code and it deploys your extension, use .NET Meteor debugger instead .NET MAUI debugger.

[PeterCR20]

We are migrating from Visual Studio (VS) to Visual Code (VC) and in VS we had no problems running and creating the IPA. With VC we had problems but now we can run on emulators and create IPA.

Our .sln:
PCL.csproj
Android.csproj
Huawei.csproj
iOS.csproj
Ext1.csproj
Ext2.csproj
Ext3.csproj

1. Open VC and install ".NET Meteor debugger" and ".NET MAUI - Archive / Publish tool"
2. In the settings of ".NET MAUI - Archive / Publish tool" in "OSProvisioning Profiles Path" use the path from XCode where you download the profiles, in my case it is "/Users/[user]/Library/MobileDevice/Provisioning Profiles"
3. Create the launch.json file:

{ "version": "0.2.0", "configurations": [ { "name": "Run MAUI", "type": "dotnet-meteor.debugger", "request": "launch", "preLaunchTask": "dotnet-meteor: Build" } ] }

4. Create the tasks.json file

{ "version": "2.0.0", "tasks": [ { "label": "Create IPA", "type": "shell", "command": "dotnet", "args": [ "publish", "/Users/[user]/Projects/App/App.iOS/App.iOS.csproj", "-f", "net8.0-ios", "-c", "Release", "-p:ArchiveOnBuild=true", "-p:RuntimeIdentifier=ios-arm64" ], "problemMatcher": [], "group": { "kind": "build", "isDefault": true } } ] }

Now you can run the application and its extensions with meteor and when you run the task you can create the IPA.
The task does not specify any Codesign, that is why you must have the Codesign in your iOS projects (extensions and iOS project):

<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-ios|AnyCPU'"> <CodesignProvision>Distribution App Client</CodesignProvision> <CodesignKey>Apple Distribution: ... (F78...)</CodesignKey> </PropertyGroup>

[NebulaSleuth]

Does anyone else get this error when trying to compile when there is an iOS extension?

C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk.net8.0_18.0\18.0.8319\tools\msbuild\iOS\Xamarin.Shared.targets(2499,3): error MSB6006: "ditto" exited with code 1.

My main .csproj

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

    <PropertyGroup>
    <TargetFrameworks>net8.0-android;net8.0-ios;net8.0-maccatalyst</TargetFrameworks>
    <TargetFrameworks Condition="$([MSBuild]::IsOSPlatform('windows'))">$(TargetFrameworks);net8.0-windows10.0.19041.0</TargetFrameworks>
    <RuntimeIdentifiers Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">ios-arm64</RuntimeIdentifiers>
	    <!-- Uncomment to also build the tizen app. You will need to install tizen by following this: https://github.com/Samsung/Tizen.NET -->
	    <!-- <TargetFrameworks>$(TargetFrameworks);net8.0-tizen</TargetFrameworks> -->

	    <!-- Note for MacCatalyst:
	    The default runtime is maccatalyst-x64, except in Release config, in which case the default is maccatalyst-x64;maccatalyst-arm64.
	    When specifying both architectures, use the plural <RuntimeIdentifiers> instead of the singular <RuntimeIdentifier>.
	    The Mac App Store will NOT accept apps with ONLY maccatalyst-arm64 indicated;
	    either BOTH runtimes must be indicated or ONLY macatalyst-x64. -->
	    <!-- For example: <RuntimeIdentifiers>maccatalyst-x64;maccatalyst-arm64</RuntimeIdentifiers> -->

	    <OutputType>Exe</OutputType>
	    <RootNamespace>MyFriendlyEyes</RootNamespace>
	    <UseMaui>true</UseMaui>
	    <SingleProject>true</SingleProject>
	    <ImplicitUsings>enable</ImplicitUsings>
	    <Nullable>enable</Nullable>
	    <AndroidTargetSdkVersion>33</AndroidTargetSdkVersion>
	    <AndroidMinSdkVersion>21</AndroidMinSdkVersion>
	    <AndroidCompileSdkVersion>33</AndroidCompileSdkVersion>
	    <MinimumOSVersion>18.0</MinimumOSVersion>
    <WindowsSdkPackageVersion>10.0.19041.53</WindowsSdkPackageVersion>

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

	    <!-- App Identifier -->
	    <ApplicationId>com.myfriendlyeyes.mfe</ApplicationId>

	    <!-- Versions -->
	    <ApplicationDisplayVersion>99.0</ApplicationDisplayVersion>
	    <ApplicationVersion>99</ApplicationVersion>

	    <SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">15.4</SupportedOSPlatformVersion>
	    <SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'maccatalyst'">13.1</SupportedOSPlatformVersion>
	    <SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'android'">24.0</SupportedOSPlatformVersion>
	    <SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'">10.0.19041.0</SupportedOSPlatformVersion>
	    <TargetPlatformMinVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'">10.0.17763.0</TargetPlatformMinVersion>
	    <SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'tizen'">6.5</SupportedOSPlatformVersion>
	    <AndroidSigningKeyStore>Extrastrength.keystore</AndroidSigningKeyStore>
    </PropertyGroup>

    <PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|net8.0-android|AnyCPU'">
      <ApplicationTitle>My Friendly Eyes</ApplicationTitle>
      <AndroidKeyStore>True</AndroidKeyStore>
      <AndroidSigningStorePass>Thurso2683p&amp;&amp;n</AndroidSigningStorePass>
      <AndroidSigningKeyAlias>extrastrength</AndroidSigningKeyAlias>
      <AndroidSigningKeyPass>Thurso2683p&amp;&amp;n</AndroidSigningKeyPass>
    </PropertyGroup>

    <PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|net8.0-ios|AnyCPU'">
      <ApplicationTitle>My Friendly Eyes</ApplicationTitle>
      <MtouchNoSymbolStrip>False</MtouchNoSymbolStrip>
    </PropertyGroup>

    <PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|net8.0-windows10.0.19041.0|AnyCPU'">
      <ApplicationTitle>My Friendly Eyes</ApplicationTitle>
    </PropertyGroup>

    <PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-android|AnyCPU'">
      <ApplicationTitle>My Friendly Eyes</ApplicationTitle>
      <AndroidKeyStore>True</AndroidKeyStore>
      <AndroidSigningStorePass>Thurso2683p&amp;&amp;n</AndroidSigningStorePass>
      <AndroidSigningKeyAlias>extrastrength</AndroidSigningKeyAlias>
      <AndroidSigningKeyPass>Thurso2683p&amp;&amp;n</AndroidSigningKeyPass>
    </PropertyGroup>

    <PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-ios|AnyCPU'">
      <ApplicationTitle>My Friendly Eyes</ApplicationTitle>
      <MtouchNoSymbolStrip>False</MtouchNoSymbolStrip>
    </PropertyGroup>

    <PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-windows10.0.19041.0|AnyCPU'">
      <ApplicationTitle>My Friendly Eyes</ApplicationTitle>
    </PropertyGroup>

    <PropertyGroup Condition="'$(TargetFramework)'=='net8.0-ios'">
      <ProvisioningType>automatic</ProvisioningType>
      <CodesignKey>Apple Development: Created via API (7C45A6N3JS)</CodesignKey>
      <CodesignProvision>VS: com.myfriendlyeyes.mfe Development</CodesignProvision>
    </PropertyGroup>

    <ItemGroup>
	    <!-- App Icon -->
	    <MauiIcon Include="Resources\AppIcon\appicon.svg" ForegroundFile="Resources\AppIcon\appiconfg.svg" Color="#512BD4" />

	    <!-- Images -->
	    <MauiImage Include="Resources\Images\*" />
	    <MauiImage Update="Resources\Images\dotnet_bot.png" Resize="True" BaseSize="300,185" />

	    <!-- Custom Fonts -->
	    <MauiFont Include="Resources\Fonts\*" />

	    <!-- Raw Assets (also remove the "Resources\Raw" prefix) -->
	    <MauiAsset Include="Resources\Raw\**" LogicalName="%(RecursiveDir)%(Filename)%(Extension)" />
    </ItemGroup>

    <ItemGroup>
      <MauiImage Remove="Resources\Images\button.psd" />
    </ItemGroup>

    <ItemGroup>
      <None Remove="Platforms\Android\google-services.json" />
      <None Remove="Platforms\Android\proguard.txt" />
      <None Remove="Platforms\Android\Resources\drawable-xhdpi\splash_logo.png" />
      <None Remove="Resources\Images\access_ready_logo.png" />
      <None Remove="Resources\Images\access_ready_logo_dark.png" />
      <None Remove="Resources\Images\bt_icon.png" />
      <None Remove="Resources\Images\busy.png" />
      <None Remove="Resources\Images\button.png" />
      <None Remove="Resources\Images\button.psd" />
      <None Remove="Resources\Images\button_dn.png" />
      <None Remove="Resources\Images\cam_icon.png" />
      <None Remove="Resources\Images\eslogo.png" />
      <None Remove="Resources\Images\eslogo_wide.png" />
      <None Remove="Resources\Images\loc_icon.png" />
      <None Remove="Resources\Images\logo.png" />
      <None Remove="Resources\Images\mic_icon.png" />
      <None Remove="Resources\Images\notify_icon.png" />
      <None Remove="Resources\Images\owl1.png" />
      <None Remove="Resources\Images\owl2.png" />
      <None Remove="Resources\Images\tip_icon.png" />
      <None Remove="Resources\Images\user.png" />
      <None Remove="Resources\Images\warning.png" />
      <None Remove="Resources\Raw\dialing.wav" />
    </ItemGroup>

    <ItemGroup>
      <MauiSplashScreen Include="Resources\Splash\splash_logo.png" Color="#faebd7" TintColor="#583b97" />
    </ItemGroup>

    <ItemGroup>
      <GoogleServicesJson Include="Platforms\Android\google-services.json">
        <CopyToOutputDirectory>Never</CopyToOutputDirectory>
      </GoogleServicesJson>
    </ItemGroup>

    <ItemGroup>
	    <PackageReference Include="CommunityToolkit.Maui" Version="9.1.1" />
	    <PackageReference Include="CommunityToolkit.Maui.Camera" Version="1.0.5" />
	    <PackageReference Include="CommunityToolkit.Maui.MediaElement" Version="4.1.2" />
	    <PackageReference Include="CommunityToolkit.Mvvm" Version="8.4.0" />
	    <PackageReference Include="DevExpress.Maui.Controls" Version="23.2.10" />
	    <PackageReference Include="DevExpress.Maui.Editors" Version="23.2.10" />
	    <PackageReference Include="MFEClientApi" Version="2.0.0" />
    <PackageReference Include="MFECommon" Version="2.0.0" />
	    <PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="8.0.14" />
	    <PackageReference Include="Microsoft.Maui.Controls" Version="8.0.100" />
	    <PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="$(MauiVersion)" />
	    <PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="8.0.0" />
	    <PackageReference Include="Microsoft.VisualStudio.Threading" Version="17.13.61" />
	    <PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
	    <PackageReference Include="Plugin.Maui.Audio" Version="3.1.0" />
	    <PackageReference Include="Refractored.MvvmHelpers" Version="1.6.2" />
	    <PackageReference Include="SkiaSharp" Version="3.116.1" />
	    <PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.116.1" />
	    <PackageReference Include="sqlite-net-pcl" Version="1.8.116" />
	    <PackageReference Include="SQLitePCLRaw.bundle_green" Version="2.1.11" />
    </ItemGroup>

    <ItemGroup>
      <ProguardConfiguration Include="Platforms\Android\proguard.txt">
        <CopyToOutputDirectory>Never</CopyToOutputDirectory>
      </ProguardConfiguration>
    </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\CrossWebRtc\CrossWebRtc.csproj" />
  </ItemGroup>
  <ItemGroup Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">
    <ProjectReference Include="..\MFEServiceExtension\MFEServiceExtension.csproj">
      <IsAppExtension>true</IsAppExtension>
      <IsWatchApp>false</IsWatchApp>
    </ProjectReference>
  </ItemGroup>

  
    <ItemGroup>
      <MauiXaml Update="Controls\WebRtcLocalView.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\AboutPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\BlankPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\ErrorPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\EulaPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\FirstInvitePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\HomePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\LocationRequest.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\LoginPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\LogoutPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\NewPage1.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\Page1.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\UpgradePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\ValidatePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\WaitingForProvidersPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\WebRtcPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
      <MauiXaml Update="Views\WebRtcTest.xaml">
        <Generator>MSBuild:Compile</Generator>
      </MauiXaml>
    </ItemGroup>

    <ItemGroup>
      <None Update="Controls\WebRtcLocalView.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\AboutPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\BlankPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\ErrorPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\EulaPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\FirstInvitePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\HomePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\LocationRequest.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\LoginPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\LogoutPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\NewPage1.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\Page1.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\UpgradePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\ValidatePage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\WaitingForProvidersPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\WebRtcPage.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
      <None Update="Views\WebRtcTest.xaml">
        <Generator>MSBuild:Compile</Generator>
      </None>
    </ItemGroup>

    <ItemGroup Condition="'$(TargetFramework)' == 'net8.0-android'">
      <PackageReference Include="Pushy.SDK.MAUI.Android">
        <Version>1.0.93</Version>
      </PackageReference>
      <PackageReference Include="Xamarin.AndroidX.Lifecycle.Runtime">
        <Version>2.7.0.1</Version>
      </PackageReference>
      <PackageReference Include="Xamarin.AndroidX.Work.Runtime">
        <Version>2.9.0.1</Version>
      </PackageReference>
      <PackageReference Include="Xamarin.Firebase.Messaging">
        <Version>123.4.1</Version>
      </PackageReference>
      <PackageReference Include="Xamarin.GooglePlayServices.Base">
        <Version>118.3.0</Version>
      </PackageReference>
    </ItemGroup>

    <ItemGroup>
      <Folder Include="Platforms\Android\Resources\drawable-xhdpi\" />
    </ItemGroup>
</Project>

and my extension .csproj

<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFrameworks>net8.0-ios</TargetFrameworks>
        <OutputType>Library</OutputType>
        <ApplicationId>com.myfriendlyeyes.mfe.mfeserviceextension</ApplicationId>
        <ApplicationDisplayVersion>1.0</ApplicationDisplayVersion>
        <ApplicationVersion>1</ApplicationVersion>
      <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
      <ImplicitUsings>enable</ImplicitUsings>
      <SupportedOSPlatformVersion>15.4</SupportedOSPlatformVersion>
    </PropertyGroup>
  <PropertyGroup>
    <IsAppExtension>true</IsAppExtension>
    <IsWatchExtension>false</IsWatchExtension>
    <BaseOutputPath>bin\</BaseOutputPath>
  </PropertyGroup>
  <PropertyGroup>
    <Registrar>static</Registrar>
  </PropertyGroup>
</Project>

[VladislavAntonyuk]

Update XCode version. It should match the latest version .NET MAUI supports.

[devperson]

Usually, this error happens on Windows platform(building on Widnows version of VS). This doesn't happen on VS Code on Mac

[ivmirx]

I was able to include a native extension (built via Xcode tools) using this example, but they're an absolute pain to sign. Still searching for the correct formula, resigning the whole IPA didn't work.

[nf-g]

Were you able to finally make it work? If yes, can you share your ShareExtension project?

[ivmirx]

@nf-g not yet, left it for tinker around later. Here're my attempts to adjust MSBuild in iOS.csproj (I set all signing in .xcodeproj):

<PropertyGroup>
  <StickersCodeSignIdentity>Apple Development</StickersCodeSignIdentity>
  <StickersCodeSignIdentity Condition="'$(Configuration)' == 'Release'">Apple Distribution</StickersCodeSignIdentity>
</PropertyGroup>
<PropertyGroup>
    <SdkName Condition="'$(RuntimeIdentifier)' == 'ios-arm64'">iphoneos</SdkName>
    <SdkName Condition="'$(RuntimeIdentifier)' == 'iossimulator-x64'">iphonesimulator</SdkName>
</PropertyGroup>
<Target Name="PrintInfo" BeforeTargets="PrepareForBuild;PrepareForPublish">
    <Message Text=">>> Platform: $(Platform), SdkName: $(SdkName), Configuration: $(Configuration), UseInterpreter: $(UseInterpreter)" Importance="High" />
</Target>
<Target Name="BuildStickerExtension" BeforeTargets="PrepareForBuild;PrepareForPublish">
  <Message Text=">>> Building sticker extension Xcode project ($(Configuration))" Importance="High" />
  <Exec Command='xcodebuild -project &quot;$(MSBuildProjectDirectory)/Main/Native/StickerPack/StickerPack.xcodeproj&quot; \
    -scheme StickerPackExtension \
    -configuration $(Configuration) \
    -sdk $(SdkName) \
    -derivedDataPath &quot;$(MSBuildProjectDirectory)/Main/Native/StickerPack/DerivedData&quot;' />
</Target>
<Target Name="CleanStickerExtension" AfterTargets="Clean">
  <Message Text=">>> Cleaning sticker extension Xcode project" Importance="High" />
  <Exec Command="xcodebuild clean -project &quot;$(MSBuildProjectDirectory)/Main/Native/StickerPack/StickerPack.xcodeproj&quot; -configuration $(Configuration) -target StickerPackExtension -sdk $(SdkName)" />
</Target>
<Target Name="ResignStickerExtension" AfterTargets="_CodesignAppBundle">
  <PropertyGroup>
    <StickerAppeXPath>$(MSBuildProjectDirectory)/bin/$(Configuration)/net9.0-ios/ios-arm64/ios.app/PlugIns/StickerPackExtension.appex</StickerAppeXPath>
    <EntitlementsFile>$(MSBuildProjectDirectory)/Main/Native/StickerPack/StickerPackExtension.entitlements</EntitlementsFile>
  </PropertyGroup>
  <Message Text=">>> Re-signing StickerPackExtension binary and bundle (final)" Importance="High" />
  <Exec Command='plutil -convert xml1 "$(EntitlementsFile)"' />
  <Exec Command='plutil -lint "$(EntitlementsFile)"' />
  <Exec Command='codesign -!-force -!-sign "$(StickersCodeSignIdentity)" -!-entitlements "$(EntitlementsFile)" "$(StickerAppeXPath)/StickerPackExtension"' />
</Target>
<ItemGroup>
  <ProjectReference Include="..\Core\Core.csproj" />
  <AdditionalAppExtensions Include="./Main/Native/StickerPack">
    <Name>StickerPackExtension</Name>
    <BuildOutput Condition="'$(ComputedPlatform)' == 'iPhone'">DerivedData/Build/Products/$(Configuration)-iphoneos</BuildOutput>
    <BuildOutput Condition="'$(ComputedPlatform)' == 'iPhoneSimulator'">DerivedData/Build/Products/$(Configuration)-iphonesimulator</BuildOutput>
  </AdditionalAppExtensions>
</ItemGroup>

[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.

[MitchBomcanhao]

.net9 is almost over - when .net10 is out maui support for .net9 will dry up very quickly. they claim 6 months extra, but in reality very little happens whenever the next version is out.

[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