"UI unresponsiveness" warning on @… | Apple Developer Forums

Developer Forums

I'm seeing a runtime warning in Xcode 14 Beta 5 that says "This method should not be called on the main thread as it may lead to UI unresponsiveness."

This is happening on the @main entry point of my app. See below:

The warning shown gives me no insight into what's actually going wrong. I think it may be due to some Core Location code that runs when the app first opens, but is there a way for me to get some more insight into what's causing this?

Or is this possibly an Xcode 14/iOS 16 bug, and this is not an issue to worry about? I'm not getting any warnings on Xcode 13/iOS 15.

68k

Posted by

r.token

Reply

">

—
Vashbhi
Sama here, Xcode 14.2.

—
cagli

Apple Recommended

The purple warning is calling attention to a runtime issue that may impact the performance of your app. In general, you should resolve these issues when they are in your code, by moving the code off the main thread. When you receive one of these runtime performance issues, you can expand the backtrace in the Issue Navigator, available through the View > Navigators > Issues menu, to see where the issue is located.

If you find the issue is pointing at an Apple framework, please use Feedback Assistant to open a bug report to let us know, and include the complete backtrace shown in the issue navigator. You can post the FB numbers to this thread for visibility. Further, if you can't identify where the issue is coming from, as the backtrace points to your main function, please also let us know, including the provided backtrace.

If you find the runtime issue is resulting from an Apple API call used in a sub-optimal way within a third-party library that your app uses, please open a bug report with the library vendor.

Posted by

edford

I've replied back below. please note

—
Kim Ju Young
I updated to OS 13.0.1 and Xcode to 14.1. My app now reports this same error "This method can cause UI unresponsiveness if invoked on the main thread. Instead, consider waiting for the -locationManagerDidChangeAuthorization: callback and checking authorizationStatus first." and traces it to this bit of code:

if CLLocationManager.locationServicesEnabled(). So, I implemented the suggested fix, but the complier says that authorizationStatus was deprecated in iOS 14.0

—
Herksrule
this is not helpful at all

—
quinton-ashley

Replies

Same here after update to Xcode 14.0 today

Captura de Pantalla 2022-09-13 a las 23.22.14.png

Posted by

oscarabilleira

Same issue is there any Fix for this?

Posted by

AlphaBo

In my case, I spotted the error on line 2, in viewDidLoad (but same issue if put elsewhere like viewDidAppear):

1.         guard let url = URL(string: "https://google.com") else {return}
2.         myWebView.load(URLRequest(url: url))

Problem: load MUST run on main thread (dispatching to another queue causes run time crash) WKWebView.load(_:) must be used from main thread only

Dispatching to main.async, logically does not change anything. That occurs in Xcode 14 / iOS 16 simulator. Also occurs with Xcode 13.4.1 / iOS 16. No such error message in Xcode 13.4.1 / iOS 15.5 So that's a new warning in iOS 16. I read there is a solution by prelaoding, but did not test yet. https://coderwall.com/p/trjkcg/preloading-uiwebview-or-wkwebview-in-swift

It is just a warning, if it works OK on real app, I think we should just ignore it.

Posted by

Claude31

Same for me with WKWebView

Posted by

wmadao11

Same issue. What is going on with Xcode?

Posted by

igork

Same issue...Xcode 14.0 - on code that has been working for years. No clue how to solve it.

—
RichApple

Same issue. How to fix it ?

Posted by

bravos567

I am seeing the problem with the simulator..but not when running on a real iPad..

Simulator Version 14.0 (986.3) SimulatorKit 624 CoreSimulator 857.7

Posted by

RichApple

I have a SwiftUI App that displays an animated gif from a weather api, using UIViewRepresentable and WKWebView. I also get this warning. I'm using the Xcode RC. I've checked the preloading solution, but not sure how I can apply this to an App with SwiftUI lifecycle.

Posted by

Hanss

Same purple security warning in Xcode 14 (latest release) here. "This method should not be called on the main thread as it may lead to UI unresponsiveness."

In my case I've traced it to a WKWebView -> loadRequest:, i.e. called from my main ViewController's -> viewDidLoad:

i.e. I load a web view at app startup, as after launch/splash screen it's the first view user will see. I'm careful about accounting for network issues and will timeout (or not even try loading), display an alternative screen, etc. if there are network issues.

I'm going to assume someone on the Xcode team chose to add this warning in the event a developer doesn't account for slow loading or not loading at all an initial wkwebview when the app first launches?

Any other theories? Is it safe to ignore the warning?

Posted by

joro1

same issue here

Posted by

Garage POS

In my case, the app works fine (even with this warnings), but image are loaded but a bit slow than before, just the other places where this warning is shown :(.

Posted by

oscarabilleira

purple warning:

This method can cause UI unresponsiveness if invoked on the main thread. Instead, consider waiting for the -locationManagerDidChangeAuthorization: callback and checking authorizationStatus first.

code:

if(CLLocationManager.locationServicesEnabled()) { locationManager.requestLocation() }

however!

did not happen until xcode 14 upgrade,

i now have auto update off, Murphy's law got me :0)

Posted by

dallas0101

I'm seeing this same warning in a UIKit app, but not with similar code in a SwiftUI app...

—
dmalicke

I want to resolve purple warning. I use WkWebView. Anyone have a solution?

purple warning: This method should not be called on the main thread as it may lead to UI unresponsiveness.

Posted by

Yuta0317

same issue

Posted by

NineWindy

Same here! Happened after upgrading iOS and Xcode.

"This method can cause UI unresponsiveness if invoked on the main thread. Instead, consider waiting for the -locationManagerDidChangeAuthorization: callback and checking authorizationStatus first."

Posted by

tunahus