I'm experiencing something really strange with one of the devices I'm working with.
We've been trying to deploy one of our existing Sencha Touch 2 app on a HP Slate 8 Pro Android tablet. The app itself seems to work fine (at least, it starts properly), however, none of the touch events (touch start, touch move or touch end....nor tap, etc.) are being registered by this device. We basically can't press a button, scroll a list, etc.
The screen is properly responsive since we can tap on a textbox and get the soft keyboard to pop up. So I assumed something was wrong with the bindings...But I can't figure out what exactly.
This app is built with Sencha Touch 2 and Cordova 3.1. In order to eliminate potential sources of issues:
I got rid of Cordova and built the application with the Sencha Native Packager. Behavior persisted.
I got rid of the Sencha Native Packager and built a very simple 1 activity application which loads index.html from the asset folder to the webview. Behavior persisted.
So I started to wonder what exactly could cause this. I tested this last version (lite Android app) in 3 different devices:
A Samsung Galaxy S3 running the latest Cyanogen Mod (Android 4.4.2)
A Galaxy Nexus running Android 4.2.1 (retail)
The HP Slate 8 pro running Android 4.2.2 (probably some HP homebrew fork which so far I blame for the issue...)
First difference is, the user agents:
SGS3 Webview uses:
Mozilla/5.0 (Linux; Android 4.4.2; SAMSUNG-SGH-I747 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/184.108.40.206 Mobile Safari/537.36
The Galaxy Webview uses:
Mozilla/5.0 (Linux; U; Android 4.2.1; en-us; Galaxy Nexus Build/JOP40D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30
The Slate Webview uses:
Mozilla/5.0 (Linux; U; Android 4.2.2; en-us; HP Slate 8 Pro Build/JDQ39) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30
The only difference (excluding the SGS3 using Chrome as a webview which is a new feature of Android KitKat) is that the Slate isn't using a Mobile version of safari. This might be expected since this is a tablet and not a phone. I'm not quite sure if there's a real impact.
Other test I ran was to trace all the events bound on the app startup:
It is possible as we have had a similar issue reported with the HTC One (TOUCH-5193). Unfortunately I do not have access to that particular device to confirm, but I will file a bug and bring this issue to Engineering's attention. Can you send me the code for your simple app.
Originally Posted by freelancer187
Thanks for the quick reply!
I'm using Sencha Touch 2.3.1a.
The app (in web app mode) works just fine (in Chrome). It's only once packaged that I encounter such issue.
I have the same issue in a HP Slate 21 (non pro). We're making an app using the android webview, and it works fine in a Nexus device, as well as several other android 4.1 devices, but this HP Slate 21 (android 4.2.2) does not work. It appears all of the buttons do not accept any input. We've tested on several devices with android 4.1, 4.2, 4.3 and 4.4 and they all work but not this HP Slate 21.
I've tried our own app, and all buttons do not work, but text fields do. Event the little (X) in the text field do not work.
I tried loading the sencha examples through our app's webview as well, and the same behavior with buttons do not work.
We're using sencha touch 2.3.1a, loading the code inside a android Webview, not through the browser or chrome.
After a bit more digging, and debugging with the chrome debugger, in the tablets that work, the button elements have Event Listeners, and the HP Slate 21 does not have event listeners for the same elements.