-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode Cloud support for version 2.0.0+ #187
Comments
Hi @AlfredReisner I'm setting up my own Xcode Cloud environment on a development branch to help triage this issue. Was Xcode Cloud previously working correctly with earlier versions of Xcode or Mapbox SDKs? Can you share your minimum OS version for your project? |
Hi, v2.0.0+ still works when we build the pipeline on Xcode 15.2. Only Xcode 15.3+ drops this configuration error. |
@AlfredReisner I have a draft pull request available which will update MapboxCoreSearch.framework at #196. This version of MapboxCoreSearch is built using Xcode 15.3. If you wouldn't mind, please try building your app with the MapboxSearch package fetching from branch |
@aokj4ck Unfortunately the pipeline drops the same configuration error using the mentioned branch. Maybe to clarify a bit more again. We can build the framework using Xcode 15.3 locally. It is just Xcode Cloud which drops the error and prevents us to build the project. As a workaround for now we stay on Xcode 15.2 with 2.0.0-rc.2 set as dependency but it would be great to get this fixed in future releases. |
@AlfredReisner and to confirm are you using SPM for your |
@aokj4ck Yes, that is correct. |
@AlfredReisner please update to our latest release v2.0.3 and let me know if you encounter any issues. https://github.com/mapbox/mapbox-search-ios/releases/tag/v2.0.3 |
@aokj4ck v2.0.3 solves the issue. |
Hello Mapbox Search team,
we are using Xcode Cloud as internal CI pipeline to build the mapbox-search-ios framework 2.0.0-rc.2 setup with SPM.
When building with Xcode 15.3+ we are receiving the follow configuration error:
Could u please have a look to fix the configuration for us?
If u need any additional information, please reach out to us.
Thanks.
The text was updated successfully, but these errors were encountered: