[Release Tooling] Update zip integration instructions for privacy manifest support (#12449)

Author: ncooke3

FirebaseCore/CHANGELOG.md

@@ -11,6 +11,11 @@
 - Fixed validation issues in Xcode 15.3 that affected binary distributions
   including Analytics, Firestore (SwiftPM binary distribution), and the
   Firebase zip distribution. (#12441)
+- [Zip Distribution] The manual integration instructions found in the
+  `Firebase.zip` have been updated for Xcode 15 users. The updated instructions
+  call for embedding SDKs dragged in from the `Firebase.zip`. This will enable
+  Xcode's tooling to detect privacy manifests bundled within the xcframework.
+
 
 # Firebase 10.21.0
 - Firebase now requires at least CocoaPods version 1.12.0 to enable privacy

ReleaseTooling/Template/README.md

@@ -34,17 +34,18 @@ To integrate a Firebase SDK with your app:
    box that appears, make sure the target you want this framework to be added to
    has a checkmark next to it, and that you've selected "Copy items if needed."
 
-   > ⚠ Do not add the Firebase frameworks to the **Embed Frameworks** Xcode build
-   > phase. The Firebase frameworks are not embedded dynamic frameworks, but are
-   > [static frameworks](https://www.raywenderlich.com/65964/create-a-framework-for-ios)
-   > which cannot be embedded into your application's bundle.
+7. If using Xcode 15, embed each framework that was dragged in. Navigate to the
+   target's _General_ settings and find _Frameworks, Libraries, & Embedded
+   Content_. For each framework dragged in from the `Firebase.zip`, select
+   **Embed & Sign**. This step will enable privacy manifests to be picked up by
+   Xcode's tooling.
 
-7. If the SDK has resources, go into the Resources folders, which will be in
+8. If the SDK has resources, go into the Resources folders, which will be in
    the SDK folder. Drag all of those resources into the Project Navigator, just
    like the frameworks, again making sure that the target you want to add these
    resources to has a checkmark next to it, and that you've selected "Copy items
    if needed".
-8. Add the `-ObjC` flag to **Other Linker Settings**:
+9. Add the `-ObjC` flag to **Other Linker Settings**:
 
    a. In your project settings, open the **Settings** panel for your target.
 
@@ -53,21 +54,21 @@ To integrate a Firebase SDK with your app:
 
    c. Double-click the setting, click the '+' button, and add `-ObjC`
 
-9. Drag the `Firebase.h` header in this directory into your project. This will
+10. Drag the `Firebase.h` header in this directory into your project. This will
    allow you to `#import "Firebase.h"` and start using any Firebase SDK that you
    have.
-10. Drag `module.modulemap` into your project and update the
+11. Drag `module.modulemap` into your project and update the
    "User Header Search Paths" in your project's Build Settings to include the
    directory that contains the added module map.
-11. If your app does not include any Swift implementation, you may need to add
+12. If your app does not include any Swift implementation, you may need to add
    a dummy Swift file to the app to prevent Swift system library missing
    symbol linker errors. See
    https://forums.swift.org/t/using-binary-swift-sdks-from-non-swift-apps/55989.
 
    > ⚠ If prompted with the option to create a corresponding bridging header
    > for the new Swift file, select **Don't create**.
 
-12. You're done! Compile your target and start using Firebase.
+13. You're done! Build your target and start using Firebase.
 
 If you want to add another SDK, repeat the steps above with the xcframeworks for
 the new SDK. You only need to add each framework once, so if you've already