Conversation
awang343
changed the title
jjoelj
approved these changes
Sep 29, 2026
This branch has not been deployed
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.
Problem:
When manually exporting contacts from Android, contacts arrive on the server with a display name but no phone number or email. The manual export path built each contact with ContactV2.toMap(), which shapes fields differently than the server API expects.
Solution:
Changed the manual export in settings_items_actions.dart to use contact.toServerMap() instead of contact.toMap(), matching what the automatic sync path already does.
Testing:
Tested that manual export uploads phone numbers and emails to server correctly.
Screenshots:
N/A