Unfortunately there is no other way. I will say that Logic is the only DAW to date where we’ve seen this crash including from developers who auto collect crash logs via analytics which is highly suggestive that Logic may have some part to play in the issue, but it’s too difficult to say how or why that is the case without a developer being able to reproduce the issue.
Customers are notified about major updates via email but it can be difficult to know if customers need to update as they could be using an open source licence or they may have a custom version of JUCE in which they’ve made their own changes. As we don’t have access to their source code we don’t know exactly what version of JUCE they are running or if their products will be impacted by the issue.
We can obviously reach out to companies individually and there are conferences throughout the year where we can catch up with developers in person too. This gives us an opportunity to find out if there is anything we can do to help. However, there are various reasons why it might be difficult to update and some of those reasons may not be directly related to JUCE.