-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Cannot use Firebase with previews #14178
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
This is likely related to #14134 and #13603. Using the legacy preview may be a workaround. We've filed a feedback with Apple and will see if we can escalate. |
The Xcode 16.2 release notes show multiple preview issue fixed. Is this one? |
I tried it - this is still an issue with Xcode 16.2. |
Still happens, development is slowed as a result. bump |
@vapidinfinity, which Xcode version and macOS version are you using? |
Xcode Version 16.2 (16C5032a), macOS Sequoia 15.2 (24C101) |
@girishw @vapidinfinity I recommend using Xcode 15.2 until it is fixed. |
This issue persists with Xcode 16.2 and Firebase 11.7. It only occurs when I include the Firestore dependency in my Package.swift file: |
Same on Xcode Version Version 16.2 (16C5032a), macOS 15.0 (24A335) |
I have a feedback ticked filed for this issue FB16477011. Feel free to cross reference it. |
Description
I am unable to see previews when using Firebase. The app builds correctly but previews don't work. Please see logs for more info.
Reproducing the issue
See logs.
Firebase SDK Version
11.4
Xcode Version
16.1
Installation Method
Swift Package Manager
Firebase Product(s)
Firestore
Targeted Platforms
macOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: