-
Notifications
You must be signed in to change notification settings - Fork 1
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
Apptimize causes a lockup on older iPad models #7
Comments
Hello. thanks for reproting the issue. could you provide more information such as what iOS version are you testing on? |
The iPad was on iOS 17.4. I'll update to your latest version and see if the problem still exists. If it does, I'll enable Apptimize verbose mode. |
@ilitvinenko Hi we came back to this problem because it is still not fixed. It looks like when we are asking for feature flag availability at iPad, at some conditions library is having deadlock. Attaching Stack trace and logs. I hope we can fix this problem as soon as possible and update library. Let me know if you need anything else.
|
@IceFloe did you capture the logs right before the deadlock?
regarding the screenshot of the stack trace. did it happen on the main thread? |
Deadlock is happening on the main thread. I put some logs before and after getting feature flag and it is clearly visible that during getting feature flag we are having it. In version 3.5.20 we don’t see this problem. All versions after it has it. |
@IceFloe could you provide statck trace for all other apptimize threads? |
@IceFloe should be fixed in 3.6.3 |
We had customers on older iPad model, such as the iPad 6, that our app was getting stuck on the launch screen. After much investigation, we discovered that we had recently upgraded the library from 3.5.15 to 3.5.21. We found an iPad and could reliably repo the issue. If we downgraded to 3.5.20 or older, our app worked and when we upgraded to 3.5.21 or newer, our app would hang on waiting for Apptimize to return from getting a feature flag value.
The text was updated successfully, but these errors were encountered: