In-App Review Component Unstable

The In-App Review Component appears to be broken in its current state. The request review block:

component_method

instantly causes the app to freeze in my testing.

I have tried it on a large project on a build downloaded through Internal Testing on the Play Store, as well as a fresh dummy project with no extensions or other stuff that could conflict.

blocks

:backhand_index_pointing_up:t3: I would expect this to work…

If you like to help finding out whats going on, then use logcat and provide the logcat output here

Taifun

1 Like

This appears to be the primary error:

System.err: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.kanishka_developer.SketchPad/com.google.android.play.core.common.PlayCoreDialogWrapperActivity}; have you declared this activity in your AndroidManifest.xml, or does your intent not match its declared <intent-filter>?
1 Like

com.jewel.inapphelper.aix (3.8 KB)

It might be helpful for you. Just put it in Screen1.

1 Like

If the community could be this hurry in response mostly in heavy functions like this and problem solving, it would be unstoppable community, appreciate your energy @JEWEL

1 Like

I made my own extension to fix the issue (also fixable by manually editing the manifest and changing the line):

<activity android:enabled="false" android:exported="false" android:name="com.google.android.play.core.common.PlayCoreDialogWrapperActivity" android:stateNotNeeded="true" android:theme="@style/Theme.PlayCore.Transparent"/>

to:

<activity android:enabled="true" android:exported="false" android:name="com.google.android.play.core.common.PlayCoreDialogWrapperActivity" android:stateNotNeeded="true" android:theme="@style/Theme.PlayCore.Transparent"/>


The point of my thread is to bring attention to the bug itself. We should not need to modify AndroidManifest.xml manually for a component to not break an app.

3 Likes

Added to the BugsTracker
and moved to Feedback > Bugs

2 Likes