New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 677604 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
qin...@chromium.org
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

[Chrome][M55][Android 7.0] same images are share via Bluetooth even though trying to share different images

Reported by seiyon.p...@gmail.com, Dec 30 2016 
Steps to reproduce the problem:
1. Have two mobile devices and enable Bluetooth on each device
2. [A] Launch Chrome on device A
3. [A] Go to any sites with images
4. [A] Long-press an image > Touch "Download image"
5. [A] Open downloaded image (download.jpg)
6. [A] Touch "Share" button > Select Bluetooth > Choose device B 
7. [B] receiving & opening "download.jpg" is successful
8. [A] Long-press another image > Touch "Download image"
9. [A] Open downloaded image (download (1).jpg)
10. [A] Touch "Share" button > Select Bluetooth > Choose device B 
11. [B] Received file is "download.jpg" not "download (1).jpg"

CREATE NEW FILE

What is the expected behavior?
"download (1).jpg" should be shared with Bluetooth.

What went wrong?
"download.jpg" is shared with Bluetooth.

Did this work before? Yes M54

Chrome version: 55.0.2883.91  Channel: stable
OS Version: 7.0
Flash Version: Shockwave Flash 24.0 r0

Comment 1 by undead1h...@gmail.com, Dec 30 2016

trash.desktop
2.6 KB Download

Comment 2 by rsgav...@chromium.org, Jan 4 2017

Cc: krav...@chromium.org
Labels: triage-te

Comment 3 by seiyon.p...@gmail.com, Jan 31 2017 

Gentle reminder

Comment 4 by seiyon.p...@gmail.com, Feb 7 2017 

Gentle reminder

Comment 5 by krav...@chromium.org, Feb 16 2017

Cc: -krav...@chromium.org qin...@chromium.org
Labels: -triage-te
Tested with latest M56 build and download(1).jpg is shared via bluetooth

To attach bugreport:

Could you please attach the bugreport, This will help us reproduce what you are seeing.

Android Settings > About Phone > Tap Build number 10 times, go back one screen, Developer options should be right above About phone.

Check the USB debugging the Take the bug report

Comment 6 by seiyon.p...@gmail.com, Mar 30 2017 

Could you take a look at main.log?
You could find important information around 03-25 11:39:xx.xxx.
main.log
7.3 MB View Download
elsa_lgu_kr_user.txt
1002 bytes View Download

Comment 7 by msrchandra@chromium.org, Nov 17 2017

Cc: msrchandra@chromium.org
Labels: Needs-triage-Mobile Triaged-Mobile Needs-Feedback
Tested the issue on Latest Stable# 62.0.3202.84 using Pixel XL (Android 8.1.0) & Samsung J710F (Android 7.0.0) and could not reproduce the issue.

@seiyon.park -- Could you please upgrade your Chrome to latest stable and provide the updated behavior. If reproducible could provide us with a screen cast of the issue which would help us triage the issue further.
Thanks in Advance.

Comment 8 by seiyon.p...@gmail.com, Nov 21 2017 

I've upgrade Chrome to v62 and verified that it's not reproducible any more.
Thanks.
Project Member

Comment 9 by sheriffbot@chromium.org, Nov 21 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by msrchandra@chromium.org, Nov 21 2017

Status: WontFix (was: Unconfirmed)
@seiyon.park -- Thank You for the quick update.
Marking the issue as Won't Fix as per Comment# 8. Please feel free to raise a new bug if the issue is again seen.
►

Sign in to add a comment