Hello all!
The official Qt reference saying - XCode 11 iOS 13 SDK. I there any way to deploy on iOS 14 device? I am using Qt 5.15. If not - when in Qt going to be iOS 14 support? Or all of it will be in Qt 6.0?
Gyp: No Xcode or CLT version detected! Reference: Installation notes for macOS Catalina (v10.15) Check MacOS version. Run swvers in terminal to check your MacOS version. They said a minor rev shouldn't hurt anything, but I was getting some deployment errors intermittently and so switched back to Xcode 11.4 and its working fine now. So, I'm using the following now with success. MacOS 10.15.4 Catalina Xcode 11.4 Visual Studio for Mac 8.5.5.
Updated.
I've just tried to update XCode 11.5 on Mojave and got this message
It's mean you can't be using Mojave anymore. You might be using previously installed, but not if you installing or reseting your apple device. Apple insisting on updates, even you trying to ignore updates:
If you will update and install XCode from AppStore there will be installed XCode 12 that is not supported by QT yet. You will get an error of something like 'I don't see iOS SDK'. Install XCode manualy by downloading it through Apple Developer login. In few going to post system configuration that is OK for Qt developing for mobile.
Is node-gyp (Node.js native addon build tool) failing during yarn install or npm install? If your macOS got upgraded to Catalina (10.15) recently, then you will find the fix right here.

node-gyp uses XCode Command Line Tools for macOS.
Both upgrading to macOS Catalina and running a Software Update in Catalina may cause normal node-gyp installations to fail. This might manifest as the following error during npm install:
gyp: No Xcode or CLT version detected!
Reference: Installation notes for macOS Catalina (v10.15)
Run sw_vers in terminal to check your MacOS version. Actually, if ProductVersion is less then 10.15, then fix of this post may not be applicable.
Reinstall the XCode Command Line Tools.


If the below acid test passes, we are good to go.

Finally, we'll run the initial npm install that failed for us.