I noticed that my existing projects no longer work on the simulator after an update to Xcode 11 with iPadOS simulators 13.
In juce_mac_CoreMidi.cpp, line 214, there is an attempt to create a MIDI network session, even though my project (standalone / auv3 JUCE project) explicitly does not need midi as input, nor produces midi as output:
#define JucePlugin_IsSynth 0
#define JucePlugin_WantsMidiInput 0
#define JucePlugin_ProducesMidiOutput 0
#define JucePlugin_IsMidiEffect 0
iOS13 does not allow to create a midi connection on the simulator and therefore the attempt fails.
I’ve seen that in the develop branch, there are commits to prevent the connection from happening, and assert instead:
However, it seems we then simply hit the assert. Is there a way we can prevent the simulator from even trying to get MIDI going? I wonder if the attempt to make a midi connection should be made dependent on whether the app / auv3 wants midi / produces midi at all?