935686 - [B2G][1.2][MMS] When a file name containing spaces is sent via MMS, it will be received with # symbols instead of spaces.

Status: RESOLVED DUPLICATE of bug 919980

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[J Zimbrick]

Description:
When a file with a name containing spaces is sent via MMS, it will be received with a new name containing # symbols instead of spaces

Pre-requisite:
Have a sendable file saved to the phone containing spaces in the title. Example "test image.jpeg" or a song title containing spaces.
Have a second phone available to receive an MMS message.

Repro Steps:
1. Update Buri device to build 20131103004003.
2. Open the Messages app.
3. Tap the pencil and paper icon in the top sright to open a new message.
4. Tap the paper clip icon in the bottom left to open the attachments menu.
5. Select the a file from the video, music, or gallery menus with a name that contains spaces.
6. Add a valid recipient in the To: field and a send the MMS message.
7. Observe that when the second phone receives the file, any spaces in the file name will be filled in with the # symbol.

Actual:
When a file with a name containing spaces is sent via MMS, the file name will have all spaces replaced with # symbols when it is received.

Expected:
The file name is the same when it is sent and when it is received.

Environmental Variables:
Device: Buri v1.2 Commercial RIL
BuildID: 20131103004003
Gaia: cb981e2f47bc644b4d178d54378c3676c946facf
Gecko: eec4da1b27eb
Version: 26.0
Base Image: 20131015

Notes:
Repro frequency: 100% on two devices.
Link to failed test case: https://moztrap.mozilla.org/manage/cases/?filter-id=9002

Comment 1

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

Hey Steve, can we have spaces in an attachment name?

Comment 2

[Steve Chung [:steveck]]

Based on comment bug 909622 comment 3, we should be able to sent attachment with space since it's ASCII char. How about we check the charcode directly if we want to make some change in this issue?

Comment 3

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

I'll dupe against bug 919980 then.