I make an application to the customer.

He provided me with a project, I modified it, from 1st to 5th version versionCode increased and sent to the client, from 1st to 5th apk the client himself poured for publication in the market.

We live with a client in different cities.

Today, the client told me to pour the new apk on beta into the market myself, it turned out that versionCode from 5 (working and uploaded) immediately went up to 8th (beta) of apk, added 1 permission to access the camera and I included proGuard on the project files when compiling (on the 5th version there was no obfuscation).

When loading, I did not write anything in the "what's new" field. The application has a rating of 2.7 in the market (as it is with a bunch of bugs, but I fix it).

After processing the apk google play site gave the following message: screenshot

Began to understand, Google has updated the "Center for Developing Rules - Malicious Behavior"

(link to the center of the rules) in May 2017.

There is nothing sensible found.

The article on Habré in general scared that now I’m afraid to do something extra, because the client is paying, and the application has 8,000 downloads.

A big request to those who came across - help advice.

For the first year I see this behavior of Google

  • Recently in the news they wrote that Google is changing the policy for applications on Google Play. To remove all trash and spam. - Vanyamba Electronics
  • @VanyambaElectronics turns out, the application has 8k downloads and a 2.7 rating rises, added a camera resolution and am I doomed?) Offensively somehow - zayn1991
  • Try to sell your project company Alphabet. - Vanyamba Electronics

1 answer 1

I received a message of this kind in the mail:

Hello Google Play Developer,

We rejected Hoff, with package name ru.hoff.app, for violating our Malicious Behavior or User Data policy. If you submitted an update, it’s still available on Google Play.

It makes it possible to use the app.

Below is your list of issues. Please upgrade your app (s) as soon as possible.

Vulnerability APK Version (s) SSL Error Handler alerts, see this Google Help Center article.

If you’re not happy, you’ll have to keep track of your app.

It’s possible that it’s not a problem. If you really want to know about security issues, even if you’re aware of your issues.

Apps and Policies.

Please support our team support team.

Best,

The google play team

Description of how to fix this problem: https://support.google.com/faqs/answer/7071387?hl=en

A question on the forum with this error: https://stackoverflow.com/search?q=SsErrorHandler

Method documentation: https://developer.android.com/reference/android/webkit/WebViewClient.html#onReceivedSslError(android.webkit.WebView, android.webkit.SslErrorHandler, android.net.http.SslError)

An example of solving a problem: https://stackoverflow.com/questions/36050741/webview-avoid-security-alert-from-google-play-upon-implementation-of-onreceiveds

In general, the replacement of this code helped me:

@Override public void onReceivedSslError(WebView view, SslErrorHandler handler, SslError error) { handler.proceed(); }

on this code:

  @Override public void onReceivedSslError(WebView view, final SslErrorHandler handler, SslError error) { final AlertDialog.Builder builder = new AlertDialog.Builder(this); builder.setMessage(R.string.notification_error_ssl_cert_invalid); builder.setPositiveButton("continue", new DialogInterface.OnClickListener() { @Override public void onClick(DialogInterface dialog, int which) { handler.proceed(); } }); builder.setNegativeButton("cancel", new DialogInterface.OnClickListener() { @Override public void onClick(DialogInterface dialog, int which) { handler.cancel(); } }); final AlertDialog dialog = builder.create(); dialog.show(); }

This method must be replaced in the newly created WebViewClient, which we must assign to our webView.

The error itself appeared when I replaced http:// with https:// in my project for webView addresses.