New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android 4.4 support for Legacy Android #35

Closed
satusuuronen opened this Issue Dec 19, 2013 · 98 comments

Comments

Projects
None yet
@satusuuronen
Contributor

satusuuronen commented Dec 19, 2013

Currently, the Android Scanner app and consequently stand-alone builds of Steroids apps do not work on Android 4.4.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Dec 31, 2013

well I still have the scanner since I updated from 4.3 to 4.4.2, and I added the following and my app started to work again:

html, body {
background: #fff;
}

also this github issue should not be labelled as a feature but as a bug

rohanbhangui commented Dec 31, 2013

well I still have the scanner since I updated from 4.3 to 4.4.2, and I added the following and my app started to work again:

html, body {
background: #fff;
}

also this github issue should not be labelled as a feature but as a bug

@munvier

This comment has been minimized.

Show comment
Hide comment
@munvier

munvier Jan 2, 2014

+1 to the bug label ! this is really really important for android apps because they can't be deployed right now ...
Is there any date on release ? or at least, have you identified the bug source ?

munvier commented Jan 2, 2014

+1 to the bug label ! this is really really important for android apps because they can't be deployed right now ...
Is there any date on release ? or at least, have you identified the bug source ?

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 2, 2014

if you need the scanner apk i can get that to anyone, just request. @munvier if you check the steroids js forum you can get updates on the status. Right now the issue is 2 part from what I understand: 1. nexus 7 devices cannot install the scanner (possibly fixed by now) and 2. android kitkat is not supported yet. With the latter the issue is that the loading.png loads and somehow "disables" the stylesheet (there by remaining as the background for the app). But using the css fix i used above, this problem gets fixed (atleast for me). I have posted that solution in the steroids js forums although I expect that the fix that the steroids js team is looking for is a comprehensive solution rather than a hack. Check the forums for the latests. Usually more active.

rohanbhangui commented Jan 2, 2014

if you need the scanner apk i can get that to anyone, just request. @munvier if you check the steroids js forum you can get updates on the status. Right now the issue is 2 part from what I understand: 1. nexus 7 devices cannot install the scanner (possibly fixed by now) and 2. android kitkat is not supported yet. With the latter the issue is that the loading.png loads and somehow "disables" the stylesheet (there by remaining as the background for the app). But using the css fix i used above, this problem gets fixed (atleast for me). I have posted that solution in the steroids js forums although I expect that the fix that the steroids js team is looking for is a comprehensive solution rather than a hack. Check the forums for the latests. Usually more active.

@munvier

This comment has been minimized.

Show comment
Hide comment
@munvier

munvier Jan 2, 2014

Ok thanks a lot ! i'll try your fix, i can install the app on 4.4 with no issue. the problem i had is the css disabled... i'll keep you in touch. on the forum ;)

munvier commented Jan 2, 2014

Ok thanks a lot ! i'll try your fix, i can install the app on 4.4 with no issue. the problem i had is the css disabled... i'll keep you in touch. on the forum ;)

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 2, 2014

Sure good luck! Its weird that steroids would have a random bug like this. I have spoken with one of the admins, we (android users) should be getting a lot of android features some of which are only available for iOS dev using steroids

rohanbhangui commented Jan 2, 2014

Sure good luck! Its weird that steroids would have a random bug like this. I have spoken with one of the admins, we (android users) should be getting a lot of android features some of which are only available for iOS dev using steroids

@munvier

This comment has been minimized.

Show comment
Hide comment
@munvier

munvier Jan 2, 2014

perfect! android so far clearly miss some features but it seems promiseful!

munvier commented Jan 2, 2014

perfect! android so far clearly miss some features but it seems promiseful!

@harsaharsa

This comment has been minimized.

Show comment
Hide comment
@harsaharsa

harsaharsa Jan 2, 2014

Member

Updated to bug label, thanks for the feedback! On some of our Android 4.4 test devices, there were more issues than just the CSS bugging out (i.e. it just wasn't working at all), so we dropped official support for 4.4 until we can be sure that it works as intended.

The transparent CSS background issue is actually something that affects earlier Android versions too, see #19 for discussion.

Member

harsaharsa commented Jan 2, 2014

Updated to bug label, thanks for the feedback! On some of our Android 4.4 test devices, there were more issues than just the CSS bugging out (i.e. it just wasn't working at all), so we dropped official support for 4.4 until we can be sure that it works as intended.

The transparent CSS background issue is actually something that affects earlier Android versions too, see #19 for discussion.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 2, 2014

@harsaharsa well that last issue is fixed using my fix, maybe a temp solution if your backlog is a lot?

rohanbhangui commented Jan 2, 2014

@harsaharsa well that last issue is fixed using my fix, maybe a temp solution if your backlog is a lot?

@patrickmarabeas

This comment has been minimized.

Show comment
Hide comment
@patrickmarabeas

patrickmarabeas Jan 4, 2014

@rohanbhangui could I grab the .apk? Just upgraded from 2.2 to 4.4 - couldn't believe my device was still incompatible!

patrickmarabeas commented Jan 4, 2014

@rohanbhangui could I grab the .apk? Just upgraded from 2.2 to 4.4 - couldn't believe my device was still incompatible!

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 4, 2014

@patrickmarabeas ya hold up post a link for it

rohanbhangui commented Jan 4, 2014

@patrickmarabeas ya hold up post a link for it

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@patrickmarabeas

This comment has been minimized.

Show comment
Hide comment
@patrickmarabeas

patrickmarabeas commented Jan 4, 2014

@rohanbhangui awesome, thanks : )

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui commented Jan 4, 2014

np

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 4, 2014

@patrickmarabeas what I did was i installed on 4.3 and then updated to 4.4.2

rohanbhangui commented Jan 4, 2014

@patrickmarabeas what I did was i installed on 4.3 and then updated to 4.4.2

@munvier

This comment has been minimized.

Show comment
Hide comment
@munvier

munvier Jan 10, 2014

If it can help, i've deleted any reference to any "localhost" value and it seems to work.

ex :
<script src="http://localhost/javascripts/menu.js"></script> is transformed in <script src="javascripts/menu.js"></script>

Same thing for the css file and all the assets that are loaded with it (fonts hosted in the app, svg).

I don't know if it can help people. I'm gonna give it another try. I'll keep you posted.

munvier commented Jan 10, 2014

If it can help, i've deleted any reference to any "localhost" value and it seems to work.

ex :
<script src="http://localhost/javascripts/menu.js"></script> is transformed in <script src="javascripts/menu.js"></script>

Same thing for the css file and all the assets that are loaded with it (fonts hosted in the app, svg).

I don't know if it can help people. I'm gonna give it another try. I'll keep you posted.

@JoaoSaleiro

This comment has been minimized.

Show comment
Hide comment
@JoaoSaleiro

JoaoSaleiro Jan 10, 2014

Can you please provide a link for the 3.1.1 version of the scanner? I would like to try some of the above hacks in my nexus 5, to see if I can temporarily hack the problem around. Currently, I only have an android 4.4 with me, and an app to finish in less than a week, so my hands are tied... :o)

JoaoSaleiro commented Jan 10, 2014

Can you please provide a link for the 3.1.1 version of the scanner? I would like to try some of the above hacks in my nexus 5, to see if I can temporarily hack the problem around. Currently, I only have an android 4.4 with me, and an app to finish in less than a week, so my hands are tied... :o)

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@JoaoSaleiro that scanner will work on android 4.4.2, it works on my nexus 4. That scanner was actually downloaded pre android kitkat

rohanbhangui commented Jan 10, 2014

@JoaoSaleiro that scanner will work on android 4.4.2, it works on my nexus 4. That scanner was actually downloaded pre android kitkat

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@munvier ya i noticed that but that could mess around with other stuff so I kept that value as is

rohanbhangui commented Jan 10, 2014

@munvier ya i noticed that but that could mess around with other stuff so I kept that value as is

@JoaoSaleiro

This comment has been minimized.

Show comment
Hide comment
@JoaoSaleiro

JoaoSaleiro Jan 10, 2014

@rohanbhangui weird, in my nexus 5 it gets stuck at the appgyver logo

JoaoSaleiro commented Jan 10, 2014

@rohanbhangui weird, in my nexus 5 it gets stuck at the appgyver logo

@munvier

This comment has been minimized.

Show comment
Hide comment
@munvier

munvier Jan 10, 2014

@rohanbhangui ok ! my app is very basic and doesn't need plugins or so. I just use the webviews and it works, i was just giving a tip for people in my situation :)

munvier commented Jan 10, 2014

@rohanbhangui ok ! my app is very basic and doesn't need plugins or so. I just use the webviews and it works, i was just giving a tip for people in my situation :)

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@munvier ya i guess. Though I find my hack a bit more safe. Anyways, all this won't matter when the steroidsjs team get their stuff in line.

rohanbhangui commented Jan 10, 2014

@munvier ya i guess. Though I find my hack a bit more safe. Anyways, all this won't matter when the steroidsjs team get their stuff in line.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@JoaoSaleiro hmmmmm. try to reinstall clear mem etc.

rohanbhangui commented Jan 10, 2014

@JoaoSaleiro hmmmmm. try to reinstall clear mem etc.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@JoaoSaleiro you could probably get the github source roll back to a previous version and recompile as apk, i mean everything is version controlled

rohanbhangui commented Jan 10, 2014

@JoaoSaleiro you could probably get the github source roll back to a previous version and recompile as apk, i mean everything is version controlled

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

wait wtf there is no source? damn it!

rohanbhangui commented Jan 10, 2014

wait wtf there is no source? damn it!

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@harsaharsa you mind putting the scanner files under version control so that some of us can recompile perhaps older version of the scanner?

rohanbhangui commented Jan 10, 2014

@harsaharsa you mind putting the scanner files under version control so that some of us can recompile perhaps older version of the scanner?

@abulte

This comment has been minimized.

Show comment
Hide comment
@abulte

abulte Jan 10, 2014

Same problem here on Android 4.4.2, CSS fix is not working. The only thing that works is to remove the doctype declaration in HTML, but of course it is not an acceptable or cross-platform solution.

abulte commented Jan 10, 2014

Same problem here on Android 4.4.2, CSS fix is not working. The only thing that works is to remove the doctype declaration in HTML, but of course it is not an acceptable or cross-platform solution.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@abulte its fine for now, try my css hack above

rohanbhangui commented Jan 10, 2014

@abulte its fine for now, try my css hack above

@abulte

This comment has been minimized.

Show comment
Hide comment
@abulte

abulte Jan 10, 2014

nope @rohanbhangui, like I said the CSS hack is not working for me.

abulte commented Jan 10, 2014

nope @rohanbhangui, like I said the CSS hack is not working for me.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@abulte hmmm interesting, could it be that we have different version of steroidsjs ?

rohanbhangui commented Jan 10, 2014

@abulte hmmm interesting, could it be that we have different version of steroidsjs ?

@abulte

This comment has been minimized.

Show comment
Hide comment
@abulte

abulte Jan 10, 2014

@rohanbhangui I'm on AppGyver Steroids 3.1.12, test device is a Nexus 4 running Android 4.4.2.

It's not a surprise that the CSS hack is not working, since my custom CSS are not loaded at all (I've seen the same problem described in Steroids forums, tried some other hacks with no luck). The only thing that works is to remove the doctype declaration.

abulte commented Jan 10, 2014

@rohanbhangui I'm on AppGyver Steroids 3.1.12, test device is a Nexus 4 running Android 4.4.2.

It's not a surprise that the CSS hack is not working, since my custom CSS are not loaded at all (I've seen the same problem described in Steroids forums, tried some other hacks with no luck). The only thing that works is to remove the doctype declaration.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 10, 2014

@abulte i think steroids js may be at a later version

rohanbhangui commented Jan 10, 2014

@abulte i think steroids js may be at a later version

@DallanQ

This comment has been minimized.

Show comment
Hide comment
@DallanQ

DallanQ Jan 22, 2014

+1 for getting the scanner app working on 4.4, or supporting the android emmulator, or both ideally

DallanQ commented Jan 22, 2014

+1 for getting the scanner app working on 4.4, or supporting the android emmulator, or both ideally

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 22, 2014

@DallanQ so has the bug been resolved with an update of some kind or some of the above hacks worked?

rohanbhangui commented Jan 22, 2014

@DallanQ so has the bug been resolved with an update of some kind or some of the above hacks worked?

@DallanQ

This comment has been minimized.

Show comment
Hide comment
@DallanQ

DallanQ Jan 22, 2014

Not for me, that's why I'm encouraging AppGyver to get the scanner app working on 4.4.2 or supporting the android emulator (or both)

DallanQ commented Jan 22, 2014

Not for me, that's why I'm encouraging AppGyver to get the scanner app working on 4.4.2 or supporting the android emulator (or both)

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui commented Jan 22, 2014

true

@patrickmarabeas

This comment has been minimized.

Show comment
Hide comment
@patrickmarabeas

patrickmarabeas Jan 23, 2014

So the linked scanner runs on my Nexus 5, but the apps themselves are completely broken. None of the phonegap/steroids API work (testing with the tutorial project).

Thought major updates were due months ago for Android...?

patrickmarabeas commented Jan 23, 2014

So the linked scanner runs on my Nexus 5, but the apps themselves are completely broken. None of the phonegap/steroids API work (testing with the tutorial project).

Thought major updates were due months ago for Android...?

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 23, 2014

@patrickmarabeas look at one of the hacks i posted see if that helps

rohanbhangui commented Jan 23, 2014

@patrickmarabeas look at one of the hacks i posted see if that helps

@patrickmarabeas

This comment has been minimized.

Show comment
Hide comment
@patrickmarabeas

patrickmarabeas Jan 23, 2014

@rohanbhangui Push to device on update doesn't even work dude. CSS issue only happens on some of the tutorial examples. Otherwise the API is completely dead.

"On some of our Android 4.4 test devices, there were more issues than just the CSS bugging out (i.e. it just wasn't working at all)" - harsaharsa

patrickmarabeas commented Jan 23, 2014

@rohanbhangui Push to device on update doesn't even work dude. CSS issue only happens on some of the tutorial examples. Otherwise the API is completely dead.

"On some of our Android 4.4 test devices, there were more issues than just the CSS bugging out (i.e. it just wasn't working at all)" - harsaharsa

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 23, 2014

Ya I know they are trying to solve it

rohanbhangui commented Jan 23, 2014

Ya I know they are trying to solve it

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Jan 23, 2014

@patrickmarabeas they have a huge backlog from what I understand a lot of new features are on the way. They had to update to the new cordova recently and they are working on sim. tools for android. They are also working on native components for android. Right if I understand correctly, what ever is on iOS they are trying to replicate on android to level the playing field

rohanbhangui commented Jan 23, 2014

@patrickmarabeas they have a huge backlog from what I understand a lot of new features are on the way. They had to update to the new cordova recently and they are working on sim. tools for android. They are also working on native components for android. Right if I understand correctly, what ever is on iOS they are trying to replicate on android to level the playing field

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Feb 7, 2014

@patrickmarabeas @osusoy for these reason (constant bugs, etc.) I have moved to native and although some stuff is harder for the most part, stuff seems logical and very fast.

@harsaharsa I am not trying to convince users away from steroids, I just think with the problems that hybrid apps still have to face, it is much better to do native dev as compared to hybrid dev.

rohanbhangui commented Feb 7, 2014

@patrickmarabeas @osusoy for these reason (constant bugs, etc.) I have moved to native and although some stuff is harder for the most part, stuff seems logical and very fast.

@harsaharsa I am not trying to convince users away from steroids, I just think with the problems that hybrid apps still have to face, it is much better to do native dev as compared to hybrid dev.

@osusoy

This comment has been minimized.

Show comment
Hide comment
@osusoy

osusoy Feb 7, 2014

@rohanbhangui agreed. it is not just steroids, hybrid development in general seems to always be fairly dodgy but i was really hoping this was going to be an exception. in my case, the client wanted to have a shot at steroids to save some time and money so we did and now we've spent so much time and money on it (would have finished at least one native by now) that it is almost impossible to change direction, just need to soldier on working with the community and trying to find workarounds and solutions. of course my app design is now pretty much completely based on what actually works on steroids rather than what my client or i might want so feeling a bit disappointed with myself for not rejecting the platform choice earlier when there was a chance.

with the new update, my app now doesn't work properly on 4.3 either (not even the ad hoc builds, its not completely broken but looks like it needs a fair bit of debugging) so work i have done that had passed UAT previously will be failing at the current sprint's UAT :(

i guess just complaining about it won't fix the problem, @harsaharsa do you have any questions for us to help you figure out where the problems are or are you already aware of all the issues?

osusoy commented Feb 7, 2014

@rohanbhangui agreed. it is not just steroids, hybrid development in general seems to always be fairly dodgy but i was really hoping this was going to be an exception. in my case, the client wanted to have a shot at steroids to save some time and money so we did and now we've spent so much time and money on it (would have finished at least one native by now) that it is almost impossible to change direction, just need to soldier on working with the community and trying to find workarounds and solutions. of course my app design is now pretty much completely based on what actually works on steroids rather than what my client or i might want so feeling a bit disappointed with myself for not rejecting the platform choice earlier when there was a chance.

with the new update, my app now doesn't work properly on 4.3 either (not even the ad hoc builds, its not completely broken but looks like it needs a fair bit of debugging) so work i have done that had passed UAT previously will be failing at the current sprint's UAT :(

i guess just complaining about it won't fix the problem, @harsaharsa do you have any questions for us to help you figure out where the problems are or are you already aware of all the issues?

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Feb 7, 2014

@osusoy in the long run, hybrid at the moment, does not save time more money. While it is good for quick prototyping if you want something robust and sustainable then its best to go native. I have found in many cases native dev to be very similar to html/css in the fact that xml and html are like cousins. I highly recommend that if your client does not mind going the extra mile you look into native. You may think hybrid saves time but it doesn't. You will pay the price somewhere when you work on hybrid apps. Having said that, I know I have mentioned it before, but maybe one of the above tricks may help. Also try to look through the compiled code. For example, the loading.png and loading.html do not exist in my projects. I removed them from them.

@harsaharsa And like @osusoy if there is anything on our side that we can do to help please let us know. The idea is to resolve this as soon as possible. I have great hope in steroids and I think it will become a formidable opponent to native in the coming months. Also appgyver should look into getting as many features currently available in phonegap (ie. os compatibility, etc.) as possible.

rohanbhangui commented Feb 7, 2014

@osusoy in the long run, hybrid at the moment, does not save time more money. While it is good for quick prototyping if you want something robust and sustainable then its best to go native. I have found in many cases native dev to be very similar to html/css in the fact that xml and html are like cousins. I highly recommend that if your client does not mind going the extra mile you look into native. You may think hybrid saves time but it doesn't. You will pay the price somewhere when you work on hybrid apps. Having said that, I know I have mentioned it before, but maybe one of the above tricks may help. Also try to look through the compiled code. For example, the loading.png and loading.html do not exist in my projects. I removed them from them.

@harsaharsa And like @osusoy if there is anything on our side that we can do to help please let us know. The idea is to resolve this as soon as possible. I have great hope in steroids and I think it will become a formidable opponent to native in the coming months. Also appgyver should look into getting as many features currently available in phonegap (ie. os compatibility, etc.) as possible.

@harsaharsa

This comment has been minimized.

Show comment
Hide comment
@harsaharsa

harsaharsa Feb 11, 2014

Member

Thanks to everyone for the comments and discussion! We really appreciate the community's spirit, and we'll work on making contributing easier. Suggestions on how to do this are welcome (although the native runtime stuff is going to stay closed-source for the time being – sorry guys)! Also, we have a ton of open-source components that would love some pull requests – the same people here are working on the native side stuff and those components, so any contributions there will help us allocate resources to fix native-side issues.

Now, on to Android 4.4. The issue you're experiencing with the current 4.4 support is that requests to http://localhost/ fail, seemingly pretty randomly – thus leading to nonfunctional JavaScript, CSS not loading etc.

It works if you are serving stuff via the File protocol (i.e. steroids.config.location = "index.html" instead of steroids.config.location = "http://localhost/index.html" and src="images/dolan.png" instead of src="/images/dolan.png"). However, given that cordova.js is loaded from localhost and Steroids apps are generally meant to work on localhost, it's pretty unusable at the moment.

Now, we could keep the limited 4.4 support available, but with the current Build Service architecture, that would mean that apps meant to work on 4.3 and lower would still be available for 4.4, but not functioning as intended.

Thus, we are rolling out a hotfix for the Build Service today that will disable the 4.4 support while we work to get the localhost issue fixed. I'll give you more details as we make progress. I know it's disappointing, but we're committed to 4.4 support, and it's coming as soon as possible.

(For those interested, the reason for putting out a non-functioning version was an unfortunate accumulation of human errors and process mishaps on our end – we thought the localhost bug was squashed in the version that went out, but it turned out it wasn't. We've taken necessary steps to ensure this sort of situation won't happen again.)

Member

harsaharsa commented Feb 11, 2014

Thanks to everyone for the comments and discussion! We really appreciate the community's spirit, and we'll work on making contributing easier. Suggestions on how to do this are welcome (although the native runtime stuff is going to stay closed-source for the time being – sorry guys)! Also, we have a ton of open-source components that would love some pull requests – the same people here are working on the native side stuff and those components, so any contributions there will help us allocate resources to fix native-side issues.

Now, on to Android 4.4. The issue you're experiencing with the current 4.4 support is that requests to http://localhost/ fail, seemingly pretty randomly – thus leading to nonfunctional JavaScript, CSS not loading etc.

It works if you are serving stuff via the File protocol (i.e. steroids.config.location = "index.html" instead of steroids.config.location = "http://localhost/index.html" and src="images/dolan.png" instead of src="/images/dolan.png"). However, given that cordova.js is loaded from localhost and Steroids apps are generally meant to work on localhost, it's pretty unusable at the moment.

Now, we could keep the limited 4.4 support available, but with the current Build Service architecture, that would mean that apps meant to work on 4.3 and lower would still be available for 4.4, but not functioning as intended.

Thus, we are rolling out a hotfix for the Build Service today that will disable the 4.4 support while we work to get the localhost issue fixed. I'll give you more details as we make progress. I know it's disappointing, but we're committed to 4.4 support, and it's coming as soon as possible.

(For those interested, the reason for putting out a non-functioning version was an unfortunate accumulation of human errors and process mishaps on our end – we thought the localhost bug was squashed in the version that went out, but it turned out it wasn't. We've taken necessary steps to ensure this sort of situation won't happen again.)

@Pixelworlds

This comment has been minimized.

Show comment
Hide comment
@Pixelworlds

Pixelworlds Feb 12, 2014

harsaharsa - thank you for the update

Pixelworlds commented Feb 12, 2014

harsaharsa - thank you for the update

@azizimusa

This comment has been minimized.

Show comment
Hide comment
@azizimusa

azizimusa Feb 17, 2014

looking forward for the update.
-nexus 5 user

azizimusa commented Feb 17, 2014

looking forward for the update.
-nexus 5 user

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Feb 17, 2014

I think one of the biggest challenges/tasks that steroids needs to undertake is matching phonegap when it comes to device/OS compatibility

rohanbhangui commented Feb 17, 2014

I think one of the biggest challenges/tasks that steroids needs to undertake is matching phonegap when it comes to device/OS compatibility

@sandros87

This comment has been minimized.

Show comment
Hide comment
@sandros87

sandros87 Feb 18, 2014

I was ready to build my first app with steroids (reading that phonegapp apps don't feel native) but finding this issue was really a major bummer! Even because the Nexus's devices I target all run KitKat and I only have one device to test that of course is on KitKat :(

sandros87 commented Feb 18, 2014

I was ready to build my first app with steroids (reading that phonegapp apps don't feel native) but finding this issue was really a major bummer! Even because the Nexus's devices I target all run KitKat and I only have one device to test that of course is on KitKat :(

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Feb 18, 2014

@harsaharsa sry to confirm has the issue been resolved? And when can we expect an update to the scanner app?

rohanbhangui commented Feb 18, 2014

@harsaharsa sry to confirm has the issue been resolved? And when can we expect an update to the scanner app?

@sandros87

This comment has been minimized.

Show comment
Hide comment
@sandros87

sandros87 Feb 18, 2014

@rohanbhangui AFAIK even if they resolve the issue with the CSS not loading you still left with the sluggishness on KitKat 4.4. That's Google's fault and they have to fix it not the steroids team! https://code.google.com/p/chromium/issues/detail?id=315111

sandros87 commented Feb 18, 2014

@rohanbhangui AFAIK even if they resolve the issue with the CSS not loading you still left with the sluggishness on KitKat 4.4. That's Google's fault and they have to fix it not the steroids team! https://code.google.com/p/chromium/issues/detail?id=315111

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Feb 18, 2014

@sandros87 true, thanks for that link! :)

rohanbhangui commented Feb 18, 2014

@sandros87 true, thanks for that link! :)

@harsaharsa

This comment has been minimized.

Show comment
Hide comment
@harsaharsa

harsaharsa Feb 19, 2014

Member

@rohanbhangui we basically know what's wrong and needs fixing, but the work is still in progress. I'll keep this thread updated, no worries! We want to make sure the 4.4 support is as complete as possible before releasing it – we don't e.g. want to have users find out their app is available and broken on 4.4 when they've only tested it with earlier versions of Android before releasing it to Google Play.

Member

harsaharsa commented Feb 19, 2014

@rohanbhangui we basically know what's wrong and needs fixing, but the work is still in progress. I'll keep this thread updated, no worries! We want to make sure the 4.4 support is as complete as possible before releasing it – we don't e.g. want to have users find out their app is available and broken on 4.4 when they've only tested it with earlier versions of Android before releasing it to Google Play.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Feb 19, 2014

@harsaharsa thanks for the update looking forward to a fix!

rohanbhangui commented Feb 19, 2014

@harsaharsa thanks for the update looking forward to a fix!

@WassimHakim

This comment has been minimized.

Show comment
Hide comment
@WassimHakim

WassimHakim Feb 19, 2014

looking forward for a fix. It's embarrassing having built a mobile app that doesn't work on the phone you are using (Nexus 5)

Keep us updated please

WassimHakim commented Feb 19, 2014

looking forward for a fix. It's embarrassing having built a mobile app that doesn't work on the phone you are using (Nexus 5)

Keep us updated please

@harsaharsa harsaharsa removed this from the Android 3.1.2 release milestone Feb 19, 2014

@andrewlively

This comment has been minimized.

Show comment
Hide comment
@andrewlively

andrewlively Feb 25, 2014

Hey @harsaharsa any chance we can get an progress update? I've got a client that doesn't understand how it can work perfectly on iOS and not at all on Android after this latest update, and have made it clear they are not happy about it, and I was hoping to give them even just a rough timeframe. Thanks!

andrewlively commented Feb 25, 2014

Hey @harsaharsa any chance we can get an progress update? I've got a client that doesn't understand how it can work perfectly on iOS and not at all on Android after this latest update, and have made it clear they are not happy about it, and I was hoping to give them even just a rough timeframe. Thanks!

@harsaharsa

This comment has been minimized.

Show comment
Hide comment
@harsaharsa

harsaharsa Feb 27, 2014

Member

So, an update for everybody!

After looking at it long and hard, the localhost issue looks like it's very nasty to fix on the existing codebase. Thus, we've been focusing on getting the new, rebuilt-from-ground-up Android client out. It'll support 4.4 with minimal native UI features when it's first released, after which we'll do our best to catch up with the existing Android client's functionalities in terms of platform support and Steroids Native UI features, releasing new versions frequently. I can't promise any timeframe yet (though, weeks instead of months would be my current gut feeling), but I'll let you know the instant we have something viable running in-house – we're doing extensive RND first to make sure we get the whole thing right from the get-go.

It's a tough decision on where to focus our efforts, but we want to get to the point where Android is completely "fixed" ASAP. So, it'll probably be a while longer before you can get your whole existing codebase to run on 4.4 (since the new client will be missing Steroids API calls at first). If it's top priority for you to get a 4.4-compatible version out ASAP, you can prepare for immediate deployment by making your app use as few Steroids Native UI features as possible (really backwards, I know, sorry!), possibly restructuring it as a single-page application (though layers.push will likely be the first Steroids feature we implement after getting the basic thing running).

Note that we might still end up fixing the 4.4 support for the current Android client at some point, so keep informing us of client pressure etc – we are listening to your comments!

Member

harsaharsa commented Feb 27, 2014

So, an update for everybody!

After looking at it long and hard, the localhost issue looks like it's very nasty to fix on the existing codebase. Thus, we've been focusing on getting the new, rebuilt-from-ground-up Android client out. It'll support 4.4 with minimal native UI features when it's first released, after which we'll do our best to catch up with the existing Android client's functionalities in terms of platform support and Steroids Native UI features, releasing new versions frequently. I can't promise any timeframe yet (though, weeks instead of months would be my current gut feeling), but I'll let you know the instant we have something viable running in-house – we're doing extensive RND first to make sure we get the whole thing right from the get-go.

It's a tough decision on where to focus our efforts, but we want to get to the point where Android is completely "fixed" ASAP. So, it'll probably be a while longer before you can get your whole existing codebase to run on 4.4 (since the new client will be missing Steroids API calls at first). If it's top priority for you to get a 4.4-compatible version out ASAP, you can prepare for immediate deployment by making your app use as few Steroids Native UI features as possible (really backwards, I know, sorry!), possibly restructuring it as a single-page application (though layers.push will likely be the first Steroids feature we implement after getting the basic thing running).

Note that we might still end up fixing the 4.4 support for the current Android client at some point, so keep informing us of client pressure etc – we are listening to your comments!

@benadamstyles

This comment has been minimized.

Show comment
Hide comment
@benadamstyles

benadamstyles Feb 28, 2014

I'm sure the answer is no but just to be absolutely clear - are our Google Play builds currently available/visible to 4.4 devices or not?

benadamstyles commented Feb 28, 2014

I'm sure the answer is no but just to be absolutely clear - are our Google Play builds currently available/visible to 4.4 devices or not?

@harsaharsa

This comment has been minimized.

Show comment
Hide comment
@harsaharsa

harsaharsa Mar 3, 2014

Member

@Leeds-eBooks – you are correct, Google Play builds are currently available/visible only for Android v3.0-4.3.

Member

harsaharsa commented Mar 3, 2014

@Leeds-eBooks – you are correct, Google Play builds are currently available/visible only for Android v3.0-4.3.

@jamespeerless

This comment has been minimized.

Show comment
Hide comment
@jamespeerless

jamespeerless Mar 7, 2014

Our application is a SPA that does not use any of the steroids api (it does use a couple cordova plugins + api) but we are currently primarily only using steroids as a build/deploy system. How easy is it for us to get a 4.4 build from our current deployment?

jamespeerless commented Mar 7, 2014

Our application is a SPA that does not use any of the steroids api (it does use a couple cordova plugins + api) but we are currently primarily only using steroids as a build/deploy system. How easy is it for us to get a 4.4 build from our current deployment?

@andrewlively

This comment has been minimized.

Show comment
Hide comment
@andrewlively

andrewlively Mar 7, 2014

We just went through the process of removing all Steroids API stuff from our Android version to use only Cordova, and it took us about 3 days with 2 developers working part-time on it. Our app is not a SPA however, which we are probably going to rewrite and make it that way, and did rely on a couple Steroids features, so reworking those is what took the majority of our time. But what's nice is since Steroids is compatible with Cordova it should be a pretty simple process for you. Just make sure that you use Cordova 3.3+, we used the latest 3.4, because that is when they added support for Android 4.4. The way we did it is created a 'Hello World' project with Cordova, dropped in files from original www directory into new www directory, added in any plugins we needed (none are included by default), and then tested it out. If that is the route you decide to go then the cordova documentation will be your best friend for the next couple days.

andrewlively commented Mar 7, 2014

We just went through the process of removing all Steroids API stuff from our Android version to use only Cordova, and it took us about 3 days with 2 developers working part-time on it. Our app is not a SPA however, which we are probably going to rewrite and make it that way, and did rely on a couple Steroids features, so reworking those is what took the majority of our time. But what's nice is since Steroids is compatible with Cordova it should be a pretty simple process for you. Just make sure that you use Cordova 3.3+, we used the latest 3.4, because that is when they added support for Android 4.4. The way we did it is created a 'Hello World' project with Cordova, dropped in files from original www directory into new www directory, added in any plugins we needed (none are included by default), and then tested it out. If that is the route you decide to go then the cordova documentation will be your best friend for the next couple days.

@kcivey

This comment has been minimized.

Show comment
Hide comment
@kcivey

kcivey Mar 12, 2014

I just found out about AppGyver, and everything looked great, but this bug seems like a real show stopper that takes away most of my reasons for trying it out. It may be months before I can do development on Android? Really? It's all well and good to say to avoid Steroids Native UI features, but that wouldn't solve the problem of not being to preview the app during development. Am I missing something, or is AppGyver basically useless to me right now?

kcivey commented Mar 12, 2014

I just found out about AppGyver, and everything looked great, but this bug seems like a real show stopper that takes away most of my reasons for trying it out. It may be months before I can do development on Android? Really? It's all well and good to say to avoid Steroids Native UI features, but that wouldn't solve the problem of not being to preview the app during development. Am I missing something, or is AppGyver basically useless to me right now?

@naartjie

This comment has been minimized.

Show comment
Hide comment
@naartjie

naartjie Mar 13, 2014

It was a sad day when I found this thread. Right now AppGyver is an
enhanced PhoneGap for iPhone only. It is a great product, but unfortunately
it's taken away "cross-platform" promise (until further notice).

On Wed, Mar 12, 2014 at 10:45 PM, Keith C. Ivey notifications@github.comwrote:

I just found out about AppGyver, and everything looked great, but this bug
seems like a real show stopper that takes away most of my reasons for
trying it out. It may be months before I can do development on Android?
Really? It's all well and good to say to avoid Steroids Native UI features,
but that wouldn't solve the problem of not being to preview the app during
development. Am I missing something, or is AppGyver basically useless to me
right now?


Reply to this email directly or view it on GitHubhttps://github.com/AppGyver/wrapper/issues/35#issuecomment-37462305
.

naartjie commented Mar 13, 2014

It was a sad day when I found this thread. Right now AppGyver is an
enhanced PhoneGap for iPhone only. It is a great product, but unfortunately
it's taken away "cross-platform" promise (until further notice).

On Wed, Mar 12, 2014 at 10:45 PM, Keith C. Ivey notifications@github.comwrote:

I just found out about AppGyver, and everything looked great, but this bug
seems like a real show stopper that takes away most of my reasons for
trying it out. It may be months before I can do development on Android?
Really? It's all well and good to say to avoid Steroids Native UI features,
but that wouldn't solve the problem of not being to preview the app during
development. Am I missing something, or is AppGyver basically useless to me
right now?


Reply to this email directly or view it on GitHubhttps://github.com/AppGyver/wrapper/issues/35#issuecomment-37462305
.

@rafalohn

This comment has been minimized.

Show comment
Hide comment
@rafalohn

rafalohn Mar 17, 2014

@harsaharsa you asked to be informed of client pressure. My app is ready, my client wants to release it. This week. I've been asking in the forum constantly.

The only plugin I use is 'Media'. I have only one steroids.layers.push outside my main page, and I can probably live without it. What I really need is support up to the current Android 4.4, ideally, the same apk to support from 2.3 up. Unfortunately I am not ready to give up on Android 2.3 support.

With the current steroids version, my Android app seems stable, except I can't make angular-animate to work properly in it (looks gorgeous on iOS). But I can (and already have) give up on that for now. Really hoping for both discussion and software updates soon.

Thanks!

rafalohn commented Mar 17, 2014

@harsaharsa you asked to be informed of client pressure. My app is ready, my client wants to release it. This week. I've been asking in the forum constantly.

The only plugin I use is 'Media'. I have only one steroids.layers.push outside my main page, and I can probably live without it. What I really need is support up to the current Android 4.4, ideally, the same apk to support from 2.3 up. Unfortunately I am not ready to give up on Android 2.3 support.

With the current steroids version, my Android app seems stable, except I can't make angular-animate to work properly in it (looks gorgeous on iOS). But I can (and already have) give up on that for now. Really hoping for both discussion and software updates soon.

Thanks!

@jamespeerless

This comment has been minimized.

Show comment
Hide comment
@jamespeerless

jamespeerless Mar 17, 2014

Luckily I wasn't using steroids for anything other than a build system and was successfully able to migrate the project to a vanilla cordova project and built for 4.4 without any issues.

jamespeerless commented Mar 17, 2014

Luckily I wasn't using steroids for anything other than a build system and was successfully able to migrate the project to a vanilla cordova project and built for 4.4 without any issues.

@benshope

This comment has been minimized.

Show comment
Hide comment
@benshope

benshope Mar 26, 2014

Any update on the 4.4 client initial availability date? My app uses no native UI features.

benshope commented Mar 26, 2014

Any update on the 4.4 client initial availability date? My app uses no native UI features.

@juhazi

This comment has been minimized.

Show comment
Hide comment
@juhazi

juhazi Mar 26, 2014

Member

We have now released a new android Scanner version 3.1.3 to Google Play with 4.4 support enabled.

Using the new version successfully requires a workaround outlined in #136

Short version of the workaround is to use <script src="http://localhost/zordova.js"></script> instead of <script src="http://localhost/cordova.js"></script>.

The build service does not currently build any builds with the new android release. We are waiting on a feature to specify a minimum and maximum android SDK version per build in build settings to avoid having built apps supporting 4.4 until the developers have had a chance to test them.

Expect the build service to be updated soon.

Member

juhazi commented Mar 26, 2014

We have now released a new android Scanner version 3.1.3 to Google Play with 4.4 support enabled.

Using the new version successfully requires a workaround outlined in #136

Short version of the workaround is to use <script src="http://localhost/zordova.js"></script> instead of <script src="http://localhost/cordova.js"></script>.

The build service does not currently build any builds with the new android release. We are waiting on a feature to specify a minimum and maximum android SDK version per build in build settings to avoid having built apps supporting 4.4 until the developers have had a chance to test them.

Expect the build service to be updated soon.

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Mar 26, 2014

@juhazi this is wonderful news. Just a quick question, although relevent to probably a different tread, I am hoping that Steroids will extend its compatibility in the near future to include as many supported flavors of android as cordova. Do you have such plans? and if so what sort of timeline are we looking at. I feel the one reason that people shy away from using Steroids (i find it is the key solution to the future of web apps) is because they don't like that its compatibility wth teh number of android flavors is so low.

rohanbhangui commented Mar 26, 2014

@juhazi this is wonderful news. Just a quick question, although relevent to probably a different tread, I am hoping that Steroids will extend its compatibility in the near future to include as many supported flavors of android as cordova. Do you have such plans? and if so what sort of timeline are we looking at. I feel the one reason that people shy away from using Steroids (i find it is the key solution to the future of web apps) is because they don't like that its compatibility wth teh number of android flavors is so low.

@pre

This comment has been minimized.

Show comment
Hide comment
@pre

pre Mar 27, 2014

Contributor

Update: It seems that Android client on 4.4 does not load CSS properly if your HTML document starts with

If you remove CSS will load. This does not affect other platforms than Android 4.4.

We have recently freed up more resources for Android development. We are not happy with the current state of our Android client and we will fix it properly. Thank you for your patience.

Contributor

pre commented Mar 27, 2014

Update: It seems that Android client on 4.4 does not load CSS properly if your HTML document starts with

If you remove CSS will load. This does not affect other platforms than Android 4.4.

We have recently freed up more resources for Android development. We are not happy with the current state of our Android client and we will fix it properly. Thank you for your patience.

@juhazi

This comment has been minimized.

Show comment
Hide comment
@juhazi

juhazi Mar 27, 2014

Member

Build service is now building the new Android 3.1.3 release

Member

juhazi commented Mar 27, 2014

Build service is now building the new Android 3.1.3 release

@harsaharsa

This comment has been minimized.

Show comment
Hide comment
@harsaharsa

harsaharsa Mar 31, 2014

Member

With 4.4 support out, I've split the known issues into separate issues and will be closing this issue:

Current Android 4.4 known issues:

Also, two general Android issues that need to be worked around with the instructions in the issue tickets:

Note that contrary to what we originally planned, all existing Android native UI features are available for 4.4 also. If you experience any more 4.4-specific issues, please open a separate ticket for them.

Member

harsaharsa commented Mar 31, 2014

With 4.4 support out, I've split the known issues into separate issues and will be closing this issue:

Current Android 4.4 known issues:

Also, two general Android issues that need to be worked around with the instructions in the issue tickets:

Note that contrary to what we originally planned, all existing Android native UI features are available for 4.4 also. If you experience any more 4.4-specific issues, please open a separate ticket for them.

@harsaharsa harsaharsa closed this Mar 31, 2014

@WassimHakim

This comment has been minimized.

Show comment
Hide comment
@WassimHakim

WassimHakim Aug 11, 2014

Are there any updates on that front?

Also, is there one document on how to deploy an app on 4.4? I didn't seem to find any

WassimHakim commented Aug 11, 2014

Are there any updates on that front?

Also, is there one document on how to deploy an app on 4.4? I didn't seem to find any

@rohanbhangui

This comment has been minimized.

Show comment
Hide comment
@rohanbhangui

rohanbhangui Aug 12, 2014

@WassimHakim just look at the logs and wait i think some of this stuff is solved not all.

rohanbhangui commented Aug 12, 2014

@WassimHakim just look at the logs and wait i think some of this stuff is solved not all.

@harsaharsa

This comment has been minimized.

Show comment
Hide comment
@harsaharsa

harsaharsa Aug 12, 2014

Member

We won't be pushing any more updates to Legacy Android. Fresh Android is very well underway, with initial MPA support coming in v3.5.3. You can see open Fresh Android issues at https://github.com/AppGyver/steroids/issues?q=is%3Aopen+is%3Aissue+label%3A%22Fresh+Android%22 and the scopes for upcoming releases at https://github.com/AppGyver/steroids/milestones

Member

harsaharsa commented Aug 12, 2014

We won't be pushing any more updates to Legacy Android. Fresh Android is very well underway, with initial MPA support coming in v3.5.3. You can see open Fresh Android issues at https://github.com/AppGyver/steroids/issues?q=is%3Aopen+is%3Aissue+label%3A%22Fresh+Android%22 and the scopes for upcoming releases at https://github.com/AppGyver/steroids/milestones

@pre pre changed the title from Android 4.4 support to Android 4.4 support for Legacy Android Feb 2, 2015

@pre

This comment has been minimized.

Show comment
Hide comment
@pre

pre Feb 2, 2015

Contributor

This issue is not valid for the current Android Scanner.

Contributor

pre commented Feb 2, 2015

This issue is not valid for the current Android Scanner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment