ok - so we got feedback on Chromebooks from Google Play. We then tried it using an Acer R11. Here is the outcome:
Good News:
Our app does run, even prior to the change in permission as indicated in the link
Bad News/Problems:
-
We have a place in our game, where you need to enter a number into a native textfield. When the player tries to enter information into the text field, if the user tries to click into the textfield then type, it won’t allow user to enter any text. However, if the user where to tap on the textfield first (on the touch screen), then the user CAN enter text as you would expect. This problem continued to exist even after we set the android.hardware.touchscreen flag.
-
Another weird problem we ran into is that when we resize the window on Chrome, the game restarts. Here are the words from Google, which we fully observed:
When reviewing the title on Chromebooks, problems were observed while resizing the app window (switching between portrait or landscape orientations, or transitioning between windowed and maximized sizes):
• App/game restarts upon resizing, causing user to lose progress
Apps should handle dynamic window resizing by utilizing onConfigChange and the android:configChanges=“ScreenSize” activity element, or by supporting Android N multi-window resizing. For more info: https://developer.android.com/topic/arc/index.html#leverage , https://developer.android.com/guide/topics/ui/multi-window.html
- Lastly, our game didn’t scale properly when user changes the aspect ratio on the window. I am wondering if there is a way to LOCK the aspect ratio on Chromebooks such that even as the player resizes the window, the UI won’t break…
I think we’ll need someone from Corona to weigh in to sort out some of these stuff.
