Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
B
Backlog
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 916
    • Issues 916
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • e
  • Backlog
  • Issues
  • #1062

Closed
Open
Opened Mar 15, 2020 by Sylvain Manceau@smu440 of 5 tasks completed0/5 tasks

Contact created from phone marked as "broken" in /e/ Cloud

  • /e/ version: lineage_chiron-userdebug 9 PQ3A.190801.002 eng.root.20200312.215330 test-keys
  • Device model: Xiaomi Mi Mix 2 (chiron)
  • When it started to occur: Not sure, happens also with contacts created weeks ago (with /e/ Oreo official)
  • Reproducible with the last /e/ version: yes
  • Reproducible with LineageOS: n/a, /e/ specific

Summary

A contact created from /e/ phone is flagged as "broken" in /e/ Cloud.

  • The device is unusable
  • The bug is the source of a data loss or a big waste of time
  • The bug concerns a third-party application
  • The bug concerns security
  • The bug concerns privacy

The problem

Steps to reproduce

1 create a contact using /e/ phone, sync 2 go to /e/ cloud, search for contact (see attached screenshots)

What is the current behavior?

Contact is flagged as "broken" in /e/ Cloud. However there is no noticeable difference.

What is the expected correct behavior?

Contact should not be "broken".

Technical informations

Relevant logs (adb logcat)

No relevant information.

Relevant screenshots

Annotation_2020-03-15_121737

Annotation_2020-03-15_121744

Solutions

Workaround

Browse all contact in /e/ Cloud, fix them.

Possible fixes

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Mar 31, 2021
Due date
Mar 31, 2021
Reference: e/backlog#1062