Issue metadata
Sign in to add a comment
|
[Chrome][M63][Android 8.0] Chrome is stuck in "Sign in to Chrome" page when opening a text file
Reported by
seiyon.p...@gmail.com,
Jan 15 2018
|
||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Settings > Apps > Chrome > Clear all data, Clear cache 2. Save a text file in the internal storage of device 3. Open a text file with Chrome What is the expected behavior? User can open a text file with Chrome. What went wrong? Chrome is stuck in "Sign in to Chrome" page, so user can't open a text file with Chrome. Did this work before? N/A Chrome version: 63.0.3239.132 Channel: stable OS Version: 8.0 Flash Version:
,
Jan 16 2018
Tested on Pixel Android 8 using reported Chrome #63.0.3239.132 and not able to reproduce the issue by following the below steps: 1. Logged in or not logged into Chrome. 2. Navigate to device settings >> Apps & notifications > Chrome> Storage and tap on "CLEAR CACHE". 3. Try to open a text file from the downloads using Chrome. 4. Observed that user is able to open the text file normally. seiyon.park@ -- Could you please let us know if we have missed anything and provide the screencast of the issue, it would help us in further triaging the issue. Thanks in advance!
,
Jan 17 2018
pnangunoori@, sorry I have not tested it on Pixel Android 8.0 but I have tested it on Nexus5X Android 8.0 and verified it's reproducible. Could you please check it out on Nexus5X Android 8.0?
,
Jan 17 2018
Thank you for providing more feedback. Adding requester "pnangunoori@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
,
Jan 18 2018
,
Jan 18 2018
,
Jan 19 2018
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Launched the Chrome Browser and signin to browser. 2. Download any test file. 3. Navigate to device Settings >> Apps & notifications >> App info >> Chrome >> Storage >> Manage Space >> Tap on “CLEAR ALL DATA”. 4. Navigate to Device Downloads Folder. 5. Long tap on the downloaded file and open with Chrome. 6. On "Welcome to Chrome" screen, tap on "ACCEPT & CONTINUE" button. 7. Tap "NEXT" on "Save data and browse faster" screen. 8. Tap on "NO THANKS" or "CONTINUE" button. 9. Observed that Chrome gets hang and not able to proceed ahead. Observed that, user notices that “Chrome has stopped” alert. Chrome versions tested: 63.0.3239.111(Stable), 65.0.3325.0(Canary), 65.0.3322.0(Dev), 64.0.3282.99(Beta) OS: Android 8.0 Android Devices: Nexus 5X Using the per-revision bisect providing the bisect results, Good Build - 60.0.3111.0 (474651) Bad Build - 60.0.3112.0 (474897) Unable to provide the per-revision bisect as it gave all the results as Good builds. Because, while performing per-revision bisect Chromium builds are launched and when Chromium builds are launched, text file gets directly opened and "Welcome to Chrome" and "Sign into Chrome" screens are not displayed. Please navigate to below link for log's and video-- go/chrome-androidlogs/801948 From the logs providing the following data which could cause the above behavior: 01-19 17:44:49.908 E/DatabaseUtils( 8244): java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/fs_id from pid=23511, uid=10100 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission() 01-19 17:44:49.908 E/DatabaseUtils( 8244): at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:633) 01-19 17:44:49.908 E/DatabaseUtils( 8244): at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:503) 01-19 17:44:49.908 E/DatabaseUtils( 8244): at android.content.ContentProvider$Transport.query(ContentProvider.java:215) 01-19 17:44:49.908 E/DatabaseUtils( 8244): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:102) 01-19 17:44:49.908 E/DatabaseUtils( 8244): at android.os.Binder.execTransact(Binder.java:674) From the GIT Blame results of the above files, following CL could be the suspect. CC'ing the reviewer as Mike is not looking into this now. jbudorick@ -- Could you please look into this issue. Thanks!
,
Jan 19 2018
,
Jan 19 2018
Another closest patch- https://chromium.googlesource.com/chromium/src/+/b522e5fd22c3454dff23fc48b43bafebd160a543 Looping to the Cl owner.
,
Jan 19 2018
Hey, I don't think my linked patch in c#9 caused this. It only really modified the behavior of chrome://sync-internals , which doesn't seem to getting navigated to in the repro steps.
,
Jan 19 2018
Thanks for confirming.
,
Feb 20 2018
Dear Chrome team, kindly pinging.
,
May 3 2018
Dear Chrome team. It's still reproducible on V66. Could you please take a look at this? FYI, bugreport and video on V66 are uploaded.
,
May 11 2018
Dear Chrome team, kindly pinging. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Jan 16 2018