Description: User may observe that when attempting to perform an NFC transfer, their transfer will send a different file than was initiated by the transfer. In many cases, the transfer appears to send the previously sent file, resulting in double transfers of the same file before sending the next. For example: PhoneA wants to send files to PhoneB PhoneA uses NFC to send Image1 // to PhoneB *PhoneB successfully downloads Image1 PhoneA uses NFC to send Image2 *Phone B successfully downloads Image1 Have observed: * From Gallery: sending a different image than the one targeted in Gallery * From Video: sending a different video than the one targeted in Video * From Music: sending a video instead of a music file * From Music: sending an image instead of a music file PreReq: * two phones with NFC enabled * phone with content (PhoneA) to transfer [images, videos] Repro Steps: 1) Update a Flame to 20150407010204 2) Open Gallery on PhoneA 3) Tap an image to open larger view 4) Position PhoneA back to back with PhoneB (initiate NFC transfer) 5) Hold until request is confirmed and begins, may set near eachother afterwards. 6) After transfer completes, compare file sent (from PhoneA) to file received (on PhoneB) Actual: File received via NFC transfer is different from file sent Expected: File received via NFC transfer matches file sent Environmental Variables: Device: Flame 3.0 Build ID: 20150407010204 Gaia: c710bac533b76635161315bf907d004e000549cb Gecko: ab0490972e1e Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0) Firmware Version: v18D (and v18D-1) User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Repro frequency: 5/20 See attached: * nothing, have not been able to repro while recording actions exhibited by the bug, through either log or video

[Blocking Requested - why for this release]: Broken functionality of a supported feature. Adding qawanted for branch checks.

I was unable to reproduce this issue on the current Nightly Flame build after 20 attempts so I cannot reliably do branch checks. Leaving the tag for another to try. Environmental Variables: Device: Flame 3.0 BuildID: 20150408010203 Gaia: 84cbd4391fb7175d5380fa72c04d68873ce77e6d Gecko: 078128c2600a Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

I also cannot reproduce this issue after one hour of trying. I sent music(mp3) files, videos, pictures and all transfers were completed for the correct files. Leaving qawanted for others to attempt. Device: Flame 3.0 Master (full flash, 319MB, KK) BuildID: 20150409010203 Gaia: 5dfd0460eb6e616205154b0d219aa5123bf1abb3 Gecko: 8f57f60ee58a Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0 Master) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

I was also unable to reproduce this issue while transferring image, audio, and video files via NFC after about 30 attempts. The correct file was sent and received each time. Environmental Variables: Device: Flame 3.0 (KK, 319mb, full flash) Build ID: 20150409010203 Gaia: 5dfd0460eb6e616205154b0d219aa5123bf1abb3 Gecko: 8f57f60ee58a Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (Master) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Removing qawanted tag.

removing nomination since this can no longer be reproduced. ni to reporter just in case there's other STR to try.

Could not repro this issue on latest master [3.0] for flame devices Results: NFC transfer correct file -------------------------------------------------- Environmental Variables: Device: Flame 3.0 BuildID: 20150417010203 Gaia: 3cd0a9facce26c2acc7be3755a17131a6358e33f Gecko: 51e3cb11a258 Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 -------------------------------------------------- Repro Rate: 10/10 Resolving as worksforme due to the overwhelming repro (4 different testers) that could not observe the issue.