MemberActivityEvent

A discrete change to the member's calendar / activities feed.

Subscribe via com.advantahealth.api.activities.Activities.activityEvents (Kotlin coroutines) or com.advantahealth.api.activities.Activities.subscribeToActivityEvents (callback bridge for Swift). Use these events as a "refresh now" signal — every emission corresponds to a server-confirmed change that actually altered what the Mobile API will return for com.advantahealth.api.activities.Activities.get.

Duplicates are filtered out. If a submission is rejected as a duplicate (e.g. a selfie for a date that already has one, a self-report on a date that already exists, an automatic visit the server collapses into an existing entry), no event fires — because the calendar didn't change. If the result is a 2xx network failure for any other business-validation reason (status == false), no event fires either, for the same reason.

Offline submissions are deferred. A submission queued to the offline outbox (AFResult.queued == true) does NOT fire an event immediately, because the calendar on the server hasn't changed yet. The event fires later when the outbox flush actually delivers the submission to the server.

See SharedFlow semantics: replay = 0, so a subscriber that attaches after an event has fired does NOT receive that event on attach. This avoids spurious refreshes on screen revisit. Pair this with com.advantahealth.api.activities.Activities.get to fetch the current month state when the screen first opens.

Inheritors