// the find
OneSignal/OneSignal-iOS-SDK
OneSignal makes engaging customers simple and is the fastest, most reliable service to send push notifications, in-app messages, SMS, and emails. This plugin makes it easy to integrate your native iOS app with OneSignal. https://onesignal.com
The official client SDK for integrating OneSignal's push/SMS/email/in-app messaging service into iOS apps. It's for teams who already use OneSignal as their notification backend and need the native-side wiring — not a general-purpose notifications library you'd use standalone.
Installation support is genuinely wide: SPM, CocoaPods, Carthage, and XCFramework, covering iOS 15 through 26 for both Swift and Objective-C. CI is taken seriously — separate ci.yml, e2e.yml, and codeql.yml workflows plus automated release-PR and publish pipelines, not just a single smoke-test action. The bundled demo app is unusually complete, exercising nearly every feature surface (live activities, in-app messages, outcomes, SMS, tags, triggers) rather than the usual one-screen hello-world most SDK demos ship with.
The README is a stub that just links out to the hosted docs site — there's no inline code sample, so you can't tell what the API actually looks like without leaving GitHub. The repo is full of 'Wrapper' targets (OneSignalExtensionWrapper, OneSignalFrameworkWrapper, etc.) that are just dummy.m/dummy.h shims around a precompiled XCFramework, so a chunk of the real implementation isn't inspectable from source here. It references OneSignal-KMP-SDK as a submodule, meaning core logic is migrating into a separate Kotlin Multiplatform repo you'd need to cross-reference to understand the full picture. And fundamentally this only gets you as far as OneSignal's proprietary backend — the SDK being open source doesn't make the service itself open or self-hostable.