Jump to content

2.4 Phaser working fine in browser but not on mobile device via Cordova


mwatt
 Share

Recommended Posts

So, this is potentially a 2.4 Phaser issue, though I doubt it since nobody else is squawking.  Nonetheless, since 2.4.1 is pronounced "live", and because it might must be an issue on my side, I'm posting this on a new thread, not the 2.4 announcement thread.

 

So here's the deal.  My game works fine in the browser - both on desk top and on target mobile devices.  However, when it is packaged up as an install with Cordova (phonegap) and stuff, it does not work.  

 

The failure mode is that touching sprites with events assigned does not generate an event.

 

My partner and I suspected some build or source issue on our side, but after some investigation, could not find a problem.  So we decided to try swapping the old phaser version (2.3) back into the solution - and things work properly again after doing so.

 

Any ideas?

 

Edit:

I just now noticed that this same issue was posted by Apoptyzm in another post, so I guess it isn't just me.  Rich, please let me know if I can provide anything else in terms of source.  A test case might be hard to create, since it only happens via Cordova for me.

Link to comment
Share on other sites

Working on that right now Rich.  I've downloaded and rebuilt the latest dev version.  I added this newly built file (I used the minified version) into my project.

 

My partner does the release builds.  I have contacted him and asked him to try it with this new phaser.js version.  He told me that the problem is also seen in the emulator so it should not take too long, once he can get to it.

Link to comment
Share on other sites

I need to alter my original description of the problem.  I had reported that through the BROWSER on a mobile device, that 2.4.1 was working properly for my game, but that is false.  We probably hadn't flushed cache when we incorrectly "noticed" that.  

 

Bottom line is that it does not run on mobile (at least, not on Apple iPhone or iPad) at all.  I believe this is consistent with what the other fellow was reporting.

Link to comment
Share on other sites

Ok I'm 99% sure this is fine now! I've uploaded new builds files to the dev branch just now. I also built a test app and deployed it to Android using Intel XDK and it works fine on device now (after I fixed this bug that is). Please give it a shot :)

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...