Closed razorsyntax closed 4 years ago
Are you targeting the version number that is live on playstore? And the version name should ideally use semver major.minor.patch 9.0.0
Here's what it looks like on the dev console:
I'm testing with semver at the moment by pushing a new semver up to the store to see what happens. Will appsync work even if it has a versionName
as something like 9.0
?
@razorsyntax AppSync looks at the version in your App_Resources/Android/path/AndroidManifest.xml file. So if you don't pass the --targetBinaryVersion <version to patch>
flag it will target the one in the manifest (for Android). More in the README.
Thanks guys. I'm assuming my versioning is weird and will concentrate my efforts there. Thanks for all your help!
The code is live in the play store.
What's odd is that if I install the same apk to the emulator on the local dev environment that also gets pushed live, the emulator gets the updates and the devices with the same code from the play store do not.
I feel like I'm missing something somewhere but I'm not sure of the issue.
I thought maybe my versioning scheme for
android:versionName
could be the issue so I changed it from9
to9.0
as you can see in the manifest below.The deployment history shows that the code is being pushed somewhere but no active installs.
Android Manifest:
main.ts
Custom App Sync Service