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
Generally if we initialise
CrashlyticsInit.sharedInstance.initialiseCrashlytics()
on didFinishLaunchingWithOptions on main thread it takes some amount and blocking main thread
but if we move to background 500-600 ms is saved in app launch time (Atleast in iPhone 12) so is there any issue in moving init to the background thread for initialisation ?
Reproducing the issue
No response
Firebase SDK Version
10.19.0
Xcode Version
16.2
Installation Method
CocoaPods
Firebase Product(s)
Database, All
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered:
Description
Generally if we initialise
CrashlyticsInit.sharedInstance.initialiseCrashlytics()
on didFinishLaunchingWithOptions on main thread it takes some amount and blocking main thread
but if we move to background 500-600 ms is saved in app launch time (Atleast in iPhone 12) so is there any issue in moving init to the background thread for initialisation ?
Reproducing the issue
No response
Firebase SDK Version
10.19.0
Xcode Version
16.2
Installation Method
CocoaPods
Firebase Product(s)
Database, All
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
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: