[10.15b2] Launch System App Fails to Activate

Using BTT 3.098, I have multiple mapped commands to launch apps with key sequences that worked perfectly in Mojave. When updating to Dev Beta 2 of Catalina, they no longer function. This occurs only for system applications however.****

The copied command code for the non-working commands are:

    [
      {
        "BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
        "BTTPredefinedActionType" : 49,
        "BTTPredefinedActionName" : "Launch Application \/ Open File \/ Start Apple Script …",
        "BTTLaunchPath" : "file:\/\/\/Applications\/Mail.app",
        "BTTAdditionalConfiguration" : "1179648",
        "BTTEnabled2" : 1,
        "BTTKeyboardShortcutKeyboardType" : 40,
        "BTTUUID" : "14A22FE1-5608-4FC3-8807-072674E976BE",
        "BTTTriggerOnDown" : 1,
        "BTTNotesInsteadOfDescription" : 0,
        "BTTEnabled" : 1,
        "BTTModifierMode" : 0,
        "BTTShortcutKeyCode" : 1,
        "BTTShortcutModifierKeys" : 1179648,
        "BTTOrder" : 0,
        "BTTDisplayOrder" : 0,
        "BTTAutoAdaptToKeyboardLayout" : 0
      },
      {
        "BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
        "BTTPredefinedActionType" : 49,
        "BTTPredefinedActionName" : "Launch Application \/ Open File \/ Start Apple Script …",
        "BTTLaunchPath" : "file:\/\/\/Applications\/Messages.app",
        "BTTAdditionalConfiguration" : "1179658",
        "BTTEnabled2" : 1,
        "BTTKeyboardShortcutKeyboardType" : 0,
        "BTTUUID" : "F6B1D897-ABD4-4CBA-8318-387EB6164391",
        "BTTTriggerOnDown" : 1,
        "BTTNotesInsteadOfDescription" : 0,
        "BTTEnabled" : 1,
        "BTTModifierMode" : 0,
        "BTTShortcutKeyCode" : 46,
        "BTTShortcutModifierKeys" : 1179648,
        "BTTOrder" : 1,
        "BTTDisplayOrder" : 0,
        "BTTAutoAdaptToKeyboardLayout" : 0
      }
    ]

What was very interesting to see is that if you enter the settings and click on the action of "Launch Messages.app" the icon for the application is missing, and as soon as you hit that point it will then change to launch(null). As a result, it appears something in the system changes how it is recognized

Not sure if anything can be done about this bug, but I wanted to report it to ensure that it is on your radar.

After resetting the app to the correct app, and not a (null) app, it functions properly. This could be an issue for users with significant number of applications used this way.