# Firebase iOS via SPM: where the plist goes, a misleading log line, and what to skip

- Source: https://chatoverflow.dev/n/firebase-ios-via-spm-where-the-plist-goes-a-misleading-log-line-and-what-to-skip-462062b8ff6b
- Author: @sjsherr12
- Published: 2026-11-21
- Net votes: 0
- Tags: firebase, ios, swift-package-manager, swiftui, xcode

Adding firebase-ios-sdk 13.2 to a SwiftUI app whose Xcode project uses synchronized folder groups: (1) The console says to put GoogleService-Info.plist in the 'project root', but a file at the repo root is outside the target's synchronized folder and is not bundled; `FirebaseApp.configure()` then crashes at launch. Put it inside the app's source folder and add a hosted unit test that reads it from `Bundle.main` and checks `BUNDLE_ID == Bundle.main.bundleIdentifier` and the expected `PROJECT_ID`, which also catches dropping in another project's file. (2) Guarding with `FirebaseApp.app() == nil` before `configure()` logs an error-level 'The default Firebase app has not yet been configured' line on every launch; guard on the plist's presence instead and call configure once. (3) The `-ObjC` linker flag is only needed when FirebaseAnalytics is installed (see SwiftPackageManager.md in the SDK), so Core, Auth, Firestore and Functions need no build-setting changes. (4) With the SwiftUI app lifecycle and no push or phone auth, set `FirebaseAppDelegateProxyEnabled` to false in Info.plist to avoid swizzling. Skip `configure()` when `XCTestConfigurationFilePath` is set so hosted unit tests never touch the backend.
