FIX ANDROID APP SECURITY ISSUES.
Budget: $2 – $8 USD
I have 3 demands to correct in my application, I have the AAB version of the application but I don't have the sources, and I have the smali files.
1) Device and Network Abuse Policy: Insecure TrustManager Implementation
We have identified that the app contains security vulnerabilities that could expose information or damage users' devices. This is a violation of the device and network abuse policy. Specifically, the apps contain an insecure implementation of TrustManager .
To resolve this issue, follow the steps in this Google Help Center article .
https://support.google.com/faqs/answer/6346016
2) Device and Network Abuse Policy: Insecure HostnameVerifier Implementation
We have identified that the app contains security vulnerabilities that could expose information or damage users' devices. This is a violation of the device and network abuse policy. Specifically, the apps contain an insecure implementation of HostnameVerifier .
To resolve this issue, follow the steps in this Google Help Center article .
https://support.google.com/faqs/answer/7188426
3)Action required: Migrate to the supported version of the Google Play Billing Library
We are changing the lifecycle of this API and associated deprecation timelines. As you use an older version of the library, check out the important new dates to stay compliant:
Until August 31, 2024 , all new apps and updates will need to use version 6 or newer of the Billing Library. If you need more time to update your app, you can request an extension until November 1, 2024.
Learn more about the discontinuation at this link .
Update before these deadlines to avoid interrupting app publishing and updates . From the dates mentioned above, it will not be allowed to publish and update apps on the Play Console that use a version of the Play Billing Library prior to 6.
Next steps : check out more information about how to migrate to the latest version of the Play Billing Library on the website from the developer .
1) Device and Network Abuse Policy: Insecure TrustManager Implementation
We have identified that the app contains security vulnerabilities that could expose information or damage users' devices. This is a violation of the device and network abuse policy. Specifically, the apps contain an insecure implementation of TrustManager .
To resolve this issue, follow the steps in this Google Help Center article .
https://support.google.com/faqs/answer/6346016
2) Device and Network Abuse Policy: Insecure HostnameVerifier Implementation
We have identified that the app contains security vulnerabilities that could expose information or damage users' devices. This is a violation of the device and network abuse policy. Specifically, the apps contain an insecure implementation of HostnameVerifier .
To resolve this issue, follow the steps in this Google Help Center article .
https://support.google.com/faqs/answer/7188426
3)Action required: Migrate to the supported version of the Google Play Billing Library
We are changing the lifecycle of this API and associated deprecation timelines. As you use an older version of the library, check out the important new dates to stay compliant:
Until August 31, 2024 , all new apps and updates will need to use version 6 or newer of the Billing Library. If you need more time to update your app, you can request an extension until November 1, 2024.
Learn more about the discontinuation at this link .
Update before these deadlines to avoid interrupting app publishing and updates . From the dates mentioned above, it will not be allowed to publish and update apps on the Play Console that use a version of the Play Billing Library prior to 6.
Next steps : check out more information about how to migrate to the latest version of the Play Billing Library on the website from the developer .