Uploaded The Google Play Store detected the following issues

[pangli]

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;

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]

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]

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.

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]

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.

[pangli]

which included a issue for Gsonsignal/deobfuscated_url

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 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.-keep class com.google.gson.internal.TroubleshootingGuide

I would like to suggest a way for the user to decide for themselves whether to include this link in the package or to replace the link with an empty one.