Response from FTDI regarding signed drivers
Apple are moving from what are called Kernel Extentions (.kexts) to what are called Driver Extensions (.dexts) for the implementation of drivers starting in macOS Catalina (10.15). Currently .kexts are still supported in macOS Catalina, however after the beta release they issued an update which stopped our driver from loading. This update required our driver (FTDIUSBSerialDriver.kext) to be re-signed and notarized, we completed this process with an updated Apple Developer ID (as they lapse every two years). Unfortunately when Apple issued our new Developer ID to re-sign and notarize the driver package they did so without the .kext support option enabled (as .kexts are being deprecated it is no longer automatically included). This is why there is a code signature issue with our driver, currently we are waiting on Apple issuing us with the correct Developer ID to be able to sign .kexts for macOS Catalina.
As such our current VCP driver available on the website has a signature issue and wont load. However if the device you are using implements a default FTDI VID/PID combination it should be picked up by the inbuilt AppleUSBFTDI.dext driver and present accordingly in the ‘/dev’ folder on your system in the following form:
/dev/cu.usbserial-xxxxxxxx
/dev/tty.usbserial-xxxxxxxx
UPDATE
Got answer back from FTDI and they provided signed FTDI driver 2.4.4 which works fine now on my iOS catalina 10.15.4 (Will be available soon here: https://www.ftdichip.com/Drivers/VCP.htm)
Note
- It worked only when I had hardware connected via USB while booting up. I had wacom tablet driver installed which prevented FTDI driver to detect FTDItoUSB hardware if I remove it and connect it again.
To solve such issue just run following command in terminal
sudo dmesg | grep -i "usb\|uart"
if you see something like not attached, or used by something else
Just uninstall that driver
/System/Library/Extensions/AppleUSBSerial.kext
and/Library/Extensions/FTDIKext.kext
– Clamshell