[B2G][Email] User is unable to resend failed email from the activity message

RESOLVED INVALID

Status

Firefox OS
Gaia::E-Mail
RESOLVED INVALID
5 years ago
5 years ago

People

(Reporter: Mila Davydova, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Bug Flags:
in-moztrap +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: testrun 2, testrun 5.1, leorun3)

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 695893 [details]
Activity message

Unagi, Build ID 20121217070202 Refer to test case #2777 

User is unable to retry sending a message by selecting the "Try Again" option in the failure message. There is no "Try Again" option displayed, to re-attempt delivery of the message.

Repro steps:
1. Install build 20121217070202
2. Set up an email account on the device
3. Go to the account Inbox and tap the Plus button to open the Email Compose View
4. Fill in all the neccessary data
5. Turn off the Wi-Fi connection and send the email

Expected result: An activity message informing the user that sending the email failed and user is able to tap on the "Try Again" button

Actual result: The activity message is displayed informing the user that sending the email is failed, but there is no "Try Again" button displayed to re-attempt delivery of the message.
(Reporter)

Updated

5 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 1

5 years ago
Issue does repro on Build 20130104070203.  There is no Try again button however you can go out and retry to send just not Try again button

Comment 2

5 years ago
UCID: email-053
https://moztrap.mozilla.org/results/case/61839/
Whiteboard: testrun 2
(Reporter)

Comment 3

5 years ago
Issue is reproducing (as it is described in Comment 0) on unagi build 20130115070201 Kernel from Dec 5th

Updated

5 years ago
Hardware: x86_64 → ARM

Updated

5 years ago
OS: Windows 7 → Gonk (Firefox OS)
(Reporter)

Comment 4

5 years ago
Issue still reproduces on Unagi device 

Build ID 20130225070200
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/3a5a27992a75
Gaia: 5691a16fff8e1403c75ed9d6f3a443b7e58198c6

The activity message is displayed informing the user that sending the email is failed, but there is no "Try Again" button displayed to re-attempt delivery of the message.

UCID: email-053
TC: https://moztrap.mozilla.org/runtests/run/859/env/305/?pagenumber=1&pagesize=20&sortfield=order&sortdirection=asc&filter-id=2777
Whiteboard: testrun 2 → testrun 2, testrun 5.1

Comment 5

5 years ago
In reference to Comment 4

Test Case # 2777
UCID: email-053

https://moztrap.mozilla.org/manage/cases/?pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-id=2777

Comment 6

5 years ago
Let's recheck the requirements around this.
Keywords: qawanted

Comment 7

5 years ago
UCID: email-053
As a user I want to be able to retry sending a message by selecting the retry option in the failure message, so that I can immediately re-attempt to deliver the message.

Updated

5 years ago
Flags: in-moztrap+
Keywords: qawanted
(Reporter)

Updated

5 years ago
Whiteboard: testrun 2, testrun 5.1 → testrun 2, testrun 5.1, leorun3

Comment 8

5 years ago
This moved out of scope in the 1.1.0 requirements.

Comment 9

5 years ago
Issue repros on 
Leo Build ID: 20130625070217
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/29933d1937db
Gaia: 1436e2778b90bd74635b0b94d1cf8ccb0d71b60c
Platform Version: 18.1

When user turns off wifi before sending and email the email fails to send.
(In reply to John Hammink from comment #8)
> This moved out of scope in the 1.1.0 requirements.

Right.  The 'retry' case was for asynchronous/background mail sending.  We don't do that in v1.1 or on master right now.  The test case should be disabled or deleted for the time being.  The 'retry' button may or may not come back when we discuss the new feature with UX and implement it; either way, it'll be worked on that bug, so we don't need this bug.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.