microg / microg/GmsCore

Exposure Notifications active, but no IDs broadcasted or received

Open
#1,353 1 comment 0 reactions 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

Describe the bug
Exposure Notifications are supposedly active, but no IDs are collected or broadcast.

To Reproduce
Steps to reproduce the behavior:

  1. Open either CWA or CCTG to enable exposure notifications
  2. MicroG crashes once, but EN are enabled after.
  3. MicroG appears to broadcast an ID, which it also collects.
  4. After a while, no IDs have been collected and the "currently broadcasted ID" field is empty.

Expected behavior
MicroG broadcasts IDs and collects them from other devices.

Screenshots
Here's what I see after a while:
Screenshot_20210105-114244_microG_Services_Core_1

The two collected IDs are from when I disabled and re-enabled EN:
Screenshot_20210105-114238_microG_Services_Core_1

So, I disable EN ams open CCTG to reenable them, and MicroG crashes:
Screenshot_20210105-114306_Corona_Tracing_1

I don't usually get this error, but it might be helpful:
Screenshot_20210105-114316_Corona_Tracing_1
Screenshot_20210105-114351_Corona_Tracing_1

Despite the error, exposure notifications are now enabled again, and my device is broadcasting an ID:
Screenshot_20210105-114403_microG_Services_Core_1_1

This time, it didn't collect any IDs, so the collected IDs are still the same as before.

If anyone tells me how to, I can include logs as well.

System
Android Version: 10
Custom ROM: Carbon ROM 8.0
Device: Xiaomi Redmi Note 7 (lavender)

Additional context
"UUID 0xFDF6 Scanner" from F-Droid confirms that other devices are broadcasting IDs.

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 reproducing the issue with CWA or CCTG on Android 10 using the reported Carbon ROM and Redmi Note 7 setup. Inspect the MicroG exposure-notification path associated with enabling, broadcasting, and collecting IDs, using the reported crash and UUID 0xFDF6 Scanner observations as evidence. Done means exposure notifications continue broadcasting and collecting IDs after activation without the crash.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.