fix(ios/mac): move existing privacy manifests into Resources folder for proper detection

[JPGmooder]

Description

This PR fixes an issue that caused the App Store to reject a review due to missing privacy manifests for all Plus plugins, even if privacy manifests already existed (ITMS-91061: Missing privacy manifest). To fix this, the manifests were placed in the plugin's Resources folder so that they would be properly recognized by Apple's privacy manifest verification system.

To resolve this, each plugin’s PrivacyInfo.xcprivacy file is now stored in a dedicated Resources folder at the root of the plugin (e.g., ios/Resources or macos/Resources). The corresponding s.resource_bundles path in each .podspec is updated to reflect this new location. This ensures the privacy manifests are properly detected, removing the “Missing privacy manifest” warning.

Related Issues

• Fix [Bug]: invaild manfiest for ios #3493
• Fix [Bug]: App Store Connect - ITMS-91061: Missing privacy manifest - #3475
• Fix [Request]: MacOS' use of share_plus for auditing has been rejected. Have we listened to the privacy list #3489
• Related [Question]: Apple Missing privacy manifest #3478

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I titled the PR using Conventional Commits.
• I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
• All existing and new tests are passing.
• The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
• No, this is not a breaking change.

[miquelbeltran]

Hello, thanks for looking into this.

I need to remind that each package change should be done in a different PR, as we say in the contribution guidelines, this is required for our release process:

When modifying multiple packages, create a different branch and pull request per package. This facilitates maintenance, the review process, and generating changelogs.

It looks like that the existing manifests were not moved, but new files were created instead. The manifests already exist in the project and should not be duplicated.

Are there any references that say that Manifests need to be located in the Resources folder? My understanding is that it doesn't really matter as long as the podfile and the Swift package manager config point to the correct files.

[miquelbeltran]

Reference from flutter/packages: https://github.com/flutter/packages/blob/6317cd601fa7031a7ad344053e54858bd59845ef/packages/ios_platform_images/ios/ios_platform_images.podspec#L29

Here the path is ios_platform_images/Sources/ios_platform_images/Resources/PrivacyInfo.xcprivacy so what we would need to do is to move e.g. packages/battery_plus/battery_plus/ios/battery_plus/Sources/battery_plus/PrivacyInfo.xcprivacy to packages/battery_plus/battery_plus/ios/battery_plus/Sources/battery_plus/Resources/PrivacyInfo.xcprivacy rather than packages/battery_plus/battery_plus/ios/battery_plus/Resources/PrivacyInfo.xcprivacy.

I am not sure if the Package.swift will need to be modified as well.

[miquelbeltran]

Closing this one as no response

[coogle]

Can we open this again? This is a pretty serious issue as you cannot get past the App Store review process without fixing it and that means any project that is dependent on this package can't do releases.