Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: iOS Rich Push Notifications #106

Open
idamaeng opened this issue Jun 13, 2024 · 4 comments
Open

[Bug]: iOS Rich Push Notifications #106

idamaeng opened this issue Jun 13, 2024 · 4 comments
Labels

Comments

@idamaeng
Copy link

idamaeng commented Jun 13, 2024

Braze Unity SDK Version

6.0.0

Steps To Reproduce

Expected Behavior

Receiving a push notification including the image.

Actual Incorrect Behavior

Receiving a push notification without the image

Verbose Logs

No response

Additional Information

No response

@idamaeng idamaeng added the bug label Jun 13, 2024
@idamaeng
Copy link
Author

Maybe its worth mentioning that I needed to rearrange the build phase of the main target to be able to build. Actually I moved Embed Frameworks and Embed Foundation Extension as high as possible

Screenshot 2024-06-13 at 18 06 01

@idamaeng
Copy link
Author

Do you need further info?

@vanessaland
Copy link
Collaborator

Hi @idamaeng ,

Thanks for reaching out! Here are some things you can try:

  • On the Targets > NotificationService configurations page, ensure that you are adding the BrazeNotificationService module under General > Frameworks and Libraries
  • Ensure you have all the necessary components in your NotificationService class (tutorial)

If you are still experiencing this issue, can you please contact support@braze.com with more information:

  • Attach verbose logs when reproducing this issue
  • Attach your code file/snippet for NotificationService.swift
  • Attach a screenshot of your Targets > NotificationService configurations page
  • Mention the Braze Unity SDK version you are on and which XCode version you are on
  • Add a link to this Github issue for reference

The Braze Support team should help with diagnosing the root cause of this issue!

Thanks!

@idamaeng
Copy link
Author

Thanks for the reply. You are referring to the steps I already tried. See the tutorial link I initially posted in my bug description :). Trying my luck with sending a mail to your support team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants