feat: Enhance date handling in InboxMessage and add unit tests for JS… - #7
Open
ktdesilva wants to merge 1 commit into
Open
feat: Enhance date handling in InboxMessage and add unit tests for JS…#7ktdesilva wants to merge 1 commit into
ktdesilva wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi team,
I identified the root cause of an parsing issue. On certain iOS devices, the SFMC inbox payload returns the sendDateUtc field inconsistently. In some cases it arrives as a string-like value, and in others it originates from an NSDate representation, which leads to inconsistent serialization before the value reaches Flutter.
Examples observed:
"2026-05-02 05:28:00.000"
"2026-05-02 3:56:00 AM +0000"
Because of this inconsistency, the Salesforce Marketing Cloud Flutter plugin can fail while mapping the date field into Dart.
To resolve this, we implemented a fix in the iOS side of the Flutter plugin to normalize the date value before it is passed to Flutter. A forked version of the plugin is available here: