# Group expiry refresh — 0.6.7 / build 15 The owner could change a group's maximum message lifetime while an older state request was in flight. The forced refresh returned immediately, leaving the composer's expiry choices at the previous maximum until a later poll. Forced refreshes now wait for the active sync and request another complete sync. The change dialog closes after that refresh, and both owner and member composers use the accepted roster. Draft text and valid shorter lifetime choices survive. The displayed and sent lifetimes use one normalization function. Switching a group from retained to finite messages resets an obsolete permanent draft choice to the new maximum; a previous longer choice is capped at a lower maximum. Existing signed message expirations are not rewritten. `scripts/check-group-expiry.mjs` reproduces the old failure with a delayed pre-change state response. It then exercises longer, shorter, permanent and finite group limits using disposable owner/member profiles and a real isolated relay, under the iOS, Android and Web UI adapters. The old code fails with only 60/3600 seconds available after increasing the maximum to 604800 seconds. The fixed code passes all three adapters. The 90-function test suite also passes. These browser checks do not establish physical iPhone or Android acceptance. Build 14 already uploaded to Apple must not be uploaded again or relabelled. This correction has a distinct version 0.6.7 and Android/iOS build number 15.