GoogleChromeLabs / GoogleChromeLabs/bubblewrap

Should touchscreen user-feature be non-required in manifest

Open
#838 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
3.1k
Forks
319
PR merge metrics
No merged PRs in 30d

Description

I have followed https://chromeos.dev/en/publish/pwa-in-play and wrapped [wide.video](https://wide.video/) PWA using `bubblewrap init --manifest="https://wide.video/manifest.json" --chromeosonly`. Which produces .apk (.aab) I use for submission to play console. The suspicious part is within play console where I can see my app is available on all 68! supported device models (Google Intel Jasper Lake Chromebook, HP Chromebook x2, Google Chromebox... just to name a few).

However, my app is not discoverable in Google Play from a chromebook, nor compatible with some Chromebooks.

I wonder if this has to do something with `android.hardware.touchscreen` as mentioned in:
- https://stackoverflow.com/questions/59175609/how-to-make-android-app-available-on-chromebook-react-native
- https://medium.com/androiddevelopers/get-your-android-app-ready-for-chromebooks-b4915426d021

I have requested Google for any insights as why my app is not compatible with any chromebook when trying to install while claiming compatible with all 68 when checking within play console.

Regarding bubblewrap, should `` feature be added into manifest when `--chromeosonly` was used?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.