When i publish the iOS app to AppStore it works only in the TestFlight mode. When I submit it to review we get notification about:

"Missing privacy manifest - Your app includes “Frameworks/FBLPromises.framework/FBLPromises”, which includes FBLPromises, an SDK that was identified in the documentation as a commonly used third-party SDK. "

At the same time I am getting the ame error for 6-7 Firebase packages.

It has something to do withdSYM? Before publishing there is a warning about lack of dSYM files.

"Upload Symbols Failed
The archive did not include a dSYM for the FBLPromises.framework with the UUIDs. Ensure that the archive's dSYM folder includes a DWARF file for FBLPromises.framework with the expected UUIDs."

I found some solution about adding configs to csproj but it didn't help at all.

<DebugType>full</DebugType>
<DebugSymbols>true</DebugSymbols>
<DSymUtilEnabled>true</DSymUtilEnabled>
<Optimize>true</Optimize>

Have anyone faced the same problem.

When i publish the iOS app to AppStore it works only in the TestFlight mode. When I submit it to review we get notification about:

"Missing privacy manifest - Your app includes “Frameworks/FBLPromises.framework/FBLPromises”, which includes FBLPromises, an SDK that was identified in the documentation as a commonly used third-party SDK. "

At the same time I am getting the ame error for 6-7 Firebase packages.

It has something to do withdSYM? Before publishing there is a warning about lack of dSYM files.

"Upload Symbols Failed
The archive did not include a dSYM for the FBLPromises.framework with the UUIDs. Ensure that the archive's dSYM folder includes a DWARF file for FBLPromises.framework with the expected UUIDs."

I found some solution about adding configs to csproj but it didn't help at all.

<DebugType>full</DebugType>
<DebugSymbols>true</DebugSymbols>
<DSymUtilEnabled>true</DSymUtilEnabled>
<Optimize>true</Optimize>

Have anyone faced the same problem.

• c#
• ios
• firebase
• maui
• app-store

• Try setting Mono interpreter <PropertyGroup Condition="$(TargetFramework.Contains('-ios')) and '$(Configuration)' == 'Release'"> <UseInterpreter>true</UseInterpreter> </PropertyGroup> – WenyanZhang Commented Mar 11 at 2:04
• What's the linker behavior you set? Is it link all assemblies? By the way, there is the UUID in your post, you could edit to hide it to protect your information. – WenyanZhang Commented Mar 11 at 2:06

2 Answers 2

The two messages are different and not the same.

As of February 2025 ios has made privacy manifests a requirement for 3rd party sdks.

Read more about Missing privacy statement requirment here:

https://developer.apple/support/third-party-SDK-requirements/

To solve this, you will need to either:

1. update your 3rd party sdk package to a later version that does include their privacy statement

   OR

2. if you want to keep your current version of the 3rd party sdk, you will have to manually find their privacy manifest, and then include it into your source code.

Such manifests are in a file called PrivacyInfo.xcprivacy

Visual studio let's you include files in your 3rd party packages by adding an ItemGroup to your project file. For instance, if I downloaded the privacy manifest from AppAuth and put it in my project as Platforms\iOS\PrivacyManifests\AppAuth.xcprivacy, then I would create this in my project file to include it into the 3rd party sdk like this:

    <ItemGroup Condition="'$(TargetFramework)' == 'net8.0-ios'">
        <BundleResource Include="Platforms\iOS\PrivacyManifests\AppAuth.xcprivacy">
            <LogicalName>Frameworks/AppAuth.framework/PrivacyInfo.xcprivacy</LogicalName>
        </BundleResource>
    </ItemGroup> 

The dSym symbols not being in the package is merely a warning. FYI dSyms are debug symbols files.

Hi