MATLAB Compiler Dependency Log Changes in R2022b: Missing File Warnings Omitted

Diagnosing Deployment Failures with Updated Compiler Logs

The primary goal is to pinpoint missing data files that cause a standalone MATLAB application to fail at runtime, using only the logs generated during the build and deployment process. In R2021a, the verbose dependency analysis (invoked with mcc -v or the -logfile option) listed every file added via the -a flag and emitted explicit "File not found" warnings when a path could not be resolved. In R2022b, the log format was streamlined: the new mccExcludedFiles.log captures only files that the analyzer decided to exclude, and the main dependency log no longer prints the same missing‑file messages for manually added files.

Additionally, the runtime log created with -R "-logfile,runtime.log" is only written after the MATLAB Runtime successfully initializes, so early failures such as a missing MCR produce no log entry. MATLAB Production Server logs separate compiler‑stage details from runtime events, but the correlation ID that would link a specific mcc build to a server deployment is not propagated by default.

Given these changes, the unresolved behavior is how to reliably trace a missing data file that is added via -a when the compiler logs no longer contain an explicit warning, and how to link that build to the runtime failure when the runtime log may be absent.

Questions:

• What log‑generation flags or configuration options in R2022b can restore the explicit "File not found" warnings for files added with -a?
• How can we correlate a specific mcc build with its MATLAB Production Server deployment when the correlation ID is not automatically included in the logs?
• Is there a recommended workflow to capture early MATLAB Runtime initialization failures that would otherwise leave the runtime log empty?