Hi, I'm having trouble saving user presets in the plugin for Audio Units. This works well for saving the user presets in the Host, but I get an error when trying to save them in the plugin. I'm not using a parameter tree, but instead using the fullState's getter and setter for saving and retrieving a dictionary with the state. With some simplified parameters it looks something like this: var gain: Double = 0.0 var frequency: Double = 440.0     private var currentState: [String: Any] = [:] override var fullState: [String: Any]? {     get {       // Save the current state       currentState["gain"] = gain       currentState["frequency"] = frequency       // Return the preset state       return ["myPresetKey": currentState]     }     set {       // Extract the preset state       currentState = newValue?["myPresetKey"] as? [String: Any] ?? [:]       // Set the Audio Unit's properties       gain = currentState["gain"] as? Double ?? 0.0       frequency = currentState["frequency"] as? Double ?? 440.0     }  } This works perfectly well for storing user presets when saved in the host. When trying to save them in the plugin to be able to reuse them across hosts, I get the following error in the interface: "Missing key in preset state map". Note that I am testing mostly in AUM. I could not find any documentation for what the missing key is about and how can I get around this. Any ideas?

I have an app that supports AUv3 and can output both Audio and MIDI information. It has the Audio Unit Type set to "aumu" which is a 'music generator'. This has worked well In iOS hosts until now (like AUM, or ApeMatrix) - because they allow the selection of this type of Audio Unit both as an audio generator and as a MIDI sender. So if someone wants to use it as an audio generator, they can - same as someone who only wants to use it as MIDI FX. Logic Pro on the iPad has changed this since it's not seeing it under the Midi FX selection. Is there any configuration to bypass this, or do I have to change to a Midi FX AUv3 ('aumi') for this to show up there?

I have a recently approved app (launched on March 11th). On March 12th I generated 20 promo codes to hand out to users. These were generated in App Store Connect > Services > Promo Codes. Users are now reporting that none of the promo codes work. Some don't get any message, the redeem dialogue just doesn't do anything. Others got an error "This item is no longer available". Is this a bug or have I done a mistake when generating the promo codes?