IntelRobert's Forum Posts

  • We still have an issue with the emulator not handling the back button correctly. We have a fix, but it requires an xdk update. Shinkan is having a problem with webgl not working in debugger. I will follow up with him. Otherwise, I think we are all caught up with regressions since the last release.

    The new release gives you cordova plugins, the ability to make a game go to usb/external storage, control over version codes/signing.

    Dean will be updating crosswalk to 7 in the build system next week. Ian is working on using cordova plugins to provide ads/payment/expansion files. We will work on getting google play game services working.

  • Dean did an update last night that should have fixed the back button. I will look into it.

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

    But the back button still kills the app.

  • 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.

    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.

  • 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...

  • If you send email to , they will either send you the keys from the old app and you can sign yourself, or you can ask them to use whatever keys you want for the new app.

    > Managed to finally get my existing C2 build with crosswalk created. The upgrade of my xdk project may have been the issue, but not really sure. Just created a new Intel XDK project then export C2 build to the www folder again and it worked.

    >

    What if this happens after you've already built your project and put it on the app store? From my experience, starting a new project from scratch changes the signing, and you can't update your current app anymore, unless I just did it wrong

  • status update: Dean has been working on the back button, but hasn't found the problem yet.

    For the backbutton issue, give me another day to find out. The fix only requires an update to our server so it will be quick after they find the problem.

    > IntelRobert Do you know if there is going to be a fix for this any time soon, should we revert back to an older version?

    >

  • For the backbutton issue, give me another day to find out. The fix only requires an update to our server so it will be quick after they find the problem.

    IntelRobert Do you know if there is going to be a fix for this any time soon, should we revert back to an older version?

  • Thanks for the clarification. I have reproduced the problem with a simple test case and we are working on it.

    IntelRobert

    No, i am saying events that calls the back button or open a url (both on the browser object, so there might be something in general with that plugin) are not being performed at all.

    The back button seems to quit the app, regardless to any events or what layout you're in.

    I tried both stable and beta version, but i am guessing it got something to do with permissions.

    I went over the list of the android permission, but i couldn't find anything related to that.

  • For the back button, are you saying that 'back' exits the program, but you want to keep it running and be able to come to the same point?

    I didn't change much.

    In the permission tab i have only:

    In app browser and splash-screen enabled (but previous exports with more permission worked as well, so i don't your problem is there)

    In the build tab under android-crosswalk:

    I filled in the normal values for app id/name/desc etc.

    The app version and version code i had to change on the second export so google play will let me upload the file.

    Domain access i left with *

    and cli version with 3.3

    I checked the full screen box

    orientation: landscape

    install location: default

    i check the signed box

    and i used crosswalk beta

    I also uploaded icons and splash screen images (all images must be located inside the www directory of the project before selecting them.

    That's it.

    As for exiting the app with the back button, that's another strange thing, it exits with the back button regardless to any events calling it, i think it's something new and built-in xdk, i have only one layout in this project, so i don't have any events to switch layouts on back button or anything, but i believe if i did, it would close the app as well, which is not a good thing at all...

    Just to make it clear, i have an event on back button/touch sprite - browser close.

    This event only works if var canPlay = 0

    but it closes the apps even when this var is = 1

    I hope this helps you guys.

  • I tested again without icons and splash screens and it works for me. Can the people who are having problems building PM me? Include your XDK username and app name. It's hard to tell from the forum who is stuck.

    So I added the icons and splash screens in the project area and had a successful build, but I thought I'd get an email with the link to download the apk so I just closed the XDK.

    After realizing I didn't get the mail I reopened the XDK (had to relogin for some reason), and when I tried to build using the existing code i got the build failed error.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I don't think you need icons, but I will test again to make sure.

    You don't need any of the 'intel XDK Cordova plugins'. The plugins you might need are described https://www.scirra.com/tutorials/809/how-to-export-to-android-with-crosswalk and they are all located under 'core cordova plugins'

    I was finally successful to build crosswalk game with XDK. Looks like you have to include Icons from now on. In previous build default Intel icons were used automatically. Now if you don't include your own icons, you would not be able to make a build.

    But still need to ask "what's the difference between "Core Cordova Plugins" and "Intel XDK Cordova Plugins"? Which one should I use?"

  • Is it possible to send a simple capx that shows the problem by PM?

    Hi everybody.

    I was recommended to visit this post to look for help related to Intel XDK problems.

    I am trying to develop a game that will use accelerometer to move the player around, I already have the game finished and accelerometer is working (at least on the cocoonjs launcher), however, when I try to build the game using IntelXDK with the option "Crosswalk for Android" the game won´t work, I know that this is not an event related problem because, as I already said, the game works just fine when I test it on my android device using the cocoonjs launcher, also, I used the debug option from the intel XDK and it works when I simulate the accelerometer movement on it. I want to note that I am using this tutorial https://www.scirra.com/tutorials/809/ho ... -crosswalk so I am setting the corresponding plugin options accordingly (accelerometer ->YES). I have no idea why this is not working, I am a developer and I could try and fix it, the problem is, I don´t even know where I should start looking!!. I would really appreciate any help you could give me guys. I was also recommended to ask someone called — In any case thank you everbody.

  • Our July release will have support for cordova/phonegap plugins. There are plugins for admob, in-app-payment, and other useful services. Users will be less dependent on XDK & crosswalk to add features when a phonegap plugin is available. The release is a few weeks away, and then someone will have to write a c2 plugin that calls the phonegap plugin.

    I just need help how to put admob and analytics on my projects...

    Can anyone help me out.. i need it on building over intel xdk

  • Current Beta has this change (v6). Also current stable (v5). Please let us know if you see crashes.

    IntelRobert

    IntelRobert

    does that mean that when I build an app today with version "BETA Crosswalk 6.35.131.6 on Cordova 3.4.0" my Samsung Galaxy S3 will not be on the blacklist? Or are we talking about some future beta?

    Thank you.