Jeriel Ng

Hi @markanderson-underdog, thanks for raising this. If I understand correctly, you are receiving the 100%-on value at your first launch of the app, and then while the app is still...

Hey @PlanesWalkerr, it sounds like you're trying to add your own custom logic in `UNNotificationServiceExtension.didReceive(_:withContentHandler:)`, is that correct? The Braze implementation of that method calls the [`brazeHandle`](https://braze-inc.github.io/braze-swift-sdk/documentation/brazenotificationservice/brazehandle(request:contenthandler:)) method, which is...

Hi @RadiBarq, thanks for raising this! For feature requests, could you file it [here](https://dashboard.braze.com/resources/roadmap) so we can get this routed to the appropriate teams? Thank you!

Sure thing @RadiBarq, we can keep this issue open as a means to update you on the status of this request. Thanks!

Closing this issue out due to inactivity. If you are continuing to see this issue, please reach out to the support email above. Thanks!

Hi all, we have released a number of versions since this issue. As of version 2.33.0, this SDK uses an updated version of the native Swift SDK, which has overhauled...

Hi @vicsuccess, thanks for raising this. It seems that there is some kind of race condition occurring here where the constraints are not allocated for some reason at the time...

Hey @vicsuccess, do you happen to have any sample code you can share that easily reproduces the issue? Or any verbose logs that show the order and history of the...

Hi @initishbhatt, thanks for your request! At the moment, our `add(alias:label:)` method does check and log errors if the alias is not valid, so you should be seeing some output...

@initishbhatt That makes sense - thank you for your feedback! Since this would be a feature request, could you file it [here](https://dashboard.braze.com/resources/roadmap) to route it to our product teams for...