Skip to content

iOS 5.5.2: anonymous user / push subscription never created — OSRequestCreateUser never fires (works in 5.5.1) #1671

@swirkes

Description

@swirkes

What happened?

On a clean install with OneSignal iOS SDK 5.5.2, the SDK fetches ios_params (HTTP 200) and the device registers with APNs (a device token is received), but OSRequestCreateUser is never sent — no anonymous user or push subscription is ever created. The device never appears under Audience → Subscriptions in the dashboard, so it can't be sent a notification.

This is deterministic: it reproduces across networks (WiFi and cellular), and across repeated delete-and-reinstall cycles. The only OneSignal API call ever made is OSRequestGetIosParams; no user/subscription request follows the APNs token.

Pinning the SDK to exactly 5.5.1 fixes it — the same app, same code, same device immediately creates the subscription and appears in the dashboard. So this is a regression introduced in 5.5.2 (which, per the changelog, refactored identifier handling: "route identifier reads through OneSignalIdentifiers" #1667 and "Preserve user identity across iOS prewarm launches" #1669).

Steps to reproduce?

  1. SwiftUI app (no AppDelegate; SwiftUI provides the synthetic one). Add the SDK via SPM (OneSignalFramework only), version 5.5.2.
  2. Call OneSignal.initialize("<APP_ID>", withLaunchOptions: nil) in the @main App's init().
  3. Call OneSignal.Notifications.requestPermission(nil, fallbackToSettings: true) (from a view's onAppear), and tap Allow.
  4. Run on a physical device (clean install). Leave the app foregrounded ~30–60s.
  5. Observe: APNs token is received (Device Registered with Apple: …), OSRequestGetIosParams returns 200, updateNotificationTypes called: 15 — but no OSRequestCreateUser is ever logged, and the dashboard shows zero subscriptions.
  6. Change the SPM dependency to Exact Version 5.5.1, clean, delete the app, rebuild. The subscription is now created and appears in the dashboard. No other change.

What did you expect to happen?

After initialize + permission granted + APNs token received, the SDK should create an anonymous user and push subscription (OSRequestCreateUser) and the device should appear under Audience → Subscriptions — exactly as it does on 5.5.1.

OneSignal iOS SDK version

Broken: Release 5.5.2. Works: Release 5.5.1.

iOS version

iOS 26

Specific iOS version

iOS 26.5

Relevant log output

VERBOSE: setAppId called with appId: <APP_ID>!
VERBOSE: launchOptions is set and appId of <APP_ID> is set, initializing OneSignal...
container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled
VERBOSE: Firing registerForRemoteNotifications
DEBUG: Downloading iOS parameters for this application
VERBOSE: requestPermission Called
Metadata file not found, starting fresh
VERBOSE: OneSignal.startNewSessionInternal
VERBOSE: network request (OSRequestGetIosParams) with URL https://api.onesignal.com/apps/<APP_ID>/ios_params.js and headers: (null)
VERBOSE: network response (OSRequestGetIosParams) ...: httpStatusCode = 200
VERBOSE: oneSignalDidRegisterForRemoteNotifications:deviceToken:
INFO: Device Registered with Apple: <DEVICE_TOKEN>
VERBOSE: updateNotificationTypes called: 15
VERBOSE: startedRegister: 1
VERBOSE: OneSignal.startNewSessionInternal
DEBUG: Application Active started
-- ~38 seconds elapse (timeSinceInitialization: 38.3), app stays foregrounded --
-- NO OSRequestCreateUser (or any create-user / create-subscription request) is ever logged --
-- Audience -> Subscriptions stays empty --

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions