Description
2025-03-21.11-54-42.mp4
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@bae0fd3There were no obvious errors in the log cat.
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Participants
Activity
areteruhiro commentedon Mar 21, 2025