Skip to content

Plugin sometimes gets "stuck" in detected or not detected state #34

@hawksley

Description

@hawksley

Where it will claim to be detecting a rift that is not plugged in or vice versa. This will sometimes continue across Chrome restarts, forcing a re-install of the plugin (after which it seems to work again)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions