Chrome OS Claims Activity Exists When It Doesn't
Reported by
mmur...@commonsware.com,
Sep 7 2016
|
|||
Issue descriptionVersion: 54.0.02840.6 dev (64-bit) Platform: 8743.4.0 (Official Build) dev-channel cyan Device: Acer Chromebook R11 C738T Steps to reproduce: On a stock Chrome OS environment, with no PDF viewer app installed, call startActivity() on an ACTION_VIEW Intent pointing to a PDF file. The attached project does this. Expected result: Failure with ActivityNotFoundException. Actual result: The Play Store appears, offering to the user to install Google Drive. Similarly, if you call queryIntentActivities() on PackageManager, with an ACITON_VIEW Intent pointing to a PDF file, you get one match: org.chromium.arc.default_intent.PlayStoreRedirectActivities$PdfActivity. Android apps expect to know, correctly, whether the Android environment can handle certain operations. If the Chrome OS device does not presently have the capability of displaying a PDF, the app may wish to take other steps, or give the user choices of how to proceed. None of that can happen if Chrome OS lies to the app about the availability of a PDF viewer.
,
Sep 12 2016
,
Nov 17 2016
On M53, 54, 55, and older 56, Chrome OS launches Play Store app when ACTION_VIEW+pdf is sent. This is because Android is not really allowed to raise ActivityNotFoundException for that intent for compatibility reasons. On the latest Chrome OS (M56 canary channel), Chrome browser on Chrome OS is actually able to handle ACTION_VIEW+pdf intents, and shows the pdf in the browser. Once M56 hits the stable channel, users won't have the Play Store redirection problem. https://bugs.chromium.org/p/chromium/issues/detail?id=654684 has some more info. Closing this as WAI. |
|||
►
Sign in to add a comment |
|||
Comment 1 by addison@chromium.org
, Sep 8 2016Status: Assigned (was: Untriaged)