We are finding that our calls in our iOS app to
Twitter.sharedInstance().APIClient.sendTwitterRequest
are locking up our UI because of delays in the response.
However, if we put this call in the background thread, we get:
TwitterKit must be used only from the main thread. Use from background threads will lead to unexpected behavior and crashes. Set a symbolic breakpoint in +[TWTRMultiThreadUtil warnForBackgroundThreadUsage] to debug this.
Is there a way to avoid UI lockups due to the TwitterKit being required to be in the main thread?
