Trouble Integrating Objective-C Framework with CI/CD for Automated Testing
I'm stuck on something that should probably be simple... This might be a silly question, but Setting up a CI/CD pipeline for a new feature in our Objective-C application has presented some unexpected challenges. We're utilizing Jenkins for our builds and Xcode 14 for the project, aiming for a seamless integration process. One major roadblock occurs when trying to execute our unit tests automatically; the tests run fine locally but fail during the CI build. The output shows: ``` error: 'MyFramework/MyFramework.h' file not found ``` This seems to suggest that the framework isn't being correctly linked in the CI environment. I've double-checked that the framework is included in the Build Phases under 'Link Binary With Libraries', yet, the issue persists. To troubleshoot, I've looked into the header search paths and ensured they are set to `$(inherited)` in the build settings. I also tried `#import <MyFramework/MyFramework.h>` instead of a relative import, but this hasn't resolved anything. Additionally, I've confirmed that the configuration for the CI environment matches the one set in my local development setup, but I suspect that there might be discrepancies in how dependencies are being managed. We are using CocoaPods for dependency management, and the Podfile is configured correctly to include my framework. Still, I'm not sure if it's the right approach for this situation. I would appreciate any insights or best practices to ensure that our CI/CD pipeline correctly builds and tests the Objective-C project with the integrated framework. Are there any specific settings or configurations that I might be overlooking, or common pitfalls in CI setups for Objective-C frameworks? My development environment is Linux. Any ideas what could be causing this? For context: I'm using Objective-C on macOS.