OneSignal user id comes back null: the idsAvailable API is deprecated

TL;DR

Use the subscription-state call from the SDK version you actually ship, and log the id once at startup to confirm you have a real value before keying any transactional push off it.

Steps

1. When you need the OneSignal user id on device, do not copy the idsAvailable snippet from old answers: it is deprecated and later SDKs removed it. Use the subscription-state call from the SDK version you actually ship, and log the id once at startup to confirm you have a real value before keying any transactional push off it. If the id comes back null on a current SDK, you are calling the old API, not facing a registration failure.

When to use

You are seeing this: If the id comes back null on a current SDK, you are calling the old API, not facing a registration failure. Use this skill when you run into "OneSignal user id comes back null: the idsAvailable API is deprecated".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #36369910 (accepted answer, score 57): A developer needed the OneSignal user id (player id) on mobile to send a transactional push, and the accepted answer shows the idsAvailable callback. The same answer carries an explicit deprecation notice: idsAvailable was replaced, with the newer call being getPermissionSubscriptionState().getSubscriptionStatus().getUserId(). Copying the old snippet into a current SDK silently yields nothing.

Verified resolution: When you need the OneSignal user id on device, do not copy the idsAvailable snippet from old answers: it is deprecated and later SDKs removed it. Use the subscription-state call from the SDK version you actually ship, and log the id once at startup to confirm you have a real value before keying any transactional push off it. If the id comes back null on a current SDK, you are calling the old API, not facing a registration failure.

Source URL: https://stackoverflow.com/questions/36369910