[question]: Aliases, IncludeExternalUserIds as deprecated.

[pmikoda]

How can we help?

Previously I was using IncludeExternalUserIds to send notification to the certain external user/s, but from the newest version, this Datamember is marked as deprecated.

When I'm trying to use aliases I have some problems with it. I'm not sure how to create them (is it available on the FE side like it was for setting up of externalUserIds?)

Also in documentation there is a mention about visibility of aliases in OneSignal Dashboard but I can't find these.

My actual code looks like this:

and I don't know what should I pass to aliasLabel <- and where to create this if I want the same label for all users but send notifications by their externalId.

Code of Conduct

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

[emawby]

@pmikoda Good questions the aliases function similarly to external user id, expect they are a key value pair where you supply both the key and value instead of just the value. This allows you to have multiple external ids if you for example you integrated with facebook and google, and wanted to represent those different ids separately.

To get the same behavior as external_user_id use the "external_id" alias label. To add an alias you can use IdentifyUserByAlias.

[mjasikowski]

@emawby The type of parameter that PlayerNotificationTargetIncludeAliases accepts is incorrect. It requires a List<string>, while it should really require Dictionary<string, List<string>, where the key for that dictionary should be the alias label (i.e. external_id), the value being a list of actual IDs.

Currently it generates the following JSON payload:

{ 
   "include_aliases": {
      "alias_label": ["values"]
   }
}

The alias_label property here cannot be renamed. This is actually the case for the SDK in other languages as well.
At the moment the IncludeAliases property is unusable due that problem.

[ante-maric]

I just bumped into this too :(

[emawby]

@yasikovsky Thank you for pointing this out we will address!

[temcewen]

@emawby
This is a severe issue. I suppose we should just continue using "IncludeExternalUserIds" until it's fixed, correct?

[temcewen]

Any updates on this?

[nan-li]

This is a bug we are fixing. In the meantime, it is safe to continue using IncludeExternalUserIds @temcewen

[grantvine-sc]

Has this since been resolved ?

[nan-li]

This fix has not yet been released. We are working on an overhaul of this library's API and Interfaces.
In the meantime, you can use IncludePlayerIds to target by subscription ID or player ID, and use IncludeExternalUserIds to target by external ID.

Thank you for your continued patience.

[matheuscschenfeld]

Any news about this issue?

[DaveBrask]

I find that IncludeExternalUserIds works for me, and I plan on using it in production. Soon. Is that a bad idea?

[matheuscschenfeld]

@nan-li Any news from OneSignal on this? I'm constantly having problems creating a notification. It looks like the response = await appInstance.CreateNotificationAsync(notification); fails and I don't know why.

[DaveBrask]

@nan-li: i'm away from the office. When I get back I'll post working code. I'm suspect your create notification works but doesn't know anyone to send it to.
I'm working on requesting push notification permissions for Android 13 and iOS in Maui.