Closed
Bug 1052349
Opened 10 years ago
Closed 10 years ago
[Loop] Discard the operation of sharing URL generate a new entry in the call log (Shared link tab)
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(b2g-v2.0 affected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
People
(Reporter: mbarone976, Unassigned, NeedInfo)
References
Details
(Whiteboard: [mobile app][not blocking][feedback pending][tef-triage])
Attachments
(1 file)
204 bytes,
text/html
|
Details |
Device: Flame
Loop Id: d9507c2
STR
1. On Loop client try to share a URL with someone with no Loop ID
2. When the fallback mechanism is shown select email or sms (I can reproduce with both options)
3. If you are in email app, close the app before send the email clicking, or perform any other action (Same in sms app). The point is, don't send the email/sms.
ACTUAL RESULT
A new entry in the Shared link tab is created even if you haven't shared the URL
EXPECTED RESULT
The new entry should be not created
Updated•10 years ago
|
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 1•10 years ago
|
||
This issue still occurs on the latest 2.0 build with the v165 KK base. Failing to complete a send will still result in the attempt being logged.
Environmental Variables:
Device: Flame 2.0
BuildID: 20140819030000
Gaia: 287a2c725a5c14e5dc1d48e3158ffc79c7d1ea33
Gecko: 6329352ca531b977979451e77e5862af485388b2
Version: 32.0 (2.0)
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Loop version: 32219a2
Comment 2•10 years ago
|
||
This is a tricky one as the message with the link could be saved to drafts and be sent later on, in that case users are likely to want to revoke the link later on, and the only way to do it is showing it in the shared links tab.
Due to that I don't think this is a bug and if it is, it should not be blocking. Massimo, what do you think?
Flags: needinfo?(mbarone976)
Whiteboard: [mobile app] → [mobile app][not blocking][feedback pending]
Closed
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(mbarone976)
Resolution: --- → WONTFIX
Reopened because is not clear the behavior here.
STR
1. Create Contact A on device using a phone number that is not a Loop ID
2. From device A try to establish a loop call with the user created on point 1
3. The fallback mechanism is shown, select the option message
4. The sms app is opened with the loop default message (that include the shared URL)
5. At this point close the sms app (click on the X)
6. Two options are displayed: 1. Save as Draft 2. Discard
ACTUAL RESULT
If you select the option 1 (Save as Draft) a new entry in the loop call log is shown even if the user didn't send the sms. Same happens with the option 2.
I guess we need Product input here, specially for option 2.
Status: RESOLVED → REOPENED
Flags: needinfo?(jmunuer)
Resolution: WONTFIX → ---
Updated•10 years ago
|
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
Whiteboard: [mobile app][not blocking][feedback pending] → [mobile app][not blocking][feedback pending][tef-triage]
Comment 5•10 years ago
|
||
Sharing by email based on MozActivity provided by email app. I don't ask for a review because we are focus on releasing right now. Maybe next week
Updated•10 years ago
|
Comment 6•10 years ago
|
||
Let's close this bug as Won't fix, as in the new 1.1.1 Loop Mobile version based on Rooms, the fallback mechanism is not a shared URL link but a Room URL. As the Room can be created without sharing it, we are not going to face this problem anymore.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•