All CLI VeraCrypt commands return the following text error in the terminal window when running on macOS 14.x:
WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
However, this error appears to be not specific to macOS 14.x. Rather, it appears to be a new check implemented in macOS 14.x. The error appears to indicate an incompatibility between application components. Searching, the error has been reported in multiple applications using Java, Python, TK, and other system components where there is a version compatibility issue between components, relative to the OS dot release , various component versions, and the application itself. TK has been most often blamed in the cases I have read, but not exclusively.
In VeraCrypt, it is occurring when running:
System: macOS 14.7.1 (23H222) on M2 Max MBP
VeraCrypt 1.26.7
This is potentially a nasty problem to deal with, as it appears to be dependent on macOS dot releases, where the system updates some component (e.g., Python) to patch some security vulnerability, and that patch introduces some app version compatibility issue elsewhere. That is, to simply detect this problem requires a lot of regression testing.
The question for which I have not been able to find an answer, is does this warning actually indicate a potential (or actual) security vulnerability? Regardless, for a security-oriented app to be throwing a warning that a potential security coding issue exists is rather disconcerting.
I have also not done testing beyond the above stated VeraCrypt and macOS versions.
However, I have read that upgrading to macOS 15 fixes the problem for many, but not all, apps. But, the consensus seems to be that just because the problem "went away" in macOS 15, doesn't mean not to expect it to reoccur in the future.
I will dig further and post updates as I find additional details regarding this issue.