Skip to content

fix(spm): Include FirebaseRemoteConfigInternal in RemoteConfig product #16291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ArthurHPorto wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −1
Open

fix(spm): Include FirebaseRemoteConfigInternal in RemoteConfig product #16291

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions FirebaseCore/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@
- [changed] Firebase now requires Swift tools version 6.1 for the Swift Package.
The package will no longer resolve in Xcode versions older than 16.3. Note that
the minimum officially supported version for the SDK remains Xcode 26.2+.
- [fixed] Include `FirebaseRemoteConfigInternal` in the `FirebaseRemoteConfig`
SwiftPM product to fix builds that fail to resolve the internal clang module
when Swift explicit modules are enabled (e.g. Xcode 26+ and Tuist).

# Firebase 12.14.0
- [fixed] Remove extra comma in Package.swift that caused SPM resolution
Expand Down
2 changes: 1 addition & 1 deletion Package.swift
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ let package = Package(
),
.library(
name: "FirebaseRemoteConfig",
targets: ["FirebaseRemoteConfig"]
targets: ["FirebaseRemoteConfig", "FirebaseRemoteConfigInternal"]

@ncooke3 ncooke3 Jun 23, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ArthurHPorto , thanks for the PR! Curious, is Tuist importing FirebaseRemoteConfigInternal explicitly?

We have a similar setup for other libraries like Firestore, so I'm trying to understand the scope of this issue while trying to prevent these internal modules from being publicly accessible.

),
.library(
name: "FirebaseStorage",
Expand Down
Loading