ios – Manually created privateness manifest seems to be ignored

Word: I do know updating to the most recent packages/SDKs is the proper long run answer however that’s not presently an possibility.

I’ve manually created a privateness manifest file (PrivacyInfo.xcprivacy) however I get precisely the identical points for a similar SDKS from App Retailer Join as when I didn’t have a PrivacyInfo.xcprivacy file.

I consider it’s doubtless one of many following choices

1. Is it not recognizing the privateness manifest.
2. The privateness manifest is incorrectly formatted.
3. Every SDK wants its personal particular person privateness manifest and making a most important one will not work as of 12 Feb 2025. See: https://developer.apple.com/assist/third-party-SDK-requirements/

Course of

I added the privateness manifest in Xcode like so:

1. Chosen my App/App folder within the challenge navigator.
2. Chosen File -> New -> File from the menu.
3. Chosen App Privateness File kind below Sources.
4. Checked my app goal within the Targets record.
5. Clicked Create. This created a PrivacyInfo.xcprivacy file subsequent to the Information.plist file.
6. Copied my manually created PrivacyInfo.xcprivacy content material into this file in VSCode.

After I generate a Privateness Report from the organizer it appears to work.

PrivacyInfo.xcprivacy:

  
    
    NSPrivacyTracking
    
    NSPrivacyTrackingDomains
    
    
    
    NSPrivacyCollectedDataTypes
    
      
      
        NSPrivacyCollectedDataType
        NSPrivacyCollectedDataTypeOtherDiagnosticData
        NSPrivacyCollectedDataTypeLinked
        
        NSPrivacyCollectedDataTypeTracking
        
        NSPrivacyCollectedDataTypePurposes
        
          
          NSPrivacyCollectedDataTypePurposeAnalytics
          
          NSPrivacyCollectedDataTypePurposeAppFunctionality
        
      
      
      
        NSPrivacyCollectedDataType
        NSPrivacyCollectedDataTypeDeviceID
        NSPrivacyCollectedDataTypeLinked
        
        NSPrivacyCollectedDataTypeTracking
        
        NSPrivacyCollectedDataTypePurposes
        
          NSPrivacyCollectedDataTypePurposeAppFunctionality
        
      
      
      
        NSPrivacyCollectedDataType
        NSPrivacyCollectedDataTypeOtherDataTypes
        NSPrivacyCollectedDataTypeLinked
        
        NSPrivacyCollectedDataTypeTracking
        
        NSPrivacyCollectedDataTypePurposes
        
          NSPrivacyCollectedDataTypePurposeAnalytics
          NSPrivacyCollectedDataTypePurposeAppFunctionality
        
      
    
    
    
    NSPrivacyAccessedAPITypes
    
      
      
        NSPrivacyAccessedAPIType
        NSPrivacyAccessedAPICategoryFileTimestamp
        NSPrivacyAccessedAPITypeReasons
        
          C617.1
        
      
      
      
        NSPrivacyAccessedAPIType
        NSPrivacyAccessedAPICategoryUserDefaults
        NSPrivacyAccessedAPITypeReasons
        
          CA92.1
          1C8F.1
          C56D.1
        
      
    
  

E-mail from app retailer:

Please appropriate the next points and add a brand new binary to App
Retailer Join. ITMS-91061: Lacking privateness manifest – Your app
contains “Frameworks/Capacitor.framework/Capacitor”, which incorporates
Capacitor, an SDK that was recognized within the documentation as a
generally used third-party SDK. If a brand new app features a generally used
third-party SDK, or an app replace provides a brand new generally used third-party
SDK, the SDK should embrace a privateness manifest file. Please contact the
supplier of the SDK that features this file to get an up to date SDK
model with a privateness manifest. For extra particulars about this coverage,
together with a listing of SDKs which can be required to incorporate signatures and
manifests, go to:
https://developer.apple.com/assist/third-party-SDK-requirements.

Repeated 10 extra occasions for the opposite SDKs.

Word that is for an Ionic / Capacitor hybrid app however this could not make a distinction.