microg / microg/GmsCore

Exposure database cleared

Open
#1,347 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

The exposure notification database was cleared.

To Reproduce
No idea if this is reproducible but it seemed to warrant a report.
I looked at my phone first thing this morning to see a warning from the swiss covid app that collection had been deactivated.
Clicked on reactivate and from the corona-warn companion app I can see only today's data and some from yesterday.
Yesterday evening companion app was showing last two weeks. I checked the database file size and it had clearly been reset.
I have gone back through the logs hunting for something that might help but I don't really know what I am looking for and at what time.
Since the database shows entries from yesterday I assume I am looking for an error last night. Using logcat -b crash doesn't show anything after 3.00 yesterday morning so probably not that?
Anyway I am not really concerned about the crash more that something could cause the database to be reset like this!

Expected behavior
Database should never be cleared like this

Screenshots
If applicable, add screenshots to help explain your problem.

System
Android Version: 7.1.2
Custom ROM: LineageOS 14.1]

Additional context
Microg 2.15.204713

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the exposure notification database and the available logcat output, including the crash buffer, around the reported overnight reset on Android 7.1.2 with LineageOS 14.1 and MicroG 2.15.204713. Done means identifying what cleared the database and confirming that the database is no longer unexpectedly reset.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.