Fix ci build dependencies (#91)

* Test: Add comment to verify CI checks pass

Small change to test that existing CI workflow works correctly
without any linting modifications.

* Fix CI build by resolving package dependencies

- Add -resolvePackageDependencies step before build
- Fixes missing AWSConnectParticipant-Target.o error

* Fix: Use stable Xcode 15.4 instead of beta

The latest Xcode (26 beta) was causing build issues with
AWSConnectParticipant-Target.o. Using stable 15.4 version.

* Remove unnecessary dependency resolution step

The Xcode version fix should be sufficient, no need for
manual dependency resolution.

* Use latest stable Xcode version 16.4.0

Updated from 15.4 to 16.4.0 which is the latest stable (GM) version
available on GitHub Actions runners.

* Add optional latest Xcode compatibility test

- Added test-latest-xcode job that tests with latest Xcode version
- Uses continue-on-error: true so it won't block the main build
- Helps identify compatibility issues with newer Xcode versions

* Make latest Xcode test non-blocking for PRs

- Only runs on main branch pushes, not on PRs
- This way it won't show as a failed check that blocks PR merging
- Still provides feedback on Xcode compatibility after merge

* Create separate Xcode compatibility workflow

- Moved latest Xcode test to separate workflow file
- This creates a separate check that can be ignored for PR merging
- Main build workflow remains required, compatibility test is optional

* Update job names to indicate optional status

- Workflow name: 'Xcode Compatibility Test (Optional)'
- Job name: 'test-latest-xcode-optional'
- Step name includes '(Optional)'
- Makes it clear this check doesn't need to pass for merging

* Make it crystal clear PR can merge even if check fails

- Workflow: 'Xcode Compatibility (Can Fail - PR Can Still Merge)'
- Job: 'test-latest-xcode-can-fail'
- Step: 'Failure OK - PR Can Still Merge'
- Removes any confusion about merge requirements

* Fix simulator compatibility with Xcode 16.1.0

- Use Xcode 16.1.0 (stable GM version from the table)
- Use iOS 18.0 simulator which should be available in Xcode 16.1
- This should resolve the device matching error

* Use Xcode 16.4.0 and remove optional compatibility check

- Back to Xcode 16.4.0 (latest stable)
- Removed separate xcode-compatibility.yml workflow
- Simplified to single required build check

* Use iPhone 16 with iOS 18.4 simulator

Based on available simulators list, iPhone 16 with iOS 18.4
is available and closest to the original iPhone 15 setup.

* Add print() statement linting check

- Added minimal linting step at end of workflow
- Checks for print() statements in Swift files
- Fails build if any print() statements are found

Author: xiajon

.github/workflows/Build.yml

@@ -19,7 +19,7 @@ jobs:
     - name: Set up Xcode
       uses: maxim-lobanov/setup-xcode@v1
       with:
-        xcode-version: 'latest'
+        xcode-version: '16.4.0'
 
     - name: Set up Ruby
       uses: ruby/setup-ruby@v1
@@ -47,8 +47,8 @@ jobs:
         echo "Available schemes:"
         xcodebuild -list -project AmazonConnectChatIOS.xcodeproj
         
-        # Use iPhone 15 with iOS 17.5
-        DESTINATION="platform=iOS Simulator,OS=17.5,name=iPhone 15"
+        # Use iPhone 16 with iOS 18.4 (available in Xcode 16.4)
+        DESTINATION="platform=iOS Simulator,OS=18.4,name=iPhone 16"
         
         # Run tests with AmazonConnectChatIOSTests scheme
         echo "Running tests with AmazonConnectChatIOSTests scheme..."
@@ -72,3 +72,12 @@ jobs:
           echo "✅ All tests passed"
         fi
         echo "::endgroup::"
+
+    - name: Check for print() statements
+      run: |
+        if grep -r "print(" --include="*.swift" . --exclude-dir=".git"; then
+          echo "❌ ERROR: Found print() statements in Swift files"
+          exit 1
+        else
+          echo "✅ No print() statements found"
+        fi