Visu

Marking this as closed since the new update should be working. Marking this as FIXED.

@tamv-ika Thanks for sharing the stack trace. Can you share the other threads for this crash? I'm looking at a potential race condition that could happen and it would be...

> @visumickey we were seeing empty values for these calls on the Simulator. > > Let me dig into the exact circumstance more. I thought it was simulator but don't...

> I'm not sure what's the purpose of doing this. I think this name is confusing with other classes such as `SessionsStartEvent` and `FirebaseSessions`. I also worry about adding [too...

Thanks @tamv-ika for sharing the stack trace. Looking at the [crashed line](https://github.com/firebase/firebase-ios-sdk/blob/master/FirebasePerformance/Sources/Timer/FIRTrace.m#L239), Firebase performance does a copy of an object. It is hard to see a reason why this could...

Based on the [comment](https://github.com/firebase/firebase-ios-sdk/issues/10470#issuecomment-1319515224) above, it looks like the issue is with iOS 16. @mustafauskuplu Do you see a similar pattern as well (where the issue is happening mostly with...

@thanhnhan111093 Based on the stack trace, I have a possible cause of this issue. But I need a couple of information to see if my assumption is right. From the...

Firebase Performance currently eliminates app start traces that are involved in the context of app backgrounding [Reference](https://github.com/firebase/firebase-ios-sdk/blob/master/FirebasePerformance/Sources/AppActivity/FPRAppActivityTracker.m#L219-L222). So, ideally this situation should not occur. The duration of 1032s definitely sounds...

Thanks for reporting the discrepancy here. Really appreciate the references to showcase the gaps. Unfortunately, we have some limitations in allowing space in the custom attribute names. So, at this...

@sp-jordi-vilalta Thanks for the suggestion and the feature request. I like the idea of turning it into a human readable form. I will followup internally to see if there are...