Auto-incrementing build numbers has suddenly stopped working

chiverton · March 2, 2022, 4:39pm

Our uplaods to iOS are being rejected saying we’re reusing build numbers

We followed Auto-incrementing Build Numbers in Capacitor - Appflow weeks ago and it’s all been working fine, but now are builds are all being rejected saying the number has reset to 1

Odd, as our default value is 2 anyway.

Build log extract :

[16:38:27]: Appflow build script detected...
[16:38:27]: $ npm run appflow:build
[16:38:28]: ▸ >x@0.0.1 appflow:build /Users/ionic/builds/tomchiverton/x
[16:38:28]: ▸ > npx cap-config run appflow.yml -y && npm run build
[16:38:30]: ▸ run ios buildNumber 89
[16:38:30]: ▸ run android versionCode 89
....
[16:42:46]: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:
[16:42:46]: [iTMSTransporter] 	/var/folders/t9/cpm_8j855m5b8jdwdwjcjsp40000gn/T/d20220302-491-tol6n7/1608875982-63f46b64-145d-45a9-9125-ac6c0388d6cb.itmsp - Error Messages:
[16:42:46]: [iTMSTransporter] 		ERROR ITMS-90189: "Redundant Binary Upload. You've already uploaded a build with build number '1' for version number '1.0'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4)."
[16:42:46]: [iTMSTransporter] [2022-03-02 16:42:46 GMT] <main> DBG-X: Returning 1
[16:42:46]: iTunes Transporter output above ^
[16:42:46]: ERROR ITMS-90189: "Redundant Binary Upload. You've already uploaded a build with build number '1' for version number '1.0'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4)."

Our appflow.yml, package.json haven’t changed

Any one else before I raise a support ticket ?

mhartington · March 2, 2022, 5:03pm

Raise a support ticket. If you’re a paying customer for appflow, that should be your first place to go to for things like this

chiverton · March 2, 2022, 5:09pm

Oh, OK, cool, I agree

Done.

chiverton · March 3, 2022, 12:50pm

Reverting to an older @capacitor/configure package has sorted it.

github.com/ionic-team/capacitor-configure

Bug: Update breaks yaml tool

opened 03:03PM - 02 Mar 22 UTC

sanderschnydrig

Hi Max We've been using this great tool for a while for white labeling but si…nce the most recent update the yaml configuration is broken. I suppose it might have to do with the capacitor.config.ts being taken into consideration, so I posted it down below for reference. For the meantime I solved it by using the previous version like this (**@1.0.31**) ```shell npm_config_yes=true npx dotenv-cli -- npx @capacitor/configure@1.0.31 run configuration/capacitor.yaml -y ``` For example my ios entitlements are not being updated: ```yaml entitlements: - com.apple.developer.associated-domains: [ 'applinks:$BASE_URL' ] ``` `capacitor.config.ts`: ```typescript import { CapacitorConfig } from "@capacitor/cli" const config: CapacitorConfig = { appId: `ch.example.app`, appName: `exampleApp`, webDir: `dist/app`, bundledWebRuntime: false, ios: { contentInset: `never`, }, plugins: { SplashScreen: { launchAutoHide: false, androidScaleType: `CENTER_CROP`, }, }, server: { // hostname: 'ch.example.app', // this property will fix the ad displaying of audienzz on android }, loggingBehavior: `production`, // 'none' | 'debug' | 'production' } export default config ```

It doesn’t help that the releases reported on GitHub - ionic-team/capacitor-configure: Manage Capacitor projects through code or configuration differ from those on https://www.npmjs.com/package/@capacitor/configure and I can’t find a changelog to try and spot the change.