I am using CC 2017, but it has been an issue for multiple versions.

I have a custom plugin that implements INumberConverter on kPageNumberingStylesService Boss for a custom numbering format. This works beautifully until I try to export to PDF. If I print to PDF Distiller it works fine, but when I export to PDF it exports with default numbering style.

This is similar to an old stubborn bug, when exporting book to PDF would not do the numbering correctly. I don't know that it is related, but they both seem to say that the numbering on export is decoupled from the way it is calculated for regular viewing of the PDF.

When a plug-in relies on the embedded Boost framework to support regular expressions, it can cause a crash because of unresolved dependencies.

The issue is that the 16.0 SDK uses Boost 1.65 and the 16.1 SDK uses Boost 1.72

Plug-ins compiled against the 16.0 SDK that use regular expressions will try to access an entry point __ZN5boost16re_detail_10650018get_default_syntaxEh (unmangled: boost::re_detail_106500) when handling regular expressions.

The problem is that this entrypoint's name is dependent on the Boost version (1.65).

This entry point is provided by the (on Mac) embedded framework

/Applications/Adobe InDesign 2021.app/Contents/Frameworks/boost_regex.framework/Versions/A/boost_regex

When a plug-in compiled against SDK 16.0 is used with InDesign 2021 16.1, this entry point does not exist any more.

Instead, the equivalent entry point is now boost::re_detail_107200 and boost::re_detail_106500 does not exist in InDesign 2021 16.1

That causes the plug-in to crash InDesign.

As a result, plug-ins that use boost_regex that are compiled for 2021 16.0 are incompatible with 2021 16.1 and vice-versa.

Function GetEnableGPUPerformance() of interface IGPUPerformancePrefs of GetExecutionContextSession()->QueryWorkspace() returns true in case no GPU or a not supported GPU is installed on your macOS computer.

To reproduce launch InDesign CC 2018 or later with modifier keys command, option, control, and shift pressed and confirm resetting the preferences.

If you now check the setting either with some C++ code, or ExtendScript "app.gpuPerformancePreferences.enableGpuPerformance", in both cases the returned result is true , which is not the expected result.

When you now choose Preferences > GPU Performance the properties are shown deselected and disabled, which is correct. If you now click in "OK", the above function call now correctly returns false. After quitting and restarting InDesign, the preferences still return false, the correct state.

Looks like the preferences are NOT setup on first launch, but use a boolean default value of "true".