How to properly reject an update over a state channel

Protocol Features & Updates State Channels
4

Thanks guys, regarding this:

  • Can we rely on the signing timeout to expire or the FSM wont return to open state even when the timer expires?

  • If this is the case, cancelling a transaction for our base-aepp hosted app would include workarounds mentioned here (issuing a conflicting update) .
    Another fast hack idea:
    Could be possible to make the base-aepp to enter “auto-signing” mode for a specific application or scenario [e.g: just channel updates] ? For example, once the user confirms the account access, channel updates could be “autosigned” avoiding the “handling cancellation of an update, use the workaround,etc” issue.

Thanks again,
Hernan