Use Array(data) instead of Data.bytes for CryptoSwift 1.9+ compatibility#79
Merged
Merged
Conversation
CryptoSwift 1.9.0 removed its `Data.bytes -> [UInt8]` extension (renamed to `byteArray`). On the Xcode 26 SDK, `data.bytes` then resolves to Foundation's new native `Data.bytes`, which returns a `RawSpan` - breaking every crypto call site with errors like: Cannot convert value of type 'RawSpan' to expected argument type 'Array<UInt8>' Value of type 'RawSpan' has no member 'toHexString' Builds pinned to CryptoSwift <= 1.8.5 are unaffected, so this only bites users whose package resolution floats up to 1.9.0/1.10.0 (e.g. after 'Update to Latest Package Versions'). Replace `<data>.bytes` with `Array(<data>)`, which yields the same [UInt8] and compiles against every CryptoSwift version (and doesn't depend on CryptoSwift at all). Verified building OmnipodKit against CryptoSwift 1.10.0 on Xcode 26.5.
Contributor
Author
Test✅ Successful test Reproduce the issue, then Demonstrate the fixReproduce the issue reported from iAPS when they modified the CryptoSwift minimum Version from 1.4.1 to 1.10.0 in OmnipodKit.xcodeproj/project.pbxproj MethodBuild Loop main branch with no changes to any submodules
Modify OmnipodKit.xcodeproj/project.pbxproj to change the minimumVersion with no other changes
Change to fix/cryptoswift-1.9-rawspan_wrt_main branch while leaving the minimumVersion at 1.10.0
Reset the change to OmnipodKit.xcodeproj/project.pbxproj to restore the minimumVersion to 1.4.1
|
marionbarker
added a commit
that referenced
this pull request
Jun 13, 2026
Use Array(data) instead of Data.bytes to support newer CryptoSwift (#79)
This file contains hidden or 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
3 participants
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.
This PR cherry-picks the commit from PR #78 which is applied to the loop-next-dev branch so the fix is available for the main branch. The rest of the description comes from the cherry-pick.
CryptoSwift 1.9.0 removed its
Data.bytes -> [UInt8]extension (renamed tobyteArray). On the Xcode 26 SDK,data.bytesthen resolves to Foundation's new nativeData.bytes, which returns aRawSpan- breaking every crypto call site with errors like:Cannot convert value of type 'RawSpan' to expected argument type 'Array'
Value of type 'RawSpan' has no member 'toHexString'
Builds pinned to CryptoSwift <= 1.8.5 are unaffected, so this only bites users whose package resolution floats up to 1.9.0/1.10.0 (e.g. after 'Update to Latest Package Versions').
Replace
<data>.byteswithArray(<data>), which yields the same [UInt8] and compiles against every CryptoSwift version (and doesn't depend on CryptoSwift at all). Verified building OmnipodKit against CryptoSwift 1.10.0 on Xcode 26.5.