Closed Bug 942759 Opened 11 years ago Closed 11 years ago

[Messages] Send SMS activity seems to be nonfunctional in some situations

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 946678

People

(Reporter: micadeyeye, Assigned: micadeyeye)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20131119030202

Steps to reproduce:

Upgraded b2g to ver. 1.3 pre-release. Then import contacts from a sim card and add some new contacts.
After that, try send an sms to a person by first going to contacts, choose a contact, and then click the text icon that is used to compose a message to the chosen contact.


Actual results:

The text icon rather takes one to the ALL Messages webview. 
If you want to get the compose message webview, you will need to hide the All Messages webview.
As one goes back to the contacts and add a contact, the contact is added to the message that needs to be composed and sent. But all of these activities are hidden from the user until (s)he hides the All messages webview


Expected results:

The text icon is supposed to load a webview, where a user can type a message to the intended recipient.
This is the logcat for the phone that acts up - http://pastebin.mozilla.org/3668359
Everything works fine on this second phone after I upgraded it - http://pastebin.mozilla.org/3668380
Hey Michael, some questions for you!

* Do you have the same contact list on both phones?
* can you share your contacts database with us (a private mail is fine if you prefer to not share it publicly on Mozilla)
* was the contact you chose imported from the SIM. What happens on a contact you manually added?

I think I have an idea of what's happening but the answer to these questions could help.

Thanks!
Summary: sms feature in b2g ver.1.3 → [Messages] Send SMS activity seems to be nonfunctional in some situations
Flagging "needinfo" on Michael so that I don't lost the track of this :)
Flags: needinfo?(micadeyeye)
* Do you have the same contact list on both phones? 
No.
* can you share your contacts database with us (a private mail is fine if you prefer to not share it publicly on Mozilla) 
Sure, I can.

* was the contact you chose imported from the SIM. What happens on a contact you manually added?
I chose both contacts - from the SIM and newly added. The contact I manually added behaved the same way.

The problem can be easily replicated on any phone. I have confirmed it on two phones running 1.3.
-Flash with the 1.3pre-release
-Add some contacts - either via import from a SIM card or manually add new contacts
- Send a message to any of them - Note: the phone behaves the right way here.
- Now go back to home; go to contact, choose a contact to send a message to, and click the send message icon. - Note: the phone will only stop at the "All Messages" view. If you want to see the compose view, go back to home and then click the sms/messaging icon.

The phone will behave the wrong way so long you have one or more messages already sent or received in the "all messages" view.

PS: I am still working on a fix for it. I changed the disposition for 'new' in the manifest from 'inline' to 'window', but it won't work.
Flags: needinfo?(micadeyeye)
Could QA please try this on a 1.3 build on one of our internal builds?
blocking-b2g: --- → 1.3?
Keywords: qawanted
Assignee: nobody → micadeyeye
Whiteboard: [mentor=:julienw]
We were unable to reproduce this issue on two Buri devices running the latest 1.3 Mozilla build.

When the user taps the text icon on a contact they are taken to the proper compose screen each time, this is after importing contacts from a sim  and creating new contacts and then sending several SMS messages.

Are there additional steps required to reproduce this issue?
Also, which device was this issue seen on?

Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20131126052050
Gaia: 4ad796b196d468bdb231beba4392acbc90a74e96
Gecko: 99479edbee2a
Version: 28.0a1
Base Image: V1.2_20131115
Keywords: qawanted
Flags: needinfo?(micadeyeye)
It's keon. I don't think there is any additional information. I have replicated the bug number of times.
Flags: needinfo?(micadeyeye)
It's keon. I don't think there is any additional information. I have replicated the bug a number of times.
ni? ayman as he wants to look into this
Flags: needinfo?(aymanmaat)
(In reply to Joe Cheng [:jcheng] from comment #9)
> ni? ayman as he wants to look into this

I cannot reproduce this.

build information:

unagi-ICS.
user.
master.
Rel0.4.
Sprint12.
B-205.
Gecko-7d81d80.
Gaia-03e6e87

I am going to speak with Julien
Flags: needinfo?(aymanmaat)
(In reply to Michael Adeyeye from comment #4)

> The problem can be easily replicated on any phone. I have confirmed it on
> two phones running 1.3.
> -Flash with the 1.3pre-release
> -Add some contacts - either via import from a SIM card or manually add new
> contacts
> - Send a message to any of them - Note: the phone behaves the right way here.
> - Now go back to home; go to contact, choose a contact to send a message to,
> and click the send message icon. - Note: the phone will only stop at the
> "All Messages" view. If you want to see the compose view, go back to home
> and then click the sms/messaging icon.

Tell me if I understood correctly: this doesn't work if you started an activity once and you want to start another activity but the previous one is not finished yet.
Flags: needinfo?(micadeyeye)
Pretty much like that. But basically, an activity (i.e. the sms activity via webcontact) shows the wrong webview. A user has to start the WebSMS program in order to get the right webview. I wouldn't want to say the activity isn't finished. The activity is finished. It's just that the right webview is buried under another webview (i.e. the wrong webview). I will try and send a short video soon.
Flags: needinfo?(micadeyeye)
It's now being fixed.
(In reply to Michael Adeyeye from comment #13)
> It's now being fixed.

 I just retested the feature. I actually did a repo sync and built FFOS again, The problem persists. I am retracting the previous message.
Michael, a video would definitely help having the same STR!

Thanks a lot in advance
Flags: needinfo?(micadeyeye)
Here is it - http://bit.ly/1ePSRZm
Flags: needinfo?(micadeyeye)
Thanks!

Now I can confirm the bug.

Isabel created the same bug (bug 946678), I'm gonna dupe this one there because the steps to reproduce are simpler and clearer.

I'd prefer to not assign you on that bug because this is a serious bug that should be fixed quickly. If you think you can do it then I can still assign you, just tell me!
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Whiteboard: [mentor=:julienw]
blocking-b2g: 1.3? → ---
You need to log in before you can comment on or make changes to this bug.