fix: resolve Apple submission errors - version 1.1.1 build 28

[graycreate]

Summary

• Updated build number from 4 to 28 (higher than existing build 27 on App Store)
• Added automatic build number increment in Fastlane to prevent future conflicts
• Ensures version 1.1.1 is higher than the closed 1.1.0 train

Problem

Apple rejected the submission with two errors:

1. ITMS-90186: Version 1.1.0 train is closed for new builds
2. ITMS-90062: Version must be higher than previously approved 1.1.0

Root Cause

The build was using version 1.1.0 with build 27, but:

• Version 1.1.0 is already closed on App Store Connect
• Build number 27 already exists for version 1.1.0
• Our project had version 1.1.1 but with build number 4 (too low)

Solution

1. Set build number to 28 (higher than existing 27)
2. Keep version at 1.1.1 (higher than 1.1.0)
3. Add automatic build increment in Fastlane using latest_testflight_build_number
4. This ensures each TestFlight upload gets a unique, incrementing build number

Testing

After merging, the release pipeline will:

• Use version 1.1.1 build 28
• Auto-increment for future builds
• Successfully upload to TestFlight

🤖 Generated with Claude Code

[Copilot]

Pull Request Overview

This PR fixes Apple App Store submission errors by updating the build number from 4 to 28 and implementing automatic build number incrementation in Fastlane to prevent future conflicts with existing builds on App Store Connect.

• Updated build number to 28 to exceed the existing build 27 for version 1.1.0
• Added automatic build number increment logic in Fastlane using latest_testflight_build_number
• Ensures version 1.1.1 build 28 can be successfully submitted to TestFlight

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
fastlane/Fastfile	Added automatic build number increment to prevent future submission conflicts
V2er.xcodeproj/project.pbxproj	Updated CURRENT_PROJECT_VERSION from 4 to 28 for both Debug and Release configurations

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The latest_testflight_build_number function can return nil if no builds exist in TestFlight, which would cause a runtime error when adding 1. Consider using the || 0 operator to handle this case: (latest_testflight_build_number(api_key: api_key) || 0) + 1

Suggested change

	build_number: latest_testflight_build_number(api_key: api_key) + 1
	build_number: (latest_testflight_build_number(api_key: api_key) || 0) + 1

[github-actions]

Code Coverage Report ❌

Current coverage: 0%