-
Notifications
You must be signed in to change notification settings - Fork 108
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
UI API called from background thread #565
Comments
Not sure why this comes up, the closure is executed further down on the main thread and has never come up as in issue before. It only appears to happen the first time it's called, on subsequent retries there is no delay. May be a false positive introduced in this beta. As the checker has been active since Xcode 9 https://developer.apple.com/documentation/code_diagnostics/main_thread_checker Flagged thread check Dispatch |
yes, same here. forgot to mention that detail. next steps? wait for the final version of Xcode and check again? |
I'm going to file a bug report, would suggest doing the same. |
I had another quick look, it seems that merely obtaining a reference to the presentingViewController flags up the thread checker. Even though the actual action is performed is dispatched in the main thread. However, the delay/pause seems to have gone in later versions of iOS 13 Beta, at least when I tested. |
We are also experiencing this problem. We are using XCode 11 GM2, ios 13.0. |
my app was rejected because of this- may be 13.1.2 specific - may be iPad specific. |
Fix in #576 |
could you please create a new tag (maybe 2.13.1) so this change is included? |
Yes, will release on Monday. Thanks |
Hey,
i am facing an issue with the current Lock version for Swift (v.2.11.0) in the iOS13 Beta 8.
When I hit the login button, the app freezes for a few seconds and the proceeds normally.
In Xcode (Version 11.0 beta 5 (11M382q)) I get the following message in the terminal:
In addition Xcode shows me this:
On iOS 12 i do not experience this issue.
The text was updated successfully, but these errors were encountered: