refactor: route identifier reads through OneSignalIdentifiers #1667
Claude / Claude Code Review
completed
May 30, 2026 in 18m 48s
Code review found 1 important issue
Found 2 candidates, confirmed 1. See review comments for details.
Details
| Severity | Count |
|---|---|
| 🔴 Important | 1 |
| 🟡 Nit | 0 |
| 🟣 Pre-existing | 0 |
| Severity | File:Line | Issue |
|---|---|---|
| 🔴 Important | iOS_SDK/OneSignalSDK/OneSignal.xcodeproj/project.pbxproj:1982-1985 |
Missing OneSignalOSCore dep in podspecs/Package.swift |
Annotations
Check failure on line 1985 in iOS_SDK/OneSignalSDK/OneSignal.xcodeproj/project.pbxproj
claude / Claude Code Review
Missing OneSignalOSCore dep in podspecs/Package.swift
This PR adds `OneSignalOSCore.framework` to the link phase of the OneSignalExtension and OneSignalNotifications targets (pbxproj lines 1985, 2070) and the implementations now reference `OneSignalIdentifiers` from those binaries, but none of the package manifests declare the new dependency. Customers using the standard NSE integration (CocoaPods `OneSignalXCFramework/OneSignalExtension` or SPM `OneSignalExtension` product) will not get OneSignalOSCore.framework embedded into their NSE target, so
Loading