-
Notifications
You must be signed in to change notification settings - Fork 142
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
NTPConnection Crash #58
Comments
Experiencing the exact same issue, hope it'll be fixed soon! |
Same problem here, any solution for this crash |
Any solution for this crash? |
Still seeing this crash since updating to v5.0.0 |
@otymartin, @arm0nic, @clopex, @ramonilho and @andrew-muzmatch - thank you for reporting and our apologies for delay in resolving this issue. We will be looking into this issue shortly. In the mean time using version 4.2.0 might help resolve the issue for the moment. Please do note that if you end up using that version, you will need to update your initialization logic. If you have additional stack traces, it would be very helpful to us if you can provide them. |
@00FA9A |
Today, we have rolled out 5.0.1 that we believe resolves this issue. Please update and do not hesitate to reopen if you encounter it again. |
@00FA9A Thank you! |
@Ariandr I'm not sure why but they haven't been updating the pod. For an immediate fix you can just point your podfile to the commit |
@Ariandr unfortunately, I'm not the owner of the pod at the moment therefore I've been unable to update it. Will try to sort this out asap for you. In the mean time, you should be able to use latest version by adding
to your Cartfile (or use @miketsprague suggestion). |
@00FA9A I see :) |
@Ariandr Podspec should now be updated |
Hello, we're still experiencing crashes on 5.0.1 version
Will be glad to help in investigation |
Thank you for reporting @mandarin6b0, looks like it might be the same issue again. If you have any additional stack traces, it might be useful. How often are you seeing this crash occur? |
I'm also still seeing this in our crash reports (never been able to reproduce it). It's our top crash and affects about .1% of our sessions. I've got two separate stack traces (although not sure how helpful they are). Here's the one that is more frequent:
Here's the less frequent one that Crashlytics seems to think is iOS 12 only:
|
Hello,
|
Hi!
|
I guess this issue should be reopened 😭 |
Same issue here on 5.0.2. |
@00FA9A Hi, could you please consider reopening the issue? Thanks. |
Just to cross reference, I think I have a fix for this: |
@Ariandr and all - sorry for late reply, issue should defiantly be reopened. We had limited time available to deal with it. We are looking into @miketsprague pr as possible solution. |
Thanks to great work by @miketsprague, we hope this issue should be resolved in 5.0.3 that is available now via CocoaPods. Thank you all for patience and apologies for inconvenience this has caused to you and your users |
Any solution? I have same problem |
@RenanDelfanti this issue was resolved #75 which should be in the latest version (5.0.3). We should be able to close this ticket as well. |
@mikesprague-fc I'm using version 5.0.3, but my app crash on second time to get true time. |
Dear all facing the same issue still, Please find the firebase logs as below Stack Trace: Device |
@msanders
Logs:
https://gist.github.com/otymartin/4ffb1be00f09fb4e2673a3824f1a14ab
The text was updated successfully, but these errors were encountered: