Running Xcode 13 I see the following log when launching my iOS app in the Simulator:
Writing analzed variants.
Note that this is, hopefully, a misspelling of the log:
Writing analyzed variants.
What is causing this log noise? Is something in my code triggering it?
How can I hide this "Writing analzed variants." Xcode log?
1. The device logs Xcode uses system logging to log its messages to the console. If you open the Console app, find your macOS device in the Devices list and look at the messages.
You can view these logs using the Devices and Simulators window in Xcode, described in About Devices and Simulators window. If a customer reports a crash, they can transfer the crash report to either a Mac or Windows computer.
Alternatively, you can actually start Xcode from the terminal (by typing /Applications/Xcode-beta.app/Contents/MacOS/Xcode in the terminal window). If you do that, all the logs will be written to the terminal console. 2. The Diagnostic Reports
The Diagnostic Reports These (also accessible via the Console app) will contain crashes that Xcode itself doesn't log (there are some cases where Xcode will die silently, but the Diagnostics Reports may still contain the error along with the callstack and other useful info).
For me this issue warning coming because of keyboard was not working in my simulator, I have made some mistakes in my code in SceneDelegate
for window
initialisation, but once I have removed that line of code this message not showing in log/consol
these 2 lines I have removed from SceneDelegate, these two lines created this issue for me
let windowScene = UIWindowScene(session: session, connectionOptions: connectionOptions)
self.window = UIWindow(windowScene: windowScene)
So I have removed these from SceneDelegate
for SceneDelegate
Code and the keybaord issue see this
According to Quinn “The Eskimo!” at Apple Developer Technical Support, this message is Xcode log noise and can be ignored.
An Apple bug report should be filed to help flag and silence the log.
It’s important to keep an eye on log messages and fix any obvious problems they call out. However, if you see a log message that’s not obviously your fault, it could just be log noise.
There are two criteria you should apply here:
- Is the log message associated with a specific failure? That is, when you see the log message, do you also see other problems?
- Is the log message written in terms you understand? That is, does it reference APIs or data that you’re using?
If the answer to both of these questions is “No”, it’s reasonable to conclude that the log message is just noise and you can ignore it. If you find it to be particularly irksome, file a bug report requesting that it be silenced.
This was annoying me because the log lines seemed to be causing a delay, which made my UI feel sluggish. I tried a number of ways to speed up my segue code before seeing the lines in the log and thinking they might be taking time.
I was using a custom keyboard which didn't have an equivalent in iOS, and I'd left "Use the Same Keyboard Language as macOS" selected in the Input > Keyboard menu. Turning that off got rid of the logging, and fixed the associated slowdown.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With