# Interface ContinuityCallback

public interface ContinuityCallback

The framework's inbound seam, handed to every `ContinuityBridge` during initialization. Ports call it when the platform delivers something; they never dispatch to application code themselves.

Both methods may be called from any thread, including before the application has a form on screen: on Apple platforms a continuation can cold-launch the app, and the operating system hands it over while the virtual machine is still starting. The framework holds such a delivery until there is somewhere to show it, so implementations must not try to do that themselves.

- ## Method Summary

  Modifier and Type
  Method
  Description
  `boolean`
  `continuationReceived(String activityType, Map<String,Object> userInfo)`
  A continuation arrived from one of the user's other devices.
  `void`
  `syncedStoreChanged()`
  The synced store changed underneath the app, because another of the user's devices wrote to it.

- ## Method Details

  - ### continuationReceived

    boolean continuationReceived(String activityType, Map<String,Object> userInfo)

    A continuation arrived from one of the user's other devices.

    ###### Parameters

    - `activityType`: the reverse-DNS type it arrived under
    - `userInfo`: the payload, as strings, numbers, booleans, lists and maps of those

    ###### Returns

    true when the application claimed it, so the port can answer the platform honestly rather than swallowing activities this app never published

  - ### syncedStoreChanged

    void syncedStoreChanged()
    The synced store changed underneath the app, because another of the user's devices wrote to it. Carries no values: the framework re-reads what it needs.