update Package.swift #9
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#8
The library was recently updated to include several binary products, yet the Package.swift file still declares only a single binary product, resulting in dependency integration issues. The following binary products are currently included in the library update:
Dynamic+IDM+Diagnosis/SensorsFocus.xcframework
Dynamic+IDM/SensorsFocus.xcframework
Dynamic/SensorsFocus.xcframework
DynamicDiagnosis/SensorsFocus.xcframework
Static+IDM+Diagnosis/SensorsFocus.xcframework
Static+IDM/SensorsFocus.xcframework
Static/SensorsFocus.xcframework
StaticDiagnosis/SensorsFocus.xcframework
Proposed Solution:
To resolve this issue, update the Package.swift file to include declarations for all the newly introduced binary products, ensuring they can be correctly located and utilized when adding the package as a dependency. This will allow seamless integration and access to all available binaries within the library.