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

Issue 836923 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 831953
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

[User Feedback - Stable] Cannot upload files on 66.0.3359.126

Project Member Reported by melodychu@chromium.org, Apr 25 2018

Issue description

Chrome Version: 66.0.3359.126
OS: Android 


What is the expected result?
Users should be able to successfully upload files via Chrome, but we've received a 7X increase in the number of users who have reported that they are not able to upload pictures through Chrome. It doesn't seem to be about a specific site.

Sites:
Facebook
Twitter
avito.ru
and more

37% reports from RU.


What happens instead?
See user reports at:
go/chromeuploadfeedback



 
Labels: M-66
Cc: finnur@chromium.org twelling...@chromium.org
Owner: peter@chromium.org
Status: Assigned (was: Untriaged)
peter@ can you triage/check and see if there is anything going on with the photo picker?  Looks like users are having trouble uploading photos on 66.

Comment 3 by m...@trineo.co.nz, Apr 26 2018

We have observed this bug affecting users of an app we develop.

In case it is useful, I'll share what I've found in replicating the problem.

65.0.3325.109 is unaffected, but I can replicate the problem in 66.0.3359.106 and 66.0.3359.126.

I've replicated the problem on two test devices we have:

1) KYOCERA DuraForce E6560, running Android 4.4.2.
2) Samsung Galaxy S4 GT-I9505, running Android 5.0.1.

Both devices exhibit the same behaviour, when tapping on a file input with an `accept` attribute value of either `image/*` or `.jpg,.jpeg,.png,.gif` (and obviously any image-only variant like this) the device opens the "Select Images" screen along with a "Unfortunately, Chrome has stopped." dialog. Dismissing the dialog leaves the "Select Images" screen open with a stuck spinner - the user can return to the webpage but is unable to upload a photo. I've attached screenshots of this from both devices.

The workaround we are using at the moment is to leave the `accept` attribute blank for Chrome 66, this shows the user the general file picker which at least allows them to use the Camera or select from existing photos (although it does allow them to upload files of other mime types).

I did replicate the problem in Chrome Beta as well (version 66.0.3359.106) and tapped "Report" on the dialog that appears, so hopefully some sort of useful trace was submitted. I can perform this again if required.

If there is any further information I can provide to help with debugging this, please let me know.
Screenshot_2018-04-23-20-54-00.png
44.6 KB View Download
Screenshot_2018-04-24-16-30-20.png
60.1 KB View Download

Comment 4 by peter@chromium.org, Apr 26 2018

Cc: -finnur@chromium.org peter@chromium.org
Components: UI
Owner: finnur@chromium.org
That's a crash, and both on fairly old versions of Android. Finnur, could you take a look please?

Comment 5 by peter@chromium.org, Apr 26 2018

Cc: agrieve@chromium.org
Finnur got the device and we just extracted the following stack trace. Is this a duplicate of  Issue 831953 ?

Stack trace:

E/AndroidRuntime(19791): FATAL EXCEPTION: main
E/AndroidRuntime(19791): Process: com.android.chrome:decoder_service, PID: 19791
E/AndroidRuntime(19791): java.lang.RuntimeException: Unable to create service org.chromium.chrome.browser.photo_picker.DecoderService: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean org.chromium.base.CommandLine.hasSwitch(java.lang.String)' on a null object reference
E/AndroidRuntime(19791): 	at android.app.ActivityThread.handleCreateService(ActivityThread.java:3167)
E/AndroidRuntime(19791): 	at android.app.ActivityThread.access$1900(ActivityThread.java:177)
E/AndroidRuntime(19791): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1532)
E/AndroidRuntime(19791): 	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(19791): 	at android.os.Looper.loop(Looper.java:145)
E/AndroidRuntime(19791): 	at android.app.ActivityThread.main(ActivityThread.java:5951)
E/AndroidRuntime(19791): 	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(19791): 	at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(19791): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
E/AndroidRuntime(19791): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)
E/AndroidRuntime(19791): Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean org.chromium.base.CommandLine.hasSwitch(java.lang.String)' on a null object reference
E/AndroidRuntime(19791): 	at org.chromium.base.SysUtils.isLowEndDevice(SysUtils.java:35)
E/AndroidRuntime(19791): 	at org.chromium.base.library_loader.LegacyLinker.ensureInitializedLocked(LegacyLinker.java:11)
E/AndroidRuntime(19791): 	at org.chromium.base.library_loader.LegacyLinker.prepareLibraryLoad(LegacyLinker.java:25)
E/AndroidRuntime(19791): 	at org.chromium.base.library_loader.LibraryLoader.loadAlreadyLocked(LibraryLoader.java:62)
E/AndroidRuntime(19791): 	at org.chromium.base.library_loader.LibraryLoader.ensureInitialized(LibraryLoader.java:17)
E/AndroidRuntime(19791): 	at org.chromium.chrome.browser.photo_picker.DecoderService.onCreate(DecoderService.java:4)
E/AndroidRuntime(19791): 	at android.app.ActivityThread.handleCreateService(ActivityThread.java:3157)
E/AndroidRuntime(19791): 	... 9 more


Comment 6 by finnur@chromium.org, Apr 26 2018

Mergedinto: 831953
Status: Duplicate (was: Assigned)
Thanks mh, very helpful writeup.

I was able to obtain a Samsung Galaxy S4 GT-I9505, running Android 5.0.1.

We verified the crash and the stack matches an issue that is already fixed (see Peter's comment).

We also verified the crash does not occur in Canary. Marking as duplicate.

Comment 7 by m...@trineo.co.nz, Apr 27 2018

Thanks Finnur, we look forward to Chrome 67 being released so that our users can return to a better user experience when uploading photos.

Sign in to add a comment