[Bug]: Braze Payload issue

[BrazeCJ]

Platform

iOS

Platform Version

iOS 14] +

Braze SDK Version

5.11.0

Xcode Version

Xcode 14.2

Computer Processor

Intel

Repro Rate

100%

Steps To Reproduce

1. iOS Setting(method didFinishLaunchingWithOptions) excepts for silent push
2. Push with Braze campaigns
3. Run to app(Background Mode)

Expected Behavior

Push Payload information(field name : ab) is not being called correctly. This prevented the app from activating properly in background mode.

Actual Incorrect Behavior

Push Payload information(field name : ab) is not being called correctly. This prevented the app from activating properly in background mode.

Verbose Logs

No response

Additional Information

No response

[jerielng]

Hi @BrazeCJ, could you provide a little more details around your testing? Are you able to debug where the failure point is in your code? Specifically, in your else block, can you confirm where exactly you are not getting the values you are expecting (i.e. is the launchOptions nil, is the remoteNotification nil, etc.)?

From our end, I am not able to reproduce a scenario where the "ab" contents are not present in the push payload. It's worth pointing out that we typically check and process the push payload in the application(_:didReceiveRemoteNotification:fetchCompletionHandler:) delegate method for handling silent/background notifications, per the integration tutorial. Is there a specific reason you are relying on didFinishLaunchingWithOptions?

[BrazeCJ]

Hi @jerielng ,

Thanks you for answer.

Are you able to debug where the failure point is in your code? answer : below the image and The issue occurs at the time of the push click while the app is closed.

Is there a specific reason you are relying on didFinishLaunchingWithOptions answer : They do not want to recieve silent push so they set Braze Slient Push exceptions.

[jerielng]

Hey @BrazeCJ, thanks - in that screenshot, more specifically, could you specify which of those three objects is coming back nil? Figuring out which one is not populating would help pinpoint if it's an issue inside the Braze payload or something in the UserNotifications framework.

If possible, it would be helpful to gather all of this information, along with a relevant campaign that you are using to test, to send to our support team at support@braze.com and then reference this GitHub issue for additional context.

[BrazeCJ]

Hi @jerielng

I hope you are doing well.

Information coming in as nil means "ab" in the Payload field

Thanks

[jerielng]

@BrazeCJ Are you able to log and share what the payload of your remoteNotification object contains?

[hokstuff]

Hi @BrazeCJ,

Are you still experiencing this issue? It will likely be easier to converse via our Support channels at support@braze.com to share any relevant code and behaviors you are seeing. Thanks!

[lowip]

Hi @BrazeCJm

I'm closing this ticket due to inactivity, feel free to re-open it if you're still facing the issue.

Best,