microg / microg/GmsCore

[com.PigeonGames.Phigros] Phigros crashing when trying to access Google Play services after updating microG

Open
#2,096 0 comments 2 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

Affected app
Name: Phigros
Package id: com.PigeonGames.Phigros
https://play.google.com/store/apps/details?id=com.PigeonGames.Phigros&hl=en&gl=US

Describe the bug
Phigros crashes after attempting to show a Google Play popup.

To Reproduce
Steps to reproduce the behavior:

  1. Open Phigros
  2. It tries to open some Google Play popup
  3. It crashes

Expected behavior
Normally it shows some popup asking about connecting to Google Play.

Crash logs

11-21 14:39:13.810 11968 11968 E AndroidRuntime: FATAL EXCEPTION: main
11-21 14:39:13.810 11968 11968 E AndroidRuntime: Process: com.PigeonGames.Phigros, PID: 11968
11-21 14:39:13.810 11968 11968 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.PigeonGames.Phigros/com.voxelbusters.nativeplugins.features.gameservices.serviceprovider.google.GooglePlayGameUIActivity}: android.content.ActivityNotFoundException: No Activity found to handle null
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3645)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3782)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:138)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2307)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.os.Looper.loopOnce(Looper.java:201)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:288)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7924)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: Caused by: android.content.ActivityNotFoundException: No Activity found to handle null
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2200)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.Activity.startIntentSenderForResultInner(Activity.java:5896)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.Activity.startIntentSenderForResult(Activity.java:5859)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.Activity.startIntentSenderForResult(Activity.java:5814)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at com.google.android.gms.common.ConnectionResult.startResolutionForResult(Unknown Source:17)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at com.voxelbusters.nativeplugins.features.gameservices.serviceprovider.google.util.BaseGameUtils.resolveConnectionFailure(BaseGameUtils.java:79)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at com.voxelbusters.nativeplugins.features.gameservices.serviceprovider.google.GooglePlayGameUIActivity.onCreate(GooglePlayGameUIActivity.java:62)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.Activity.performCreate(Activity.java:8342)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.Activity.performCreate(Activity.java:8321)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1417)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3626)
11-21 14:39:13.810 11968 11968 E AndroidRuntime: 	... 12 more

System
Android Version: 13
Custom ROM: LineageOS 20

microG
microG Core version: 0.3.0.233515
microG Self-Check results: All ticked

Additional context
This began happening after updating from microG 0.2.29 & FakeStore 0.2.1 to microG 0.3.0. I install microG using nift4's microG installer, and this update is where the issue started.

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 crash on Android 13 with microG Core 0.3.0.233515, then trace the reported failure through GooglePlayGameUIActivity.onCreate and BaseGameUtils.resolveConnectionFailure. Done means Phigros can reach the Google Play connection popup without ActivityNotFoundException.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.