You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Firebase version 10.25.0 on an iPhone 13 Pro running iOS 17.6.1, a crash occurs exclusively with TestFlight builds. The app successfully configures Firebase on the first launch. However, if the app is sent to the background for 15 minutes or longer and then reopened, it crashes when transitioning back to the active state.
Reproducing the issue
Using Firebase version 10.25.0 on an iPhone 13 Pro running iOS 17.6.1, a crash occurs exclusively with TestFlight builds. The app successfully configures Firebase on the first launch. However, if the app is sent to the background for 15 minutes or longer and then reopened, it crashes when transitioning back to the active state.
Description
Using Firebase version 10.25.0 on an iPhone 13 Pro running iOS 17.6.1, a crash occurs exclusively with TestFlight builds. The app successfully configures Firebase on the first launch. However, if the app is sent to the background for 15 minutes or longer and then reopened, it crashes when transitioning back to the active state.
Reproducing the issue
Using Firebase version 10.25.0 on an iPhone 13 Pro running iOS 17.6.1, a crash occurs exclusively with TestFlight builds. The app successfully configures Firebase on the first launch. However, if the app is sent to the background for 15 minutes or longer and then reopened, it crashes when transitioning back to the active state.
Firebase SDK Version
10.25.0
Xcode Version
15.4 (15F31D)
Installation Method
CocoaPods
Firebase Product(s)
Authentication, Crashlytics, Database, Messaging
Targeted Platforms
iOS
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
snippetThe text was updated successfully, but these errors were encountered: