We've been trying to deal with this issue for weeks now. We suspect might be something related with sendbird and we are also in contact with sendBird team but getting nowhere. Sometimes, when starting our app after the login our app just freezes and becomes unresponsive, sometimes even causing a crash. We are having some trouble finding out what is causing it. Today I was able to replicate the issue using an iPhone 7 simulator with ios 15.4 and I was able to debug a little. The debug view hierarchy is also unresponsive and suggests to try and use time profile, which I did. I also use Thread safe But I couldnt actual make much sense of the results. So I was hoping you could help me with it. Hopefully, you can provide some light on this issue. Thanks

When I try to use instruments most of the time I can't identify the threads. I'm assuming these are "internal" threads? One of the threads was causing the CPU to go up to 100% usage. I didn't change anything in the code, how do I identify what is causing these issues.

When I set breakpoints I keep getting Invalid expression for variables that are clearly set and there "in context". Furthermore lets say I have an object X with a property y I'm able to check object X with all of its properties but If i try to watch for X.y I get "Invalid expression" this doesnt make much sense... I even try to add watch directly from X.y in the watch section but then I got this error Details Failed to set watch point Domain: IDEDebugSessionErrorDomain Code: 2 Failure Reason: error: Watchpoint creation failed (addr=0x282efac68, size=8, variable expression='self.controller'). error: sending gdb watchpoint packet failed User Info: {   DVTRadarComponentKey = 855031; } -- System Information macOS Version 12.1 (Build 21C52) Xcode 13.2.1 (19586) (Build 13C100) Timestamp: 2022-03-02T15:45:33Z I've looked into my build options for the project and optimizations are set to None on Debug... Am I missing something?

Good afternoon, It's been sometime since we've added metrickit to our app but the latest versions have not shown in the metrics, all I can see in organizer for our current version are the 3 types of reports (crashes, disk writes and energy). All the metrics (launch time, memory, scrolling, so on...) after 7 versions ago are still missing. What are we doing wrong?

I'm having several crashes that I've been unable to replicate <compiler-generated> - Line 4370483668 specialized Dictionary.subscript.getter + 4370483668 I suspect this might be related with dictionaries not being accessed in a safe way due the use of several threads(?) The most common crash happens in this line guard self.service?.handlers[id] != nil else { any ideas or suggestions? Do you think a .async(flags: .barrier) could solve the issue? because I'm unable to replicate it. this code is called via observers over a Realm database so the Unit test i've created does several threads that try to write the database at same time. UNIT TEST PSEUDO CODE func testDictionaryAccess() { &#9; for i in 0...10 &#9; { &#9;&#9; dispatchGroup.enter() &#9;&#9; DispatchQueue(label: "createActivityThreads").async { &#9;&#9;&#9; create records on database() &#9;&#9;&#9; dispatchGroup.leave() &#9;&#9; } &#9; } &#9; dispatchGroup.wait() &#9; XCTAssertTrue(true) } each loop iteration takes about 20 seconds to run so theres plenty of time for them to start having conflicts between each other