Xamarin Google play publish

2019-09-05 17:32发布

In recent update Xamarin made it possible to publish android apps straight to the Google play (before you had to generate apk and upload it manually). More info

enter image description here

These are my version numbers. I was at version 10437 when the update came, I made some changes and raised version number to 10438 and tried the new way of publishing. What happened is that my version number became 141510 for some reason and when I tried to do it again it became 207046. After that I set the number to 320000 and started uploading manully again.

I suspect that the reason for this is that I had Multiple supported architectures and xamarin was uploading multiple apks and I was getting some errors about that. Since then I changed supported architectures to armeabi-v7a only.

Question is:

Can I somehow tell google to forget about these screwed up numbers so I can continue with my 10438 (it won't let me now, I get an error that version number must be bigger then the last one)? Also all versions after 10437 are private and this is the current version on beta (image is from beta channel).

Also do I lose mobile devices if I set my supported architecture as armeabi-v7a only?

1条回答
来,给爷笑一个
2楼-- · 2019-09-05 18:02

versionCode vs. versionName:

The versionCode is not shown to the user:

An integer used as an internal version number. This number is used only to determine whether one version is more recent than another, with higher numbers indicating more recent versions. This is not the version number shown to users

Ref: https://developer.android.com/studio/publish/versioning.html

ABI Architecture:

Google does not breakdown the CPU Information/ABI Architectures in a Dashboard like they do for API level or screen resolution. You can get a device breakdown for your app install:

Ref: https://developer.android.com/distribute/googleplay/developer-console.html#app-stats

Assuming your app is not dependent on a 3rd-party NDK library that only supports a subset of all the ABIs, there is no general reason not to support multi-ABIs as you are just pre-limiting your applications available user-based.

Current API and Screen Sizes and Densities Distributions:

Ref: https://developer.android.com/about/dashboards/index.html

查看更多
登录 后发表回答