Closed 0x61726b closed 4 years ago
Any news @mikehaney24 about the possible timelines for a 6.15.0 update? Thanks :)
update is still slated for this week, but today is a holiday in the US, so not today
Thanks for the update! Hope you have a nice holiday :)
We seem to be facing the same issue. Is there any news on when the updated plugin will be available? In the meantime I will try downgrading Unity.
We still expect a new Firebase Unity SDK this week, but keep in mind: this may not completely fix your issue. The fundamental problem is that Unity has a hanging bug when a library calls SCNetworkReachabilitySetDispatchQueue() during +load time on iOS. What we've done is move that call to a later time in one of our libraries. Other libraries may still do this and you'll encounter it again. This issue needs to be addressed by Unity.
On Wed, May 27, 2020 at 1:24 AM stuhowarth notifications@github.com wrote:
We seem to be facing the same issue. Is there any news on when the updated plugin will be available? In the meantime I will try downgrading Unity.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/firebase/firebase-ios-sdk/issues/5463#issuecomment-634508946, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIILARR2CMF55UFNPFPXNTRTTE4FANCNFSM4MRONEEQ .
I found a solution, you just need to update your pod.
firebase authorization, database, core Version 6.25
I searched high and low and finally ended up here. Hoping that fix works!
Has anyone made a Unity bug report about this issue so we can surface it to Unity employees?
[REQUIRED] Step 1: Describe your environment
CocoaPods (importing .unitypackage)
[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
When updating the app from a previous version, app does not start and gets killed by watchdog after some time. Subsequent launches are fine. Only the first launch after an update crashes. Also installing from scratch does not have any issue. I'm only posting this here because I see GDTCORReachability on the crash log.
We dont have background entitlements.
Also doesnt appear on Crashlytics.
The UnityFramework addresses are symbolicated by me using:
atos -arch arm64 -o UnityFramework.framework.dSYM/Contents/Resources/DWARF/UnityFramework -l 0x105000000 0x000000010522fee4
etc.
Please tell me if I'm symbolicating these incorrectly.
Other addesses are symbolicated by Xcode (by dragging the crash file to Xcode)
Stack trace:
Podfile.lock: