832365 - When B2G fails to *send* a file over bluetooth, the error message is incorrect -- it says "Bluetooth *received* a file it can not o..."

Status: RESOLVED FIXED

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

Description

[Daniel Holbert [:dholbert]]

STR:
 1. Pair another bluetooth device with your B2G device. (I'm using my Nexus 4 android phone)
 2. Try to send a file from B2G.
    (e.g. open music app, tap the lower-right icon for "albums" view, tap an artist,
     and long-press an audio-file in the final listing)

 3. Choose your other bluetooth device in the resulting dialog, and hit "OK".

ACTUAL RESULTS:
 Notification message saying "Bluetooth received a file it can not o...". This sounds like there was an issue with my device _receiving_ a file over bluetooth, when really I'm trying to _send_ a file.

EXPECTED RESULTS:
 Error message should indicate that the issue occurred with a file-send operation.

Comment 1

[Daniel Holbert [:dholbert]]

I'm using an unagi w/ build id 20130116230203.

Comment 2

[[e-mail], [e-mail]]

Daniel,
I have revised the string to let it reasonably in Bug 822168.
Notification message "Bluetooth received a file it can not open" has be changed by "File could not be received".
I'm not sure that the change is expected your results.

Comment 3

[Daniel Holbert [:dholbert]]

I'd marginally prefer "File could not be _sent_" for this situation (since B2G device is trying to send a file, not receive it).

However, "File could not be received" doesn't specify who failed at receiving (the B2G device vs. the other device), so I suppose it's vague enough to cover this situation.

Comment 4

[[e-mail], [e-mail]]

Attachment: File could not be sent

Comment 5

[[e-mail], [e-mail]]

Daniel,
I sorry that I misunderstand your mean. You're talking about the message("Bluetooth received a file it can not o..." or "File could not be received") unsuited for the sending file failed. I put the message in wrong side of judgement send/receive case.  

I have already fixed the issue in Bug 822168 too. So, it will show the message "File could not be sent" as the attached file now. We can close the issue now. 

Thanks for your help.:)

Comment 6

[Daniel Holbert [:dholbert]]

Ah, nice! Thanks.

Comment 7

[John Ford [:jhford] CET/CEST Berlin Time]

this is fixed by Bug 822168 which is fixed on v1-train