Ephemeral push notifications authorization status

[IsaiahJTurner]

There seems to be a discrepancy between the PustEnablement status options in the iOS SDK and the ones in the node API.

In the node SDK, there are two statuses both "UNAUTHORIZED" and "DENIED" and it's unclear what "UNAUTHORIZED" is since that is not a status option within the Apple Docs.

Additionally, the node SDK lacks type support for EPHEMERAL.

Here are the statuses in the Apple Documentation:
https://developer.apple.com/documentation/usernotifications/unauthorizationstatus

Here is what is in the Kaviyo iOS SDK:
https://github.com/klaviyo/klaviyo-swift-sdk/blob/80cec2cc2dbfd7a17b9a971b3ffe1268d86576a6/Sources/KlaviyoCore/Models/PushEnablement.swift#L14

Here is what is in the TypeScript definition:

klaviyo-api-node/model/pushTokenCreateQueryResourceObjectAttributes.ts

Line 27 in d287328

'enablementStatus'?: PushTokenCreateQueryResourceObjectAttributes.EnablementStatusEnum | 'AUTHORIZED' | 'DENIED' | 'NOT_DETERMINED' | 'PROVISIONAL' | 'UNAUTHORIZED' | null = PushTokenCreateQueryResourceObjectAttributes.EnablementStatusEnum.Authorized;

There is no option for EPHEMERAL and an unexpected option for UNAUTHORIZED.

Also somewhat related and worth noting that the iOS sdk does not seem to use "iPadOS" as a platform option despite this being provided as an option in the OpenAPI spec.

[evan-masseau]

Hey thanks for bringing these details to our attention!

The difference between DENIED and UNAUTHORIZED is by platform. The former is used for iOS, the latter is for Android. In truth they effectively mean the same thing.

The missing EPHEMERAL status is an oversight that we will investigate, but I think that our SDK doesn't support "instant apps", which are the only way to get that status. So while we do have the enum case in there, it's technically unreachable.

We should fix that OS detection in the SDK code that you pointed out, since the swift SDK could be running on iOS, iPadOS or MacOS!

[IsaiahJTurner]

Got it, that makes sense. Thank you!

We use App Clips (instant apps) and were attempting to set up Klaviyo without the client SDK to minimize file size by using the API directly with our backend which is why I was looking to pass the ephemeral status along. Good to know this may be unsupported/untested!

[evan-masseau]

No problem! We’d love to hear more about your use case with app clips / instant apps if you have a minute to share. Do you get a lot of traffic via these ephemeral apps? Presumably push notifications would help drive return traffic. It isn’t something we hear about much from customers, so your feedback would be valuable!

[IsaiahJTurner]

Spending a minute to think about it, I realize it may be easier to just use local notifications since they are scheduled and predictable but generally we use our App Clip as a way to funnel new users into the full app. Almost every new user goes through it. Notifications are a way to maximize funnel conversion. In theory Klaviyo Flows could do this.