I have no idea what invokes TrustManager, and I haven't found any information about this problem elsewhere either.
Anyone knows what plugin might be the culprit?
Anyone knows what plugin might be the culprit?
- 329 Posts
- 12 Reply Likes
Posted 4 years ago
- 329 Posts
- 12 Reply Likes
This is what Google sent me:
Hello Google Play Developer,
We rejected XXXXXX, with package name XXXXXXX, for violating our Malicious Behavior policy. If you submitted an update, the previous version of your app is still available on Google Play.
This app uses software that contains security vulnerabilities for users.
Below is the list of vulnerabilities and the corresponding APK versions that were detected in your recent submission. Please upgrade your app(s) as soon as possible and increment the version number of the upgraded APK.
Vulnerability APK Version(s)
TrustManager
You can find more information about TrustManager in this Google Help Center article.
3
To confirm you’ve upgraded correctly, submit the updated version of your app to the Developer Console and check back after five hours to make sure the warning is gone.
While these vulnerabilities may not affect every app that uses this software, it’s best to stay up to date on all security patches. Make sure to update any libraries in your app that have known security issues, even if you're not sure the issues are relevant to your app.
Apps must also comply with the Developer Distribution Agreement and Developer Program Policies.
If you feel we have made this determination in error, please reach out to our policy support team.
Best,
The Google Play Team
Hello Google Play Developer,
We rejected XXXXXX, with package name XXXXXXX, for violating our Malicious Behavior policy. If you submitted an update, the previous version of your app is still available on Google Play.
This app uses software that contains security vulnerabilities for users.
Below is the list of vulnerabilities and the corresponding APK versions that were detected in your recent submission. Please upgrade your app(s) as soon as possible and increment the version number of the upgraded APK.
Vulnerability APK Version(s)
TrustManager
You can find more information about TrustManager in this Google Help Center article.
3
To confirm you’ve upgraded correctly, submit the updated version of your app to the Developer Console and check back after five hours to make sure the warning is gone.
While these vulnerabilities may not affect every app that uses this software, it’s best to stay up to date on all security patches. Make sure to update any libraries in your app that have known security issues, even if you're not sure the issues are relevant to your app.
Apps must also comply with the Developer Distribution Agreement and Developer Program Policies.
If you feel we have made this determination in error, please reach out to our policy support team.
Best,
The Google Play Team
- 329 Posts
- 12 Reply Likes
I suspect cordova-background-geolocation that can post locations to a server.
- 329 Posts
- 12 Reply Likes
I've found others with similar or same problem, but not in combination with PhoneGap Build. The theory is that an old cordova.js used somewhere. As I use PGB I don't have any cordova.js in my project, so if this is in the build process I have no way to fix it. If its in a plugin I still don't really know which one.
- 329 Posts
- 12 Reply Likes
Crap! It was the customer's own app that had this problem. I should have guessed when the package name wasn't for my app. Yes, I'm an idiot ~:).
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
Yes, I'm an idiot ~:).Nice idiots are the best company one can have. Keep up the good work!
Related Categories
-
PhoneGap Build
- 15111 Conversations
- 275 Followers

