For those reading this thread, frameworks (such as Cocos2D) that rely on using XHR with file:// URLS, and treat a non-200 status and/or a non-OK statusText as an error may not work in App Preview due to some XHR override code that is included as part of App Preview. This special handling XHR code code built into App Preview can be disabled by adding the "data-noxhrfix" property to the <head> tag in your app, for example:
Please watch this video for a quick overview of how to update an existing Intel XDK project in the latest XDK release.
There is no audio in this video.
If you are seeing the following dialog on the Build tab:
Our support staff is based in the USA. We only monitor this forum during Pacific Time business hours, Monday thru Friday. We do not monitor the forum on weekends or during US national holidays.
For anyone having a problem with custom web services not showing up in the list of web services, update your apiconfig.json file to have these field within the service description object:
We are seeing that some users are having difficulties building for iOS. The errors in the Build log generated by Xcode are not very useful, but it turns out that lot of issues come from not providing the correct certificate (P12 file) and/or provisioning profile or mismatch between P12 and provisioning profile. We are looking into providing specific errors so you don't have to guess what's wrong. But meanwhile if your build fails please make sure your P12 and provisioning profile are correct.
Please follow these steps to generate the P12 file.
Many Construct2 users are reporting a "white bar" or a "white line" during the startup of their app, especially when built with Crosswalk for Android. The following observations and solution may help with that problem. This topic on the Scirra forum covers the same issue > https://www.scirra.com/forum/viewtopic.php?f=146&t=171108&p=1033751#p103...
There is a significant change in the Windows Phone 8.1 webview and apps, compared to the "legacy" Windows Phone 8.0 webview and apps that is the cause of many Windows app crash problems.
If you receive a "Package signature verification failed" message (see image below) when installing the Intel XDK on your system, it is likely due to one of the following two reasons:
One of our very passionate developers has discovered a very odd problem with the Facebook Connect plugin, that is caused by performing a simple copy and paste action from the Facebook Dashboard to the Intel XDK. Probably for responsive design reasons, if your Facebook App Name is 11 or more characters long there will be "soft hyphen" characters inserted into your Facebook app's name. These extra characters are hidden from view, but they are part of the name that you copy from the Facebook dashboard.