Unanswered: Native packaging and AndroidManifest.xml
I've developed a very simple app in order to test the native packaging functionalities, and the cross-platform capabilities of ST.
On webkit based browsers and iPad 2, the app works as expected, but on Android, either with the stock browser or "native packaging", I find the app to perform in a very slugish/abnormal way.
The taps on tab selectors and buttons have huge lag, and sometimes it even looks as if it skips some taps.
I've read other threads describing similar behaviors, and suggesting to edit the AndriodManifest.xml to enable hardware acceleration, but I was wandering how one could do that using the native packaging functionality.
The senchadevelopers blog states that in version 2.1 it would be possible:
"The packager config also lets you pass in "raw" data to the iOS info.plist and Android AndroidManifest.xml through the rawConfig key."
But then on ST 2.1 documentation:
"rawConfig (iOS only)"
Shall I just forget the native packaging until it is more mature?
Sencha Premium Member
I want to add custom scheme url for my android app, can't figure out how to do it on my own. Docs are iOS only.
Tags for this Thread