[GH-ISSUE #171] X-smssync-address does not parse correctly when it has utf-8 string in it #143

Closed
opened 2026-02-26 00:36:21 +03:00 by kerem · 1 comment
Owner

Originally created by @priv on GitHub (Aug 18, 2011).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/171

When the contact name has utf-8, for example:
(+886987654321 below is a fake example number I created for example)

X-smssync-address: =?UTF-8?Q?=E6=AD=A3=E8=8A=AC-GSM_=3C+886987654321=3E?=

sms backup+ failed to parse out the number +886987654321
I restore the contact, and in messaging AP it shows the contact as "=?UTF-8?Q?=E6=AD=A3=E8=8A=AC-GSM_=3C+886987654321=3E?="

But when exact same contact(And actually they're in the same dialogues if you view them in gmail), but only has number in X-smssync-address, ie. X-smssync-address: +886 987654321

Sms backup+ restore can correctly file the message to correct contact in my phone.

What's your suggestion that I can prevent this problem? Will you fix this? Either you should strip the utf-8 string in X-smssync-address, or you should convert it back to a valid utf-8 string.

Originally created by @priv on GitHub (Aug 18, 2011). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/171 When the contact name has utf-8, for example: (+886987654321 below is a fake example number I created for example) X-smssync-address: =?UTF-8?Q?=E6=AD=A3=E8=8A=AC-GSM_=3C+886987654321=3E?= sms backup+ failed to parse out the number +886987654321 I restore the contact, and in messaging AP it shows the contact as "=?UTF-8?Q?=E6=AD=A3=E8=8A=AC-GSM_=3C+886987654321=3E?=" But when exact same contact(And actually they're in the same dialogues if you view them in gmail), but only has number in X-smssync-address, ie. X-smssync-address: +886 987654321 Sms backup+ restore can correctly file the message to correct contact in my phone. What's your suggestion that I can prevent this problem? Will you fix this? Either you should strip the utf-8 string in X-smssync-address, or you should convert it back to a valid utf-8 string.
kerem 2026-02-26 00:36:21 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@jberkel commented on GitHub (Jun 12, 2015):

hopefully fixed with new K9

<!-- gh-comment-id:111417779 --> @jberkel commented on GitHub (Jun 12, 2015): hopefully fixed with new K9
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sms-backup-plus-jberkel#143
No description provided.