Basically, now that a client app should not send unsent messages for an Action Channel, we should find ways to do this automatically, and better. Currently, after an action message's target message is sent successfully, ActionMessageManager gets a chance to then update its action message specs and then send unsent action messages. For this reason, this should work MOST of the time, but there will be scenarios when the action messages do not get sent (e.g. 429 too many requests), and will have to be sent later.
See https://github.com/rrbrambley/MessageBeast-Android/issues/39.
Basically, now that a client app should not send unsent messages for an Action Channel, we should find ways to do this automatically, and better. Currently, after an action message's target message is sent successfully, ActionMessageManager gets a chance to then update its action message specs and then send unsent action messages. For this reason, this should work MOST of the time, but there will be scenarios when the action messages do not get sent (e.g. 429 too many requests), and will have to be sent later.