Opened on 01/02/2018 at 11:04:22 PM
Closed on 01/14/2018 at 04:16:30 AM
#6227 closed change (fixed)
Prevent UI API access on background threads
Reported by: | dzhang | Assignee: | dzhang |
---|---|---|---|
Priority: | Unknown | Milestone: | Adblock-Plus-for-iOS-next |
Module: | Adblock-Plus-for-iOS/macOS | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Platform: | iOS | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description (last modified by dzhang)
Background
There are a few places where explicit UI thread dispatching is required due to a UI API being activated from a background thread or threads by KVO, the notification center or similar causes.
These operations can cause the reporting of a warning or error in Xcode 9 indicating that a UI API was called on a background thread.
See https://developer.apple.com/documentation/code_diagnostics/main_thread_checker
Preventing improper UI API access is meant to improve overall stability.
What to change
Explicitly dispatch UI operations to the UI thread where needed.
Attachments (0)
Change History (5)
Note: See
TracTickets for help on using
tickets.