Would it be possible to add a define that lets you use a “real” assert so that if you run into an jassertfalse, then the app would “crash”.
I created an example here:
In the example above you would still break at the line where jassertfalse is if running in a debugger.
One option that does not require any changes in juce is to redefine JUCE_LOG_CURRENT_ASSERTION, but then one needs to include <cassert>in different places. I think it would be best if the file, that defines what jassertfalse does, also includes the necessary headers.