Fixed
Status Update
No update yet.
Comments
uc...@google.com
xa...@google.com
sr...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Which Android build are you using? (e.g. TQ3A.230705.001.A1)
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Which Android build are you using? (e.g. TQ3A.230705.001.A1)
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
sr...@google.com
sr...@google.com
We can't repro the issue on our test devices so can't really help with the build number and the bug report unfortunately we got this crashes through our crash reporting service. I can share a list of devices and os versions this crash is occurring if it helps.
sr...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
lb...@gmail.com
Hi. Are there any updates on this issue?
sr...@google.com
We've resolved this bug, and the fix will be included in the upcoming version. We'll update this issue once that version is released.
sr...@google.com
Thanks for the update. Is the fix going to be on Google Play Services or we will have to update a library in the app?
sr...@google.com
this issue is still not fixed under 2.0.2 version of review and review-ktx.
following is the crashlog recently we are facing
build.gradle:
implementation("com.google.android.play:review:2.0.2")
implementation("com.google.android.play:review-ktx:2.0.2")
Exception:
Log1:
Fatal Exception: java.lang.NoClassDefFoundError
Failed resolution of: Lcom/google/android/play/core/common/PlayCoreDialogWrapperActivity;
Log2:
Caused by java.lang.ClassNotFoundException
com.google.android.play.core.common.PlayCoreDialogWrapperActivity
com.google.android.play.core.review.zzd.launchReviewFlow (com.google.android.play:review@@2.0.2:2)
com.bnb.paynearby.legacy.PlayStoreInAppFeedback.showInAppPopupFeedback$lambda$1 (PlayStoreInAppFeedback.java:34)
com.google.android.gms.tasks.zzi.run (com.google.android.gms:play-services-tasks@@18.1.0:1)
android.os.Handler.handleCallback (Handler.java:958)
android.os.Handler.dispatchMessage (Handler.java:99)
android.os.Looper.loopOnce (Looper.java:257)
android.os.Looper.loop (Looper.java:368)
android.app.ActivityThread.main (ActivityThread.java:8839)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:572)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1049)
following is the crashlog recently we are facing
build.gradle:
implementation("com.google.android.play:review:2.0.2")
implementation("com.google.android.play:review-ktx:2.0.2")
Exception:
Log1:
Fatal Exception: java.lang.NoClassDefFoundError
Failed resolution of: Lcom/google/android/play/core/common/PlayCoreDialogWrapperActivity;
Log2:
Caused by java.lang.ClassNotFoundException
com.google.android.play.core.common.PlayCoreDialogWrapperActivity
com.google.android.play.core.review.zzd.launchReviewFlow (com.google.android.play:review@@2.0.2:2)
com.bnb.paynearby.legacy.PlayStoreInAppFeedback.showInAppPopupFeedback$lambda$1 (PlayStoreInAppFeedback.java:34)
com.google.android.gms.tasks.zzi.run (com.google.android.gms:play-services-tasks@@18.1.0:1)
android.os.Handler.handleCallback (Handler.java:958)
android.os.Handler.dispatchMessage (Handler.java:99)
android.os.Looper.loopOnce (Looper.java:257)
android.os.Looper.loop (Looper.java:368)
android.app.ActivityThread.main (ActivityThread.java:8839)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:572)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1049)
lb...@gmail.com
@9 I see.
Why is it marked as "fixed" though?
Why is it marked as "fixed" though?
sr...@google.com
It is marked as fixed because the original issue (pointing to a prefix path instead of the full path) is no longer present on 2020.3.1 Beta 1.
lb...@gmail.com
@11 So now there won't ever be links being shown that when you press them they go to somewhere else, and that they aren't even marked as the full path ?
Description
Version of Gradle Plugin:
Version of Gradle:
Version of Java:
OS:
Android Studio 4.0.1
Build #AI-193.6911.18.40.6626763, built on June 25, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 7954M
Cores: 12
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins: String Manipulation, org.jetbrains.kotlin, com.google.services.firebase, ignaciotcrespo.github.com.vector-drawable-thumbnails, org.intellij.plugins.markdown
Steps to Reproduce:
0. Have projects created on a path such as:
"C:\android\Android studio Projects\YourApp".
1. Have something wrong on the project, so that when you try to generate the APK, it will show a link to the issue. In my case, it was a string that's translated to some language but doesn't even exist on English strings file.
2. Try to build a signed APK.
3. Press the link to the error that you see.
The bug is that it won't go to the file. Instead it will mark and go to a partial path of it.
In my case it will go to a folder :
C:\android\Android Studio
instead of the file:
C:\android\Android studio Projects\AppManager\app\src\main\res\values-zh-rCN\strings.xml (on the specific line)