Crosswalk Intel XDK experiences

  • bjadams

    I use this for signing my apks

    apk-signer-1.8.5

  • I'll be XDK all the way as my app is about 5 days to finally reach the Play store (in full form) for Android... I've already written up a really long post that I'd like to share... It starts from ground zero, just having an idea and Construct2. XDK Crosswalk for Android has so far been the most compatible. In fact, I've had VERY VERY little issues as far as Compatibility through compilation goes... While with CJS and Ludei, I couldn't even get the App past their branded load screen. (Did I mention XDK gives you your own brand/splash - cheers!)

  • Now it just needs in app purchases and ad functionality to be the best

    And I couldn't seem to get the back button working for some reason...

  • There was a bug with backbutton. Dean diagnosed the problem so I am expecting a fix soon.

    Now it just needs in app purchases and ad functionality to be the best

    And I couldn't seem to get the back button working for some reason...

  • Well i have build it the app .. everything was great at my side.. BUT.. didnt be able to build a app with the admob integration not even the example that the plugin have it.

    https://software.intel.com/en-us/html5/ ... pplication

    Once again did anyone had try the example?

    I tried and nothing happened. It seemed to build normal, just nothing happened. Same for you?

  • IntelRobert Thanks IntelRobert for the quick reply and fix!! Much Appreciated!

  • IntelRobert

    I think there is a bug (or change?) with open external link in the last XDK version.

    At first export, I use "Minimum plugin". When we touch a button to open a link, nothing happens.

    Then, I tested all plugins in order to know why the link was not opened.

    To open a link with C2 function "Browser, Open URL" we must to activate plugin xdk "Device"

    But this plugin ask to user " permission Send sms" and many others...

    With the older version, we need no permissions (or only Internet permission)... it seems more logic no ?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • amkp Did you manage to get opening a url to work in the new XDK?

    I tried with all permissions on and it still didn't work.

  • Yes it works. But I've downgraded to old xdk version now, too much bug.

    All permissions or all plugins ?

    I talk about xdk and cordova plugins you can choice in "PROJECT" tab.

  • Is there a way to turn on/force webgl in XDK preview or debug?

    My game after build runs in webgl on my phone but in preview/debug always starts with canvas2d only. And it's kind of hard to determine if it's working fine.

  • Getting same bugs with opening urls, app.loadurl is the error. Also tested literally all of Construct2's objects having anything related to opening/redirecting to url as a function, and tested + compiled in XDK Crosswalk but to NO avail. Nothing works to open a url. Yeah, major issue here, since no URLs can't be opened on the device's default web browser.

    One last test I'll try is to try and pull the Cordova API and see if inappbrowser is of any use. Maybe this is a better option than opening up the user's default browser... Who knows. I'm using XDK 1199 and the latest C2 now (176)

    I guess right now, it's time to build your userbase.

  • Your phone is on the chrome blacklist for webgl. I believe if you tried the game in chrome for android, it would always use canvas2d. We disabled the blacklist when building apk. I put in a request to disable it for XDK debugger so you see consistent behavior. There isn't a way to do it yourself, unfortunately, so you have to wait for an update.

    Is there a way to turn on/force webgl in XDK preview or debug?

    My game after build runs in webgl on my phone but in preview/debug always starts with canvas2d only. And it's kind of hard to determine if it's working fine.

  • inappbrowser is the preferred way to open a url. I wrote an example that uses it for oauth here: https://github.com/rscohn2/phonegapi/bl ... onegapi.js

    look for window.open

    Getting same bugs with opening urls, app.loadurl is the error. Also tested literally all of Construct2's objects having anything related to opening/redirecting to url as a function, and tested + compiled in XDK Crosswalk but to NO avail. Nothing works to open a url. Yeah, major issue here, since no URLs can't be opened on the device's default web browser.

    One last test I'll try is to try and pull the Cordova API and see if inappbrowser is of any use. Maybe this is a better option than opening up the user's default browser... Who knows. I'm using XDK 1199 and the latest C2 now (176)

    I guess right now, it's time to build your userbase. <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing">

  • Your phone is on the chrome blacklist for webgl. I believe if you tried the game in chrome for android, it would always use canvas2d. We disabled the blacklist when building apk. I put in a request to disable it for XDK debugger so you see consistent behavior. There isn't a way to do it yourself, unfortunately, so you have to wait for an update.

    Thanks for answering.

    I can run html5 version of my game (and other games/webpages) with webgl using chrome for android on my galaxy S3 (standard chrome for android version, all settings and flags are default) and can't remember having any issues with that.

    anyway, there's one more issue while testing/debugging using USB connection. Testing works fine, game starts in App preview on my phone, but If I try to use debugger XDK flashes white for a second and after that App preview on my phone is crashing.

  • It seems like the call to browse close and open url are fixed now.

    But the back button still kills the app.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)