FliplineStudios had assumed we'd just upload a 32-bit APK and a 64-bit APK (similar to how we upload separate x86 APKs),
see Assigning version codes
see https://forum.starling-framework.org/d/15841-how-to-set-androidversioncode/2
On Android, the AIR versionNumber is translated to the Android integer versionCode using the formula: a1000000 + b1000 + c, where a, b, and c are the components of the AIR version number: a.b.c.
and then see Version your app
versionCode
— A positive integer used as an internal version number.
and
Warning: The greatest value Google Play allows for versionCode is 2100000000.
<br/>
if your version is 1.2.3
then the versionCode
will be 1*1000000 + 2*1000 + 3
or 1002003
in Adobe AIR, the app XML
<versionNumber>1.2.3<versionNumber>
then in the AndroidManifest.xml
<manifest android:versionCode="1002003" android:versionName="1.2.3"
android:installLocation="auto" package="air.com.foobar.myapp"
xmlns:android="http://schemas.android.com/apk/res/android">
so you got about 3 ranks to play with
eg.
2100000000
1002003
0001002003
so you need to unpack the APK, and modify the AndroidManifest.xml
so the android:versionCode="1002003"
is updated to
foobar 32-bit APK using version 1.2.3
for API level 4
then android:versionCode="0401002003"
foobar 64-bit APK using version 1.2.3
for API level 11
then android:versionCode="1101002003"
and then repack the APK etc.
OR if you want to avoid the unpack/pack little dance
reserve/cheat a digit in your version number
eg. 1.2.3
for 32-bit and 11.2.3
for 64-bit