Skip to content

v0.16.7 - FCM decrypt resilience

Choose a tag to compare

@bvis bvis released this 19 Jun 09:27
4bc82f6

Fixed

  • FCM listener no longer dies in a reconnect loop on an undecryptable push (#25) — follow-up to the #21 crypto-key padding fix. A malformed crypto-key (dh=) value that decodes to an invalid P-256 point made http_ece raise ValueError: Invalid EC key, which propagated to the upstream _listen catch-all and shut the client down. Because the crash happened before the message was acknowledged, MCS redelivered the same poisoned message on every reconnect — an endless crash/restart loop with no notifications. The per-message decrypt is now isolated: any decode/decrypt failure is logged and that single message is skipped so the listener acks it and stays alive to process the next push.

Confirmed in the wild by the reporter (FCM stays connected; notifications and camera streaming restored).