-
Notifications
You must be signed in to change notification settings - Fork 1.7k
pass appData for In-App Messaging's test message #9134
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
pass appData for In-App Messaging's test message #9134
Conversation
|
Thanks for the PR @fumito-ito! Many people are currently out, so it may be a few weeks before we can do a review. |
|
hi @fumito-ito , Thanks for doing this fix and it looks good. But did you get any chance to check whether with this fix you were able to receive the data bundle for a test campaign. When I checked I was not able to receive the databundle and it seems like the back end is not sending it. Could you please confirm? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please wait till we test this changes before merging.
|
@eldhosembabu You can merge it when ready. |
|
hi @eldhosembabu, Thanks for your review.
#9126 is caused by both sdk and backend. This PR fixes only sdk problem. Could you report this problem to backend team ? Or to report this problem, could you let me know a backend team's public contact point If you have ? |
|
I've already brought it to the backend team attention. Merging this PR as it looks good for the SDK side. |
updating change log wrt #9134
updating change log wrt #9134
* add test to check appData parsing * parse appData for test message * fix by formatter
updating change log wrt #9134
refs: #9126
FIRIAMFetchResponseParseris better not to ignore appData for test message. This PR fixes #9126 problems particaly but not completely.