ENVIRONMENT: ZTE Open C v1.3 from Ebay [ro.build.display.id]: [FFOS_US_EBAY_OPENCV1.0.0B05] [ro.build.inner.version]: [FFOS_US_EBAY_P821A10V1.0.0B07] [ro.build.version.incremental]: [eng..20140519.032635] STEPS TO REPRODUCE: 1. Use a phone "A" to send an SMS to the ZTE Open C. 2. Tap on the SMS notification received in the ZTE Open C, to open that message thread (A). 3. Use a different phone, "B" to send an SMS to the ZTE Open C. 4. Tap on the new SMS notification received in the ZTE Open C, to open that message thread (B). 5. Reply to the message. EXPECTED RESULTS: The message reply should go to the notification that was tapped on the latest, thread B. ACTUAL RESULTS: The message is sent to wrong person, on message thread A. Please let me know if there is any information I could provide to help with the investigation and troubleshooting of this issue. Thanks!!

Is this the same issue we saw in bug 988726?

Hi Gabriele, After reading bug 988726, it seems similar to what Dietrich experienced - however, I have been able to replicate this issue 100% of the time on ZTE Open C (that I can remember). I don't know about other devices - I haven't attempted these specific steps on other models/versions. Thanks, - Ralph

bug 988726 was not on v1.3 and notifications and navigation work quite different between 1.3 and 2.0. I'm really surprised by this bug and I am afraid that this is due to a partner change... NI me to check on a v1.3 build. Ralph, it would help a lot if you can try to reproduce on your phone using several configurations (known contacts, unknown contacts, etc) and report. Also, can you try to extract the file application.zip for the sms app from your phone and attach it here?

Hi Julien, I tried it with contacts and with no contacts, as well as 1 phone from someone listed in Contacts and the other phone from someone not listed in Contacts. The issue replicated in all cases. I had to use ZTE's update tool to get the phone rooted, so that I could extract the SMS app. This is the command I used, is it right?: "adb pull /system/b2g/webapps/sms.gaiamobile.org/"

Extracted SMS app using the following command: "adb pull /system/b2g/webapps/sms.gaiamobile.org/"

Screenshot of the 4 steps to replicate this bug.

I'm sorry Ralph, I don't follow the steps on the screenshot. On the second image, we see "Google Voice" in the header, but the content is really the "self" thread, right? So is this the issue ? * tapping on the second notification (from Google Voice) should move to the Google Voice thread * the header is right * the content is wrong, the content is the content from the "self" thread * sending a message sends it correctly to the "Google Voice" number. (I say "correctly" because that's the thread that is supposed to be displayed, even if it's confusing that the content is wrong). I don't see much difference between the SMS app in attachment 8449086 [details] and the app on our repository. There are some difference because of some late fixes we did and very small changes the operator did. So let's confirm it with you first :)

Ralph, another useful source of information would be the logcat. Can you capture the logcat output while you reproduce the issue and put it in a log file and attach it here?

Hi Julien, You are correct on all counts, that's a perfect description of the screenshots and the behavior of this bug. I can definitely get a logcat for it. Is this logcat command good enough, or should I add other arguments? adb logcat -v time Thanks! - Ralph

I usually use "-v threadtime" but in this case it's probably as good. Also FYI I got one same report here in Paris from the same device/same version (and we still couldn't reproduce when really trying, on that device...). So the goal is to find the correct STR...

Hi Julien, Here is the logcat file. I also recorded a video of the steps to reproduce, in sync with the logcat. The video is available on Youtube, through this link: https://www.youtube.com/watch?v=-3ykih-Sopw I hope this helps. Please let me know if there's anything else I can do to help. Thanks, - Ralph

Thanks a lot Ralph, this is very precise information. This is really weird that I don't reproduce on my side (but I'll try again using the exact steps you used). Can you tell me whether you linked some Contacts with Facebook?

So I tried again and I still can't reproduce. This is really frustrating. Is it possible that you share with me your whole db (in /data/local/storage/persistent/ on the device)? It can be by private mail if necessary (you can use my PGP key :) ).

BTW my mozilla mail is julien AT mozilla.com.

Hi Julien, I had no Facebook contacts linked in the Contacts app. I had only saved contacts for testing purposes, but besides that, the phone had a fresh "factory reset." I am attaching the contents of "/data/local/storage/persistent" as a zip file. I hope it helps! Additionally, I will be in the San Francisco office this Friday, between 12:00pm-6:00pm before I have to catch my plane back to Portland. If you would like, I might be able to arrange handing this phone to you and ordering another one for myself. Please let me know your thoughts. Thanks! =) - Ralph

(In reply to Ralph Daub [:rdaub] from comment #15) > Created attachment 8453500 [details] > data-local-storage-persistent.zip > > Hi Julien, > > I had no Facebook contacts linked in the Contacts app. I had only saved > contacts for testing purposes, but besides that, the phone had a fresh > "factory reset." > > I am attaching the contents of "/data/local/storage/persistent" as a zip > file. I hope it helps! Thanks a lot, I'll try with this now :) > > Additionally, I will be in the San Francisco office this Friday, between > 12:00pm-6:00pm before I have to catch my plane back to Portland. If you > would like, I might be able to arrange handing this phone to you and > ordering another one for myself. I'm in Paris, so it won't work ;)

I really still can't reproduce with your data; I don't have exactly the same build but I tried with both an older (when I tried before) and newer (when I tried now); I tried sending from several other SIMs. The only thing I haven't tried is sending first from the SIM that's in the device (that SIM couldn't send a message) so I'll try this now.

So I don't reproduce here either...

I'll try to find a real Open C here, probably with Natalia, but she's away this week so...

Hi Julien, I am giving this phone to Hermina Condei, who was here in San Francisco for the week and will be flying back today. =) Thanks, - Ralph

Great thanks !

I got your phone and I definitely reproduce. I think that what happens is that we get the notification callback twice... and I also definitely remember the issue, and that we fixed it. Now trying to dig :)

Found it, I'm sure it's bug 956276. It was fixed quite late in the 1.3 process, and now I'm afraid ZTE didn't take it in their build. I didn't see it when you sent me the SMS app from your phone because the bug was actually in the System app... I'm gonna dupe this bug there, but I'll follow-up with our release managers to know if and how this can be handled.

Oh, I see; bug 956276 was uplifted to 1.3 very late, because other bugs were uplifted in the same time that caused this regression. Now, I feel like ZTE took the main bugs but forgot to take the regression fixes...

Confirmed, the offending line is in the System code.