Google play don't let me update my app

Question

I already made a huge search and don't know why Google Play are not letting me update my Prod app. Their error message does not make too much sense for me, actually I don't understand for real why they are not accepting it.

This is the error message:

This configuration cannot be published for the following reason(s):
It is forbidden to downgrade devices which previously used M permissions (target SDK 23 and above) to APKs which use old style permissions (target SDK 22 and below). This occurs in the change from version 178 (target SDK 23) to version 2008 (target SDK 22).
It is forbidden to downgrade devices which previously used M permissions (target SDK 23 and above) to APKs which use old style permissions (target SDK 22 and below). This occurs in the change from version 178 (target SDK 23) to version 2008 (target SDK 22).
It is forbidden to downgrade devices which previously used M permissions (target SDK 23 and above) to APKs which use old style permissions (target SDK 22 and below). This occurs in the change from version 178 (target SDK 23) to version 2008 (target SDK 22).
It is forbidden to downgrade devices which previously used M permissions (target SDK 23 and above) to APKs which use old style permissions (target SDK 22 and below). This occurs in the change from version 178 (target SDK 23) to version 2008 (target SDK 22).

And here is a print of it:

The first build 0.1 was made using build.phonegap.com and the second one (0.2) was released locally using CLI because the results are better.

Anyone has some clue about that?

Thanks for reading.

Answer 1

Late to the game but I have been seeing this a lot with Xamarin clients recently.

In addition to Andreas's excellent point, another possibility for those using Xamarin is that you might previously have set an explicit build target of 23 or higher but then reverted to Automatic.

Xamarin places < uses-sdk /> in the manifest when using Automatic which when replacing an APK that used an explicit target gives an error message as above but complaining of a change to target SDK 0. This happens even if the Automatic target is equal or higher than the existing SDK.

To solve this set an explicit target of 23 or higher