Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uploaded The Google Play Store detected the following issues #2821

Open
pangli opened this issue Mar 7, 2025 · 3 comments
Open

Uploaded The Google Play Store detected the following issues #2821

pangli opened this issue Mar 7, 2025 · 3 comments

Comments

@pangli
Copy link

pangli commented Mar 7, 2025

signal/deobfuscated_urls: 
deobfuscated ur: htts://ithub.com/google/gson/blob/main/Troubleshooting.md/#18-abstract class from class Lcom/google/gson/internal/Troubleshooting Guide: & 
deobfuscated urt: https://github.com/google/gson/blob/main/Troubleshooting.md#java-lang-class-unsupported from class Lcom/google/gson/internal/TroubleshootingGuide;

Image

The following obfuscation is configured

-keep class * extends com.google.gson.TypeAdapter
-keep class * implements com.google.gson.TypeAdapterFactory
-keep class * implements com.google.gson.JsonSerializer
-keep class * implements com.google.gson.JsonDeserializer
-keep,allowobfuscation,allowshrinking class com.google.gson.reflect.TypeToken
-keep,allowobfuscation,allowshrinking class * extends com.google.gson.reflect.TypeToken
-keepclassmembers,allowobfuscation class * {
  @com.google.gson.annotations.SerializedName <fields>;
}
-assumenosideeffects class com.google.gson.internal.TroubleshootingGuide {
    public static java.lang.String createUrl(java.lang.String);
}

What can I do about this problem, please? How to remove this Url when packaging?

@Marcono1234
Copy link
Collaborator

Could you please clarify what exactly the issue here is?

  • What tool is reporting this issue?
  • Why is it an issue?

Gson's internal TroubleshootingGuide class creates URLs for troubleshooting Gson configuration issues. They are only used in exception messages, Gson does not open those URLs.

@pangli
Copy link
Author

pangli commented Mar 13, 2025

Could you please clarify what exactly the issue here is?

  • What tool is reporting this issue?
  • Why is it an issue?

Gson's internal TroubleshootingGuide class creates URLs for troubleshooting Gson configuration issues. They are only used in exception messages, Gson does not open those URLs.

Image
Uploading Google app store, when the app was rejected, the internal staff gave some questions, which included a signal/deobfuscated_url issue for Gson, our app aab package is obfuscated, I searched for this url after decompiling the app using jadx tool . can this url be removed when packaging the official version? Preventing similar warnings from appearing on shelves?

@Marcono1234
Copy link
Collaborator

Marcono1234 commented Mar 15, 2025

which included a signal/deobfuscated_url issue for Gson

I am not very familiar with Android development, but I cannot find any information when googling for this specific issue name. And it is not really clear to me why they are rejecting the app due to this. Is it because they think this URL concatenation obscures the purpose of the URL, and that it is potentially used for malicious purposes?


can this url be removed when packaging the official version?

Do you mean the Gson release JAR should not include this URL? That would probably defeat the whole purpose of this code, which is to make it easier for users to understand Gson exceptions.

That code exists since Gson 2.11.0, which has been released nearly a year ago and so far no other user has mentioned that this is a problem (at least not here on GitHub).
Have you mentioned to the Google app store reviewers that this is part of the Gson library and not your own code?

Maybe you could try adding a -keep class com.google.gson.internal.TroubleshootingGuide to your R8 config, so that the class is preserved and the Google app store reviewers see that this is not an attempt to obfuscate URLs or similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants