林紫一

> Hi @linziyiwj, it seems like your issue is related to #6392. Could you try updating your SDK version to 8.14.0 and see if you'll still encounter the issue? Hi...

> Thanks, We will upgrade the version and then look at the data

> Thanks for reaching out, @linziyiwj. Could you provide the detailed steps in reproducing the issue as well as the complete stack trace? @rizafran Unfortunately I have not been able...

> Looks like the lock is necessary for this initialization logic, but we could potentially speed it up by using `os_unfair_lock`. @morganchen12 Sorry, I don't quite understand it. Can you...

> @linziyiwj I believe @morganchen12 was talking about a possible change in our internal implementation. @paulb777 Please ask when will the version be updated to deal with this problem，Hope to...

> Hi @linziyiwj, could you please provide all stack traces, including all other threads? It would help us to know where our internal worker thread is blocked. Thanks. @tsunghung Unfortunately...

> @linziyiwj Just want to be sure, it's not a dead lock, right? It's just that the main thread gets blocked for 1 second, right? Please correct me if I...

> same problem.have you resolved it? @wwc625 No, the official didn't reply, have you solved it？

> We have the same problem! > > ``` > App Hang: The app was terminated while unresponsive > > 0 libsystem_kernel.dylib ___ulock_wait > 1 libsystem_platform.dylib __os_unfair_lock_lock_slow > 2 libobjc.A.dylib...

> Hello @pmanuelli The upgrade content of the official sdk does not mention the relevant optimization. Have you made any improvement after the upgrade