Repository navigation
SPM binary target checksum mismatch in 5.2.16 (and 5.2.15) #1633
Description
Description
When resolving Swift Package Manager dependencies for version 5.2.16 (and 5.2.15), the checksums of the downloaded binary targets don't match the checksums specified in Package.swift.
Error Message
checksum of downloaded artifact of binary target 'OneSignalLocation' (efa24b15c8e321aa2768853ce90406af257aded6d87b54461a183aac2592cf36) does not match checksum specified by the manifest (bc5a812dc5b55880570867aeae54e93c686108b45ade0275e5fca03b755741cf)
This affects all binary targets in the package.
Expected vs Actual Checksums
| Binary Target | Package.swift Checksum | Actual Download Checksum |
|---|---|---|
| OneSignalLocation | bc5a812d... | efa24b15... |
| OneSignalFramework | 0b40df3b... | 07405de4... |
| (all other targets similarly affected) |
Steps to Reproduce
- Add OneSignal-iOS-SDK as SPM dependency
- Specify version 5.2.15 or 5.2.16
- Run
xcodebuild -resolvePackageDependencies
Impact
All iOS projects using OneSignal via SPM cannot build.
Suggested Fix
The checksums in Package.swift need to be updated to match the actual binaries on GitHub Releases.
Activity
ignaciojuarez commentedon Jan 12, 2026
same error here. havent found a solution. Cannot build app
ignaciojuarez commentedon Jan 13, 2026
downgrading and cleaning cmd+k and cache still gave me errors. This fixed it:
The Problem:
Xcode's SPM cache got into a corrupted/inconsistent state. Even after you "Reset Package Caches" in the UI, Xcode was still holding onto bad state internally. The GUI kept failing before it could even attempt to download packages.
The Fix:
- ~/Library/Caches/org.swift.swiftpm
- ~/Library/org.swift.swiftpm
- ~/Library/Developer/Xcode/DerivedData/Pretzel-*
- Package.resolved file
About versions:
nan-li commentedon Jan 17, 2026
Hi all, thanks for reporting. I did find a checksum issue on 5.2.16 that is now fixed. Please try it again, and let me know if it is still not working.
However, I did not find an issue with 5.2.15. The Package.swift checksums match the assets attached to Release 5.2.15. Can you share the exact errors for 5.2.15?
Alternatively, you can add the SDK via SPM using the https://github.com/OneSignal/OneSignal-XCFramework repository instead of https://github.com/OneSignal/OneSignal-iOS-SDK. This is also a correct way to add the SDK.
nan-li commentedon Feb 5, 2026
Hi all, haven't heard back from my last response, it may be resolved. We have also released new versions since.