Fixed

Bug

Status Update

No update yet.

Description

ha...@meta.com

created issue #1

May 28, 2024 03:15PM

We can't reproduce these but after integrating with the in app review library we started to see crash reports with these stack traces at the bottom. We don't have info on the Google play services version on the client. But the issues might be device specific. Seems like we are on the latest versions of these libraries.

app library versions :

com.google.android.play:core-common: 2.0.3 com.google.android.play:review: @2.0.1

Crash 1

Mostly occuring on some xioami devices on android 14 Top 3 devices: Xiaomi-23127PN0CG Xiaomi-22071212AG Xiaomi-2303ERA42L

Trace: java.lang.RuntimeException: Unable to start activity ComponentInfo{ com.app/com.google.android.play.core.common.PlayCoreDialogWrapperActivity}: android.content.ActivityNotFoundException: No Activity found to handle null
- android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3971)
- android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:4124)
- android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:103)
- android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:149)
- android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:99)
- android.app.ActivityThread$H.handleMessage (ActivityThread.java:2572)
- android.os.Handler.dispatchMessage (Handler.java:106)
- android.os.Looper.loopOnce (Looper.java:224)
- android.os.Looper.loop (Looper.java:318)
- android.app.ActivityThread.main (ActivityThread.java:8677)
- java.lang.reflect.Method.invoke (Native Method:0)
- com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:561)
- com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1013)
- Caused by: android.content.ActivityNotFoundException: No Activity found to handle null
- android.app.Instrumentation.checkStartActivityResult (Instrumentation.java:2280)
- android.app.Activity.startIntentSenderForResultInner (Activity.java:6205)
- android.app.Activity.startIntentSenderForResult (Activity.java:6168)
- android.app.Activity.startIntentSenderForResult (Activity.java:6123)
- com.google.android.play.core.common.PlayCoreDialogWrapperActivity.onCreate (com.google.android.play:core-common@@2.0.3:12:0)
- android.app.Activity.performCreate (Activity.java:8891)
- android.app.Activity.performCreate (Activity.java:8856)
- android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1468)
- android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3953)

Crash 2

mostly occuring on vivo and huawei devices on differend android versions

top 3 devices vivo-V2027 vivo-V2029 HUAWEI-CAM-L21

Trace: java.lang.RuntimeException: Unable to start activity ComponentInfo{ com.app/com.google.android.play.core.common.PlayCoreDialogWrapperActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.IntentSender android.app.PendingIntent.getIntentSender()' on a null object reference
- android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3973)
- android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:4138)
- android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:103)
- android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135)
- android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95)
- android.app.ActivityThread$H.handleMessage (ActivityThread.java:2458)
- android.os.Handler.dispatchMessage (Handler.java:106)
- android.os.Looper.loopOnce (Looper.java:233)
- android.os.Looper.loop (Looper.java:334)
- android.app.ActivityThread.main (ActivityThread.java:8513)
- java.lang.reflect.Method.invoke (Native Method:0)
- com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:582)
- com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1068)
- Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.IntentSender android.app.PendingIntent.getIntentSender()' on a null object reference
- com.google.android.play.core.common.PlayCoreDialogWrapperActivity.onCreate (com.google.android.play:core-common@@2.0.3:11:0)
- android.app.Activity.performCreate (Activity.java:8506)
- android.app.Activity.performCreate (Activity.java:8484)
- android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1379)
- android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3946)

Comments

vi...@google.com <vi...@google.com> #2May 29, 2024 11:28AM

Assigned to vi...@google.com.

Converting to an enhancement request.

ha...@meta.com <ha...@meta.com> #3Jun 3, 2024 04:15PM

Any update on the status of this enhancement?

vi...@google.com <vi...@google.com> #4Jun 18, 2024 02:34AM

Fails for UrlFetches to far-away places like China. Making it configurable would be useful -- or reporting it as an actual timeout would help as well.

to...@gmail.com <to...@gmail.com> #5Sep 24, 2024 02:31PM

I also need this feature, any update on the status ?

ra...@google.com <ra...@google.com> #6Oct 4, 2024 08:51PM

Any update?

to...@gmail.com <to...@gmail.com> #7Oct 7, 2024 11:18AM

Any update on this feature request, Its really important for us to have this feature

ra...@google.com <ra...@google.com> #8Oct 22, 2024 08:09PM

Marked as fixed.

I'm seeing the opposite issue lately. The UrlFetchApp.fetch call is taking far too long, the worst today is 257sec. I'd like to set a 10-30sec timeout and stop these calls from using up all of my time-based quotas. There must be an issue with this function as manually calling these urls is much faster, typically a second or less.

ra...@paynearby.in <ra...@paynearby.in> #9Jan 7, 2025 07:19AM

Yes, I need a configurable timeout to prevent a single long running fetch from eating up all the time-based quota.

IssueTracker

Crashes at PlayCoreDialogWrapperActivity after integrating the In app review library .

Status Update

Description

Crash 1

Crash 2

Comments

vi...@google.com <vi...@google.com> #2May 29, 2024 11:28AM

ha...@meta.com <ha...@meta.com> #3Jun 3, 2024 04:15PM

vi...@google.com <vi...@google.com> #4Jun 18, 2024 02:34AM

to...@gmail.com <to...@gmail.com> #5Sep 24, 2024 02:31PM

ra...@google.com <ra...@google.com> #6Oct 4, 2024 08:51PM

to...@gmail.com <to...@gmail.com> #7Oct 7, 2024 11:18AM

ra...@google.com <ra...@google.com> #8Oct 22, 2024 08:09PM

ra...@paynearby.in <ra...@paynearby.in> #9Jan 7, 2025 07:19AM

Issue 343086058

Description

Crash 1

Crash 2

Issue summary

Comments

vi...@google.com <vi...@google.com> #2May 29, 2024 11:28AM

ha...@meta.com <ha...@meta.com> #3Jun 3, 2024 04:15PM

vi...@google.com <vi...@google.com> #4Jun 18, 2024 02:34AM

to...@gmail.com <to...@gmail.com> #5Sep 24, 2024 02:31PM

ra...@google.com <ra...@google.com> #6Oct 4, 2024 08:51PM

to...@gmail.com <to...@gmail.com> #7Oct 7, 2024 11:18AM

ra...@google.com <ra...@google.com> #8Oct 22, 2024 08:09PM

ra...@paynearby.in <ra...@paynearby.in> #9Jan 7, 2025 07:19AM

Add comment

Issue metadata