microg / microg/GmsCore

Choosing "Allow and share" for access to Google account simply leads to reiteration of the same prompt

Open
#3,666 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
14.6k
Forks
3.2k
PR merge metrics
PR metrics pending

Description

# Scope

The issue affects any application seeking to interact with a Google account.

# Description

I use microG currently on two devices, and on both find the same behavior not as desired.

When an application attempts contact with a Google account, microG produces a popup overlay entitled "Allow to sign you in to ".

The options available are "Cancel" and "Allow and share".

In most cases, after is selected "Cancel", the application will proceed, without any further such prompts, and presumably without any interaction with the Google account.

However, if interaction with the Google account is desired, then it would be necessary to choose "Allow and share". However, choosing the particular option results in the same prompt being reproduced immediately. Always selecting "Allow and share" would produce an infinite loop. Selecting "cancel" is necessary to exit the loop.

# Steps to reproduce

Unfortunately, I have never observed correct behavior for the particular aspect of microG.

As such, I cannot provide any steps that specifically would reproduce the issue.

# Expected behavior

After selecting "Allow and share", the application proceeds normally, now having access to the Google account.

# Screenshots

See below for screen captures.

# System

The AOSP version is 16.

The system image is Lineage OS 23.2, from a build distributed by the microG project (i.e. Lineage for microG).

The device is a Pixel 4.

# microG

- microG Core version: 0.3.15.250932

- microG Self-Check results: All ticked

----

Image

Image

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the consent loop on the reported Pixel 4, Lineage for microG, AOSP 16 environment with microG Core 0.3.15.250932, since the report provides no reliable reproduction steps or code entry point. Investigate the Google-account access flow; done means selecting “Allow and share” lets the application proceed without repeating the prompt.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.