We were catching an exception, but not stopping execution of the code which could result in a message being delivered when sent with an invalid app ID.
This could only really happen if you updated the App ID in your environment and immediately began broadcasting with the new App ID without restarting the Reverb server.
To address this, the exception is being caught higher up by the server instead of directly in the controller.
This PR resolved #142
We were catching an exception, but not stopping execution of the code which could result in a message being delivered when sent with an invalid app ID.
This could only really happen if you updated the App ID in your environment and immediately began broadcasting with the new App ID without restarting the Reverb server.
To address this, the exception is being caught higher up by the server instead of directly in the controller.