Have you solved this problem?

Thanks for the reply! Just to clarify, the issue occurs while the app is actively being used — it’s not in the when the problem happens. I only mentioned and other system conditions as speculative possibilities, not confirmed behavior.

Thanks for the reply! Just to clarify, the issue occurs while the app is actively being used — it’s not in the when the problem happens. I only mentioned and other system conditions as speculative possibilities, not confirmed behavior.

Thanks for the reply! Just to clarify, the issue occurs while the app is actively being used — it’s not in the when the problem happens. I only mentioned and other system conditions as speculative possibilities, not confirmed behavior.

There’s a word limit for comments—please see my reply below. Thanks!

There’s a word limit for comments—please see my reply below. Thanks!

Also, since you mentioned .internal (8) errors — do you happen to know what typically causes them? We’ve seen a few of those as well, though less frequently. Is it usually an issue with how the code is written or when the configuration is applied (e.g. timing, thread, app state), or is it more often a system-level failure outside the developer’s control? Any hints on how to mitigate or avoid .internal errors would be much appreciated!