Skip to content

on_resume vs on_new_intent firing #1671

Description

@BrendanScottAU

I have an application which implements both on_resume and on_new_intent (the intent is a VIEW action from the file viewer).
Unfortunately, if it receives a new intent while it is paused (the most likely scenario) then on_new_intent and on_resume fire in an undefined order (sometimes on_resume is first, sometimes not). Either way one fires while the other is still executing.
This is a problem because if there is no intent I want to restore the saved state. However, if there is a new intent I want to reinitialise based on the intent received. I can't see a way for testing one vs the other.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions