microg / microg/GmsCore

[ jp.naver.line.android] <I can't access my Google account.>

Open
#2,830 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

https://github.com/user-attachments/assets/ac378b43-be41-4f8f-956a-59b674d86dbb

Affected app
Name: LINE
Package ID: jp.naver.line.android

Describe the bug
A clear and concise description of what the bug is.
Cannot access Google account.

To Reproduce
Steps to reproduce the behavior:

Go to "Settings"
Click on "Backup and restore chat history"
Click on "Restore or Back up now" and log in to the account
An error occurs
Expected behavior
The account should be selected, and the chat should be backed up or restored.

Screenshots
Since this behavior is unusual, I have attached a video instead.

System
Android Version: 13
Custom ROM: MagiskOnWSALocal

Magisk + LSPosed + FakeGApps

microG
microG Core version: v0.3.6.244735
microG Self-Check results: Only SafetyNet is unchecked

////////////////
I am verifying whether LINE is compatible with microG.

The difference between a device with microG and a device with GApps was whether the following was called or not.
(This is an Xposed module for verification, which logs calls that start with "com.google.android.gms.")
GApps Device(Expected behavior)

2025-03-20 21:32:28.624 23783-21475 LSPosed-Bridge          jp.naver.line.android                I  [GMS-LOGGER] [com.google.android.gms.common.internal.h.a]
                                                                                                    Return Type: g0 (com.google.android.gms.common.internal.g0)
                                                                                                    Return Value: com.google.android.gms.common.internal.g0@d29211f
                                                                                                    Arguments:
                                                                                                      [0] LineApplication: jp.naver.line.android.LineApplication@bae0fd3
2025-03-20 21:32:28.626 23783-21475 LSPosed-Bridge          jp.naver.line.android                I  [GMS-LOGGER] [com.google.android.gms.common.internal.d0.a]
                                                                                                    Return Type: Intent (android.content.Intent)
                                                                                                    Return Value: Intent { cmp=com.google.android.gms/.auth.GetToken }
                                                                                                    Arguments:
                                                                                                      [0] LineApplication: jp.naver.line.android.LineApplication@bae0fd3

There were no obvious errors in the log cat.

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 failure through LINE's Settings > Backup and restore chat history > Restore or Back up now flow on the documented Android, microG, and FakeGApps setup. Compare the account-selection and authentication behavior with a GApps device, using the supplied video and GMS logger output; done means the account can be selected and chat history can be backed up or restored.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
authentication, mobile-dev
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.