Identify the app
Bundle ID identifies an app, for example com.example.reader. CFBundleShortVersionString is the release version; CFBundleVersion is the build number. Apple associates uploads using package metadata. Inspect build settings and the exported IPA, not a filename such as reader-final.ipa. Do not casually change an existing app’s Bundle ID for a normal update.
Fix a build within the same version
Suppose version 1.2.0 already has build 18 uploaded. A corrected package for that release can use build 19 while keeping 1.2.0. Set values before building, archiving and exporting, then verify them in App Store Connect. Renaming app18.ipa to app19.ipa changes no package metadata. Do not patch a signed package to change its version.
Prepare a new release
For release 1.3.0, align project settings with the intended platform and version record in App Store Connect. Platforms such as iOS and macOS can have different release schedules, so include the platform in your records. Agree on a team numbering convention to prevent different operators from reusing build numbers.
Investigate duplicate-build errors
Compare the error, package metadata, previous builds and CI logs. Give the developer the Bundle ID, platform, version, build number, upload time and original error. Rebuild after establishing the cause rather than switching upload tools repeatedly. EasyIPA uploads an existing IPA; versioning and signing belong to the package-generation workflow.