Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 693
    • Issues 693
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #1224

Closed
Open
Opened May 09, 2018 by akwizgran@akwizgranOwner

Explain when no transports can be used for adding a contact

When adding a contact in person, there are various circumstances where we can tell as soon as we've scanned the contact's QR code that we won't be able to communicate. For example:

  • Both devices support Bluetooth, but neither device knows its own Bluetooth address (Android 8, see #1147)
  • Both devices support wifi but they're on different networks (see #1223, #1178 (closed))
  • One device only supports Bluetooth, the other only supports wifi If the user declines to activate Bluetooth and there's no wifi connection, we can tell even sooner that we won't be able to communicate.

We should detect these situations and explain the problem to the user in an actionable way.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#1224