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.

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.

We just made a change in Crosswalk Beta in XDK to unconditionally disable it. Until we get the next release out in July, we can't add any options to current build, but we will add a control soon after that release.

There were many people reporting that the blacklist was not needed, but no real evidence that the blacklist was preventing crashes. If that turns out to be false, then we will unconditionally disable it again. But I am hoping that we can leave it that way for a few weeks until we give the developer control. Please let us know what your experience is.

IntelRobert

Hopefully you guys will provide option to enable or disable the GPU blacklist so that we can choose for stability or high performance. If you hard coded it, I'm worried that somehow we will encountered some stability problem when deployed.

Yes, window.open opens a browser. I have written tests for it, but never tried from C2. Crosswalk5 (stable in xdk) had some issues, but it works well for me in crosswalk 6 (beta in xdk).

> Crosswalk supports cordova APIs, including the inappbrowser api that lets you pop up a browser and visit a URL. It is accessible from javascript, so you would need a c2 plugin to include it in your game.

>

>

> > We need only 2 thinks...

> > 1. remove exit bug in stable version, when i close aplication, aplication crashes...

> > 2. add some feature, that we can open web pages in defaul browser, it is anoying to open in aplication and i can not go back...

> >

>

Did you mean this: http://cordova.apache.org/docs/en/2.4.0 ... er.md.html ? It is same as in Construct2, no? Construct 2 uses:

window.open(url_);[/code:1bvb3mer]

The XDK release has slipped a couple weeks into July. It will have support for custom phonegap plugins, so you can include the admob and other phonegap plugins. This will make it available in javascript, but someone will have to make a c2 plugin to use it in C2. If someone already has a c2 plugin that will work with phonegap, then we are all set. I am also trying to get the GPU blacklist disabled--hopefully without waiting for the next xdk release.

There are some big changes coming to the way the XDK build works. It will make it much easier to roll out new features, but it has taken longer than expected. We know that ads and payment are important for you to make money.