When running my app after it has been compiled, exportgraphics calls seem to cause the following messages (or similar) to output in the terminal window:
<</ID[<05208558C807F1784140FF8D8426A497><05208558C807F1784140FF8D8426A497>]/Info 1 0 R/Root 40 0 R/Size 41>>
<</ID[<DD2F4FE7DF1F30092B20485DA2514F38><DD2F4FE7DF1F30092B20485DA2514F38>]/Info 1 0 R/Root 26 0 R/Size 27>>
Fixing references in 41 0 R by 40
Fixing references in 42 0 R by 40
Fixing references in 43 0 R by 40
Fixing references in 44 0 R by 40
Fixing references in 45 0 R by 40
Fixing references in 46 0 R by 40
Fixing references in 47 0 R by 40
Fixing references in 48 0 R by 40
Fixing references in 49 0 R by 40
Fixing references in 50 0 R by 40
Fixing references in 51 0 R by 40
Fixing references in 52 0 R by 40
Fixing references in 53 0 R by 40
Fixing references in 54 0 R by 40
Fixing references in 55 0 R by 40
Fixing references in 56 0 R by 40
Fixing references in 57 0 R by 40
Fixing references in 58 0 R by 40
Fixing references in 59 0 R by 40
Fixing references in 60 0 R by 40
Fixing references in 61 0 R by 40
Fixing references in 62 0 R by 40
Fixing references in 63 0 R by 40
Fixing references in 64 0 R by 40
Fixing references in 65 0 R by 40
Fixing references in 66 0 R by 40
These messages are not to my knowledge actually causing any failures within the program, as the plots still export to the pdf and seem the same as when generated outisde of the compiled version. But similar messages post every time exportgraphics is called. If remove the exportgraphics calls from the code and nothing else no messages appear.
These messages do not appear when running the app from App Designer as a .mlapp file.

Some further testing reveals that the above messages do not appear for the first exportgraphics call, but does appear for all subsequent calls with the "fixing references" numbers called out increasing for each call.When running my app after it has been compiled, exportgraphics calls seem to cause the following messages (or similar) to output in the terminal window:
<</ID[<05208558C807F1784140FF8D8426A497><05208558C807F1784140FF8D8426A497>]/Info 1 0 R/Root 40 0 R/Size 41>>
<</ID[<DD2F4FE7DF1F30092B20485DA2514F38><DD2F4FE7DF1F30092B20485DA2514F38>]/Info 1 0 R/Root 26 0 R/Size 27>>
Fixing references in 41 0 R by 40
Fixing references in 42 0 R by 40
Fixing references in 43 0 R by 40
Fixing references in 44 0 R by 40
Fixing references in 45 0 R by 40
Fixing references in 46 0 R by 40
Fixing references in 47 0 R by 40
Fixing references in 48 0 R by 40
Fixing references in 49 0 R by 40
Fixing references in 50 0 R by 40
Fixing references in 51 0 R by 40
Fixing references in 52 0 R by 40
Fixing references in 53 0 R by 40
Fixing references in 54 0 R by 40
Fixing references in 55 0 R by 40
Fixing references in 56 0 R by 40
Fixing references in 57 0 R by 40
Fixing references in 58 0 R by 40
Fixing references in 59 0 R by 40
Fixing references in 60 0 R by 40
Fixing references in 61 0 R by 40
Fixing references in 62 0 R by 40
Fixing references in 63 0 R by 40
Fixing references in 64 0 R by 40
Fixing references in 65 0 R by 40
Fixing references in 66 0 R by 40
These messages are not to my knowledge actually causing any failures within the program, as the plots still export to the pdf and seem the same as when generated outisde of the compiled version. But similar messages post every time exportgraphics is called. If remove the exportgraphics calls from the code and nothing else no messages appear.
These messages do not appear when running the app from App Designer as a .mlapp file.

Some further testing reveals that the above messages do not appear for the first exportgraphics call, but does appear for all subsequent calls with the "fixing references" numbers called out increasing for each call. When running my app after it has been compiled, exportgraphics calls seem to cause the following messages (or similar) to output in the terminal window:
<</ID[<05208558C807F1784140FF8D8426A497><05208558C807F1784140FF8D8426A497>]/Info 1 0 R/Root 40 0 R/Size 41>>
<</ID[<DD2F4FE7DF1F30092B20485DA2514F38><DD2F4FE7DF1F30092B20485DA2514F38>]/Info 1 0 R/Root 26 0 R/Size 27>>
Fixing references in 41 0 R by 40
Fixing references in 42 0 R by 40
Fixing references in 43 0 R by 40
Fixing references in 44 0 R by 40
Fixing references in 45 0 R by 40
Fixing references in 46 0 R by 40
Fixing references in 47 0 R by 40
Fixing references in 48 0 R by 40
Fixing references in 49 0 R by 40
Fixing references in 50 0 R by 40
Fixing references in 51 0 R by 40
Fixing references in 52 0 R by 40
Fixing references in 53 0 R by 40
Fixing references in 54 0 R by 40
Fixing references in 55 0 R by 40
Fixing references in 56 0 R by 40
Fixing references in 57 0 R by 40
Fixing references in 58 0 R by 40
Fixing references in 59 0 R by 40
Fixing references in 60 0 R by 40
Fixing references in 61 0 R by 40
Fixing references in 62 0 R by 40
Fixing references in 63 0 R by 40
Fixing references in 64 0 R by 40
Fixing references in 65 0 R by 40
Fixing references in 66 0 R by 40
These messages are not to my knowledge actually causing any failures within the program, as the plots still export to the pdf and seem the same as when generated outisde of the compiled version. But similar messages post every time exportgraphics is called. If remove the exportgraphics calls from the code and nothing else no messages appear.
These messages do not appear when running the app from App Designer as a .mlapp file.

Some further testing reveals that the above messages do not appear for the first exportgraphics call, but does appear for all subsequent calls with the "fixing references" numbers called out increasing for each call. appdesigner, compiler, graphics MATLAB Answers — New Questions

​