Release Notes

Supported Systems: For a full list of systems supported by the Intel® XDK please review Intel XDK Supported Systems.

Our automatic updater provides notification to existing Intel XDK users when an update is available. Updates will be released to all users within 24 hours of the public release. To update your version sooner, download and install the Intel XDK directly from xdk.intel.com.


Intel® XDK - Update - 2017 May 24, v3977

This hotfix update addresses several issues that were introduced in the v3900 and v3972 releases. 

IMPORTANT: As of March 14, 2017, the Intel XDK cloud-based build servers have been deprecated and will be retired at the end of June, 2017. Until then, expect no further upgrades and limited support for the Intel XDK cloud-based build system.

Support for creating new App Designer projects has been retired. Existing App Designer projects can still be opened and edited; however, there is no further technical support for the App Designer editor or for applications created using App Designer, and there will be no bug fixes or updates for App Designer. Additionally, our product and engineering management team has decided there will be no open source release of the App Designer editor.

As of February, 2017, the Crosswalk Project was retired. Crosswalk 23 was the last version of the Crosswalk library produced by the Crosswalk team. You can continue to build for the Crosswalk library using Cordova CLI or PhoneGap Build, but no further updates to the Crosswalk library will occur.

Issues Addressed

  • Regressions in the built-in Brackets editor, especially problems with files changes not being properly updated and some editor shortcut keys behaving badly on Mac systems.

  • The App Name field (from the Build Settings) is now correctly updated in the <name> tag within the config.xml file that is created by the Cordova Build Package tool. Note that the Android application name has priority over iOS, which has priority over Windows. If you export for only one platform that platform's name will be applied to the <name> field within the exported config.xml file.

  • The "legacy conversion" and other certificate management dialogs were incorrectly hiding the dialog input fields. The dialogs now match those shown in the documentation screen shots.

Known Issues

Issue Workaround
New IoT projects based on the "Azure Integration - Smart Home" sample cannot be created in Mac OSX* or Linux* Download the sample manually from here, decompress it in a folder and extract the sample files located in the "template" folder. You can open them like any existing Intel XDK project.
Brackets is unable to update extensions when you are running behind a proxy server. This is a known and unresolved issue with the Brackets 1.8 editor. The only known workaround is to update your Brackets extensions from a network that does not have a proxy server (such as your home network). Alternatively, you can perform a manual install from a ZIP of the Brackets extension. See this forum post for detailed instructions.

Simulate tab does not support the retired intel.xdk APIs or the barcode plugin. When your app encounters those APIs it generates a dialog similar to the following:

The Simulate tab depends on the availability of simulation code that is provided by the respective Cordova plugin developers. Since there is no Simulate tab backend provided by the PhoneGap barcode plugin author(s), nor for the retired Intel XDK plugins, you will see the dialog shown to the left.

This is proper behavior for the Simulate tab when it encounters a third-party plugin for which there is no "simulate backend" provided by the plugin author(s) -- thus the reason you must provide a "simulated response" for the API call, allowing your app to continue. Additional documentation can be found here:

The Simulate tab does not retain local storage or local cache files. There is no known workaround for this problem. The alternative is to debug a built version of your app on a real device.
The Simulate tab does not include the ability to specify a starting URL like the Emulate tab did. This means you cannot test web apps using a custom URL. Since you are testing a web app, which, by definition, does not include any Cordova plugins, you can test your app using a browser and a local web server. If you prefer not to setup your own local web server, this "Web Server for Chrome" extension may be a useful alternative. Note, the Chrome browser includes a "device mode" for viewport emulation feature that can be used to simulate rendering your app on a variety of device screens.
If you install this version of Intel XDK for Apple* OSX* on a system with an existing Intel XDK version 3522 (or earlier) using a new installation directory, the installer may not completely remove the old version of the Intel XDK. The newly installed version should be fully functional and you can safely remove the older one, manually.
If you experience a crash of the Intel XDK, immediately following an update, and each attempt to start the Intel XDK results in an immediate crash of the Intel XDK, your installation may have been corrupted during installation.

On a Windows system this can be identified by looking at the list of installed applications, where you will find the old version and the new version of the Intel XDK are still listed as "installed."
Follow the instructions in this FAQ to completely uninstall all application files and cache files used by the application from your system. Then download the Intel XDK from xdk.intel.com and reinstall the Intel XDK.
The "Cordova Build Package" tool on the Build tab fails to prompt to save a ZIP file. This can be caused by the presence of an inconsistent *.json file in your project's "plugins" folder. See this forum post for a workaround.
Unable to add or remove plugins in an exported Construct2 project. This can be caused by the presence of a config.xml file in your project's root folder. Projects that are exported by the Construct2 export tool include a config.xml file designed for use with PhoneGap Build. Unfortunately, the presence of that file sometimes interferes with the Cordova CLI tools that are built into the Intel XDK.

You can either delete the config.xml file or rename the file to resolve this problem.
Unable to remove plugins after upgrading from an older version of the Intel XDK. This is an outstanding Cordova CLI issue that is related to a small subset of plugins. The issue does not impact older versions of the Intel XDK (3759 and older) but does impact versions 3900 and later of the Intel XDK.

For a workaround, see this forum thread. This workaround will help you remove a plugin that you otherwise are unable to remove via the Plugin Manager.
"TypeError: Cannot read property 'mode' of undefined" error when trying to export project with the "Cordova Build Package" tool:

If your project is configured as a "web app" upgrading it to a "cordova" project should fix this problem (not all "web app" projects will cause this behavior).

See this forum thread for details on how to upgrade your "web app" project to a cordova project, so it can be exported using the "Cordova Build Package" tool.

Keep Us Informed

To provide us with feedback, report issues, and find answers to your questions, please visit the Intel XDK forum.


Intel® XDK - Release - 2017 May 17, v3972

This update retires several features that were previously announced as deprecated, eliminates the requirement to register before using the Intel XDK and fixes several minor bugs.

IMPORTANT: As of March 14, 2017, the Intel XDK cloud-based build servers and the Publish tab have been deprecated and will be retired at the end of June, 2017. Until then, expect no further upgrades and limited support for the Intel XDK cloud-based build system.

Support for creating new App Designer projects has been retired. Existing App Designer projects can still be accessed and edited within the Intel XDK; however, there is no further technical support for the App Designer editor or for applications created using App Designer and there will be no bug fixes for that tool. Additionally, our product and engineering management team has decided there will be no open source version of the App Designer editor.

As of February, 2017, the Crosswalk Project was retired. Crosswalk 23 was the last version of the Crosswalk library produced by the Crosswalk team. You can continue to build for the Crosswalk library using Cordova CLI or PhoneGap Build, but no further updates to the Crosswalk library will occur.

Issues Addressed

  • Fixed an issue where the Linux and Mac OSX version of the Intel XDK would sometimes hang when creating an app while disconnected from the network.

  • The Cordova Build Package tile incorrectly reported an error when build credentials were not provided in the Build Settings section of the Projects tab, and would prevent export of your application if build credentials were not provided.

  • The Bower "auto sync" state now defaults to "no" for all new projects in order to avoid issues for those who utilize Bower manually, at the command-line.

  • You are no longer required to register for an Intel XDK account when installing and starting the Intel XDK for the very first time. You do need to create an account in order to use the Test tab and (soon to be retired) cloud-based build system. An account is not required to use the Projects tab, Develop tab, Simulate tab and the Cordova Build Package tile on the Build tab.

  • The Cordova Build Package tile is now visible and usable when the Intel XDK does not have a network connection.

  • The Publish tab has been retired.

  • Issues that prevented the Simulate tab from working with alert(), confirm() and other "modal dialogs" have been addressed and will now work. See this SO post for background and this forum post for a recommended alternative to using those "modals" in your app.

  • Under certain conditions, the connection between the Intel XDK and your IoT device could be lost. A "keep-alive" feature was added to minimize this problem.

  • All mobile application templates and samples that depend on App Designer or App Framework have been retired. Additionally, those templates and samples that are out-of-date or not relevant to the development of mobile companion apps for IoT have been retired.

Known Issues

Issue Workaround
New IoT projects based on the "Azure Integration - Smart Home" sample cannot be created in Mac OSX* or Linux* Download the sample manually from here, decompress it in a folder and extract the sample files located in the "template" folder. You can open them like any existing Intel XDK project.
Brackets is unable to update extensions when you are running behind a proxy server. This is a known and unresolved issue with the Brackets 1.8 editor. The only known workaround is to update your Brackets extensions from a network that does not have a proxy server (such as your home network). Alternatively, you can perform a manual install from a ZIP of the Brackets extension. See this forum post for detailed instructions.

Simulate tab does not support the retired intel.xdk APIs or the barcode plugin. When your app encounters those APIs it generates a dialog similar to the following:

The Simulate tab depends on the availability of simulation code that is provided by the respective Cordova plugin developers. Since there is no Simulate tab backend provided by the PhoneGap barcode plugin author(s), nor for the retired Intel XDK plugins, you will see the dialog shown to the left.

This is proper behavior for the Simulate tab when it encounters a third-party plugin for which there is no "simulate backend" provided by the plugin author(s) -- thus the reason you must provide a "simulated response" for the API call, allowing your app to continue. Additional documentation can be found here:

The Simulate tab does not retain local storage or local cache files. There is no known workaround for this problem. The alternative is to debug a built version of your app on a real device.
The Simulate tab does not include the ability to specify a starting URL like the Emulate tab did. This means you cannot test web apps using a custom URL. Since you are testing a web app, which, by definition, does not include any Cordova plugins, you can test your app using a browser and a local web server. If you prefer not to setup your own local web server, this "Web Server for Chrome" extension may be a useful alternative. Note, the Chrome browser includes a "device mode" for viewport emulation feature that can be used to simulate rendering your app on a variety of device screens.
If you install this version of Intel XDK for Apple* OSX* on a system with an existing Intel XDK version 3522 (or earlier) using a new installation directory, the installer may not completely remove the old version of the Intel XDK. The newly installed version should be fully functional and you can safely remove the older one, manually.
If you experience a crash of the Intel XDK, immediately following an update, and each attempt to start the Intel XDK results in an immediate crash of the Intel XDK, your installation may have been corrupted during installation.

On a Windows system this can be identified by looking at the list of installed applications, where you will find the old version and the new version of the Intel XDK are still listed as "installed."
Follow the instructions in this FAQ to completely uninstall all application files and cache files used by the application from your system. Then download the Intel XDK from xdk.intel.com and reinstall the Intel XDK.
The certificate management tool, the tool that facilitates creating, uploading and converting Android and iOS package certificates, appears to be missing some of the input fields. The tool is incorrectly sized in the vertical direction. There is a small vertical scrollbar to the right of the input fields that can be used to see the "missing" fields in the dialog. See this forum thread for additional details and some helpful screenshots.
The "Cordova Build Package" tool on the Build tab fails to prompt to save a ZIP file. This can be caused by the presence of an inconsistent *.json file in your project's "plugins" folder. See this forum post for a workaround.
Unable to add or remove plugins in an exported Construct2 project. This can be caused by the presence of a config.xml file in your project's root folder. Projects that are exported by the Construct2 export tool include a config.xml file designed for use with PhoneGap Build. Unfortunately, the presence of that file sometimes interferes with the Cordova CLI tools that are built into the Intel XDK.

You can either delete the config.xml file or rename the file to resolve this problem.
Unable to remove plugins after upgrading from an older version of the Intel XDK. This is an outstanding Cordova CLI issue that is related to a small subset of plugins. The issue does not impact older versions of the Intel XDK (3759 and older) but does impact versions 3900 and later of the Intel XDK.

For a workaround, see this forum thread. This workaround will help you remove a plugin that you otherwise are unable to remove via the Plugin Manager.
"TypeError: Cannot read property 'mode' of undefined" error when trying to export project with the "Cordova Build Package" tool:

Your project is configured as a "web app" which needs to be upgraded to a "cordova" project. See this forum thread for details on how to upgrade your project to a cordova project, so it can be exported using the "Cordova Build Package" tool.

Keep Us Informed

To provide us with feedback, report issues, and find answers to your questions, please visit the Intel XDK forum.


Intel® XDK - Update - 2017 April 3, v3922

This update primarily addresses problems with the Intel XDK user login and registration pages and bugs in the newly introduced Cordova Build Package tile (located on the Build tab). Additionally, some critical crash bugs and issues that impaired usability of the Intel XDK have been addressed. Continue reading for details.

Support for creating new App Designer projects using any of the previously deprecated App Framework, Framework 7, and Ionic UI frameworks has been removed. Existing projects using these deprecated frameworks can still be accessed and modified within App Designer.

IMPORTANT: with this release of the Intel XDK, the App Designer component (aka the UI layout tool) has been deprecated. It will be retired from the Intel XDK in an upcoming release. Once retired, existing App Designer projects will continue to work, but you will not be able to create new App Designer projects. Also, no bug fixes will be implemented for the App Designer component.

IMPORTANT: As of March 14, 2017, the Intel XDK cloud-based build servers and the Publish tab have been deprecated and will be retired at the end of June, 2017. Until then, expect no further upgrades and limited support.

These features are being retired because, as previously announced and noted in these release notes, the Intel XDK is now focused on the development of IoT (Internet of Things) apps and IoT mobile companion apps. Since we introduced the Intel XDK IoT Edition in September of 2014, the need for accessible IoT app development tools has increased dramatically. At the same time, HTML5 mobile app development tools have matured significantly. Given the maturity of the free open-source HTML5 mobile app development tools, we feel you are best served by using those tools directly.

On February, 2017, the Crosswalk Project was retired. Crosswalk 23 was the last version of the Crosswalk library produced by the Crosswalk team. You can continue to build for the Crosswalk library using Cordova CLI or PhoneGap Build, but no further updates to the Crosswalk library will occur.

Issues Addressed

  • Due to unforseen problems with certificate authorizations and the version of the node-webkit runtime distributed with the Intel XDK release v3900, the Intel XDK login pages were inaccessible for many users. With this update we have upgraded the node-webkit runtime to address this problem. See this forum post for details regarding the original issue.

  • The Cordova Build Package tile did not correctly handle icon and splash screen images that were located outside of the 'package-assets' project folder. See this forum post for more details regarding the original issue.

  • The structure of the Adobe* PhoneGap* Build system prevents it from supporting the standard Apache* Cordova* CLI Android "launchMode" preference. This results in an incompatibility between builds generated by the Intel XDK build system and PhoneGap Build (based on the config.xml file generated by the Cordova Build Package tile). Changes were made to the exported config.xml file to rectify this discrepancy. See this forum post for details.

  • Android packages built using PhoneGap Build based on projects generated by the Cordova Build Package tile did not include icons and splash screen images, due to the lack of the 'density' attribute within the config.xml file for the icon and splashscreen preference tags. See this forum post for details.

  • The cordova-plugin-crosswalk-webview was sometimes wrongly included in the build export package generated by Cordova Build Package tile. See this forum post for details.

  • Android packages built using PhoneGap Build from the project exported by the Cordova Build Package tile and configured to use Cordova CLI version 5.1.1 within the Intel XDK Build Settings were wrongly built using the old ant build tools, rather than the gradle build tools. See this forum post for details. This update adds a preference tag specific to PhoneGap Build that forces the use of gradle for all Android builds. This issue did not impact users of Cordova CLI.

  • On Apple* OSX* systems, the icons and splash screen images could not be added or updated, and existing icon and splash screen images were not displayed correctly.

  • On Apple OSX systems, pressing the command key (⌘) when the cursor was located within the code editor would cause the current line of code to get an "un-indent" command, as if the keyboard shortcut "Crlt+[" had been depressed. This issue would also impacted some other OSX keyboard shortcuts.

  • Under certain conditions, dragging and dropping a widget in App Designer would cause the Intel XDK to crash with a "Cannot read property 'pageYOffset' of undefined" error.

  • Closing the Intel XDK with the Simulator debug window open would generate a crash with "nw.js exit code = 258."

  • Changing or inspecting project icons (and similar tasks) sometimes generated a crash with the error "Cannot read property 'removeChild' of null."

Known Issues

Issue Workaround
New IoT projects based on the "Azure Integration - Smart Home" sample cannot be created in Mac OSX* or Linux* Download the sample manually from here, decompress it in a folder and extract the sample files located in the "template" folder. You can open them like any existing Intel XDK project.
Brackets is unable to update extensions when you are running behind a proxy server. This is a known and unresolved issue with the Brackets 1.8 editor. The only known workaround (at this time) is to update your Brackets extensions from a network that does not have a proxy server (such as your home network). Alternatively, you can perform a manual install from a ZIP of the Brackets extension. See this forum post for detailed instructions.
The alert() and confirm() functions do not work when using the Simulate tab. If you are using these features for debugging, please use console.log() and the Simulate tab's debug console, instead.

If you are using these features as a functional part of your app, please take a look at the standard Cordova "notification" (aka "dialogs") plugin. This plugin provides much more flexibility and incorporates a look and feel that matches the native platform.

Simulate tab does not support the retired intel.xdk APIs or the barcode plugin. When your app encounters those APIs it generates a dialog similar to the following:

The new Simulate tab depends on the availability of simulation code that is provided by Cordova plugin developers. This means that a more accurate emulation of specific plugins is possible in the browser environment in which the Simulator (and the old Emulator) runs in (there is no device emulation in either the old Emulate tab or in the new Simulate tab).

The old Emulate tab included legacy code that allowed the PhoneGap barcode plugin to be simulated. However, there is no Simulate tab backend for the PhoneGap barcode plugin, nor for any of the retired Intel XDK plugins. Thus the reason for the dialog shown to the left.

This is proper behavior for the Simulate tab when it encounters a third-party plugin for which there is no "simulate backend" provided by the plugin -- at which point you need to provide the "simulated response" for the API call in order to make your app continue. Additional documentation can be found here:

The Simulate tab does not retain local storage or local cache files. There is no known workaround for this problem. The alternative is to debug a built version of your app on a real device.
The Simulate tab does not include the ability to specify a starting URL like the Emulate tab did. This means you cannot test web apps using a custom URL. Since you are testing a web app, which, by definition, does not include any Cordova plugins, you can test your app using a browser and a local web server. If you prefer not to setup your own local web server, this "Web Server for Chrome" extension may be a useful alternative. Note, the Chrome browser includes a "device mode" for viewport emulation feature that can be used to simulate rendering your app on a variety of device screens.
If you manually install this version of Intel XDK for Apple* OSX* on a system with an existing Intel XDK version 3522 (or earlier) using a new installation directory, the installer may not completely remove the older version. The newly installed version should be fully functional and you can safely remove the older one, manually.
If you experience a crash of the Intel XDK, immediately following an update, and each attempt to start the Intel XDK results in an immediate crash of the Intel XDK, your installation may have been corrupted during installation.

On a Windows system this can be identified by looking at the list of installed applications, where you will find the old version and the new version of the Intel XDK are still listed as "installed."
Follow the instructions in this FAQ to completely uninstall all application files and cache files used by the application from your system. Then download the Intel XDK from xdk.intel.com and reinstall the Intel XDK.
The certificate management tool, the tool that facilitates creating, uploading and converting Android and iOS package certificates, is missing some of the input fields. The tool is incorrectly sized in the vertical direction. There is a small vertical scrollbar to the right of the input fields that can be used to see the "missing" fields in the dialog. See this forum thread for additional details and some helpful screenshots.
The "Cordova Build Package" tool on the Build tab fails to prompt to save a ZIP file. This can be caused by the presence of an inconsistent *.json file in your project's "plugins" folder. See this forum post for a workaround.
Unable to add or remove plugins in an exported Construct2 project. This can be caused by the presence of a config.xml file in your project's root folder. Projects that are exported by the Construct2 export tool include a config.xml file designed for use with PhoneGap Build. Unfortunately, the presence of that file sometimes interferes with the Cordova CLI tools that are built into the Intel XDK.

You can either delete the config.xml file or rename the file to resolve this problem.
Unable to remove plugins in 3922 after upgrading from an older version of the Intel XDK. This is an outstanding Cordova CLI issue that is related to a small subset of plugins. The issue does not impact older versions of the Intel XDK (3759 and older) but does impact versions 3900 and later of the Intel XDK.

For a workaround, see this forum thread. This workaround will help you remove a plugin that otherwise you are unable to remove using the Plugin Manager.

Keep Us Informed

To provide us with feedback, report issues, and find answers to your questions, please visit our forums.


Intel® XDK - Release - 2017 March 14, v3900

New Features

This release upgrades the version of NW.js, which is the underlying run-time of the Intel XDK, and provides improved security and stability. Due to these changes, Apple OS X* versions prior to 10.9 (Mavericks), are no longer supported. (See Intel XDK Supported Systems for more details.) Additionally, we have added support for exporting mobile app projects; they can be built using either PhoneGap Build or Cordova CLI. See the "Cordova Build Package Tile" section below, for details. Finally, we extended the IoT support to include Wind River® Pulsar™ Linux operating system for IoT projects.

Exporting apps and going "all-In" on IoT (Internet of Things)

As we have been talking about in the past several months and releases, we have been looking for new ways to make your mobile app development experience more complete and more productive, even as we move more toward IoT application development. With that in mind, we’d like to tell you about the new direction for Intel® XDK. Please read Joe's blog for details.

Cordova Build Package Tile

In this release, we have added the new Cordova Build Package tile in the Build tab. This feature will allow you to use the Adobe* PhoneGap Build service or Cordova* CLI client to build your mobile apps.

Cordova Build Package tile

For further information about using the Cordova Build Package Tile, see the Cordova Build Package documentation.

Wind River® Pulsar™ Linux Support

The Intel XDK and its IoT Daemon can now be used on a variety of IoT boards running Wind River® Pulsar™ Linux operating system. For details, about using this operating system with the Intel XDK, please visit the Intel XDK documentation.

Issues Addressed

The following item has been addressed in this release:

  • Some issues with Bower* Package Manager not working in Mac OSX* and Linux* were fixed. See this forum post for more details.

Known Issues

Issue Workaround
New IoT projects based on the "Azure Integration - Smart Home" sample cannot be created in Mac OSX* or Linux* Download the sample manually from here, decompress it in a folder and extract the sample files located in the "template" folder. You can open them like any existing Intel XDK project.
The Icons and Splash Screens section of the Build Settings on the Projects tab does not work properly in this release on Mac OSX and Linux. If you have an existing project that already includes icons and splash screen images, they will be included with your build package, but you will not be able to replace them using the GUI tool. The issue is being researched and will be resolved in a hot-fix. To work around this issue, you can reference your icons and splash screen images using the intelxdk.config.additions.xml file. See this sample intelxdk.config.additions.xml file, which is part of the "hello cordova" demo app, for additional information and an example of how this is done. You must still locate your icon and splash screen images within the "package-assets" folder, to insure they will be included with your build package when submitting to our on-line build system or to PhoneGap Build and Cordova CLI.
Brackets is unable to update extensions when you are running behind a proxy server. This is a known and unresolved issue with the Brackets 1.8 editor. The only known workaround (at this time) is to update your Brackets extensions from a network that does not have a proxy server (such as your home network). Alternatively, you can perform a manual install from a ZIP of the Brackets extension. See this forum post for detailed instructions.
Depressing the Mac "Command" key in an edit window (on the Develop tab) causes source code lines to "undent" (the "Command-[" function). If you wish to use the built-in Brackets editor, you will have to avoid the use of the editor shortcut keys (such as "Cmd-s" for save) and use your mouse to navigate the menus.

Alternatively, you can use an external editor (such as Sublime or Brackets or Visual Studio Code, etc.) to edit your project's source code files directly. The Intel XDK includes a "file-watcher" that continuously monitors the state of the source code files in your project and will detect any file saves made when using an external editor.
Attempting to login to the Intel XDK results in an error message similar to:

The webpage at https://signin.intel.com/?appid=515&TYPE=33554433&REALMOID= ...stuff deleted... %3den-US might be temporarily down or it may have moved permanently to a new web address.
See this workaround provided in the Intel XDK forum.
PhoneGap Build and Cordova CLI always build for Crosswalk, regardless of the "Optimize for Crosswalk" setting. You must edit the exported config.xml file before submitting your ZIP file to PhoneGap Build or before using it with Cordova CLI. This means you must open the ZIP file and remove any lines similar to:

<plugin name="cordova-plugin-crosswalk-webview" ... />

were "..." means additional attributes may be present in the plugin tag. If you are submitting to PhoneGap Build, you must then replace the modified config.xml file in the ZIP file, before submitting to PhoneGap Build.
Specifying CLI 5.1.1 in your Intel XDK Build Settings results in PhoneGap Build attempting to build with the Android "ant" build system, rather than with the Android "gradle" build system, which was the standard for Cordova CLI. Unfortunately, PhoneGap Build switched to using gradle as their build system later than standard Cordova CLI did, thus the reason for this discrepancy.

To work around this issue, add the following PhoneGap Build preference tag to your intelxdk.config.additions.xml file:

<preference name="android-build-tool" value="gradle" />

before you export your PhoneGap Build package.
The alert() and confirm() functions do not work when using the Simulate tab. If you are using these features for debugging, please use console.log() and the Simulate tab's debug console, instead.

If you are using these features as a functional part of your app, please take a look at the standard Cordova "notification" (aka "dialogs") plugin. This plugin provides much more flexibility and incorporates a look and feel that matches the native platform.
If you experience a crash of the Intel XDK, immediately following an update, and each attempt to start the Intel XDK results in an immediate crash of the Intel XDK, your installation may have been corrupted during installation.

On a Windows system this can be identified by looking at the list of installed applications, where you will find the old version and the new version of the Intel XDK are still listed as "installed."
Follow the instructions in this FAQ to completely uninstall all application files and cache files used by the application from your system. Then download the Intel XDK from xdk.intel.com and reinstall the Intel XDK.
The certificate management tool, the tool that facilitates creating, uploading and converting Android and iOS package certificates, is missing some of the input fields. The tool is incorrectly sized in the vertical direction. There is a small vertical scrollbar to the right of the input fields that can be used to see the "missing" fields in the dialog. See this forum thread for additional details and some helpful screenshots.
The "Cordova Build Package" tool on the Build tab fails to prompt to save a ZIP file. This can be caused by the presence of an inconsistent *.json file in your project's "plugins" folder. See this forum post for a workaround.

Keep Us Informed

To provide us with feedback, report issues, and find answers to your questions, please visit the Intel XDK forum.


Intel® XDK - Release - 2016 December 12, v3759

IMPORTANT: The Debug tab, the hosted weinre server associated with the Test tab and the Live Development pane located on the Develop tab were deprecated as part of our October, 2016 release. With this December, 2016 release of the Intel XDK we have officially retired these features. Retirement means these features are no longer available for use with any version of the Intel XDK. Your project will continue to be recognized as an Intel XDK HTML5 mobile app project and it will continue to build (using the Build tab) and work within the Simulate tab. Additionally, the Test tab is still present and can still be used to send your app to App Preview for on-device testing.

These features were retired because, as previously announced and noted in these release notes, future editions of the Intel XDK will focus on the development of IoT (Internet of Things) apps and IoT mobile companion apps. Since we introduced the Intel XDK IoT Edition in September of 2014, the need for accessible IoT app development tools has increased dramatically. At the same time, HTML5 mobile app development tools have matured significantly. Given the maturity of the free open-source HTML5 mobile app development tools, we feel you are best served by using those tools directly.

See the next section for more details and pointers to free open-source alternatives to these retired features. Finally, we have also retired the Game Asset Manager (GAM) and all associated game samples and templates.

Important Information Regarding Retired Features

A complete summary of mobile app debug options are available on the Debug and Test Overview doc page.

Alternatives to the Debug Tab

We recommend that you use the Simulate tab for basic debugging. You can debug a built Android app directly on-device, with full JavaScript and CSS debugging, by way of remote Chrome* DevTools*. For those who have access to a Mac, it is also possible to use remote web inspector with Safari to debug your built iOS app directly on-device.

Debugging a built app does not require rebuilding your app to test changes or experiment with your code. The best debugging experience will come from taking advantage of the interactive JavaScript console to redefine functions within your app and then run those redefined functions directly from the console or restart your app, in situ, using the window.location.reload() function. An example of using this technique can be seen in this video, starting at about 18:30. The video is demonstrating the use of the weinre debugger, but the debugging techniques can also be applied to remote CDT and remote Web Inspector when debugging a built app.

NOTE: The Intel App Preview app for Android is distributed with the "debug flag" enabled. This means that you can use remote CDT to debug your app within App Preview using a USB connection, as long as you restrict your debugging efforts to code that only interacts with the core Cordova plugins. App Preview does not include any third-party plugins; therefore, you cannot debug any parts of your app that interact with third-party Cordova plugin APIs.

Alternatives to Using the Hosted weinre Debug Server

You can install the weinre JavaScript console server directly on your workstation by following the instructions in Using Node weinre to Debug Cordova* Apps and connecting your built app to that self-hosted weinre console or from within App Preview. For additional help on using weinre locally, watch Using WEINRE to Debug an Intel® XDK Cordova* App (beginning at about 14:30 in the video).

Alternatives to Using Live Development

If you have been using the Run My App feature, we recommend that you use the Simulate tab as an alternative. It is also possible to get on-device JavaScript and CSS debugging for Android devices, by way of remote Chrome* DevTools*.

For those who have been using the Live Layout Editing feature, we recommend using the Simulate tab or the Brackets* Live Preview feature, on which the Intel XDK Live Layout Editing feature is based (the Intel XDK editor is Brackets). The Brackets Live Preview feature utilizes your desktop browser to provide a feature similar to Intel XDK Live Layout Editing. If you use the Google* Chrome browser with Brackets Live Preview you can take advantage of the Chrome device emulation feature to simulate a variety of customizable device viewports.

New Features

This release introduces some new minor features.

Web Services Explorer for IoT Projects.

The Web Service Explorer allows you to make code binding to web services for your IoT apps. This feature was already available for mobile apps and is now enabled for IoT projects, as well.

For more information about using the Web Services Explorer, see the Intel® XDK documentation, here.

Web Services Explorer

Brackets Live Preview

Due to the retirement of the Live Development pane, we have enabled the standard Live Layout feature that is built into the Brackets editor. This feature is accessible from the File menu (Live Preview) or by clicking the "lightning bolt" icon located at the right edge of the editor window.

Brackets' Live Preview

For more information about this feature see the Brackets documentation.

Samples Support for the Intel® Joule™ IoT Development Board

Many of the IoT "templates" have been updated to support the Intel® Joule™ development board. In addition, new IoT sample apps have been added to the "IoT samples" section that are designed to run on the Intel Joule development board.

In some cases you may see duplicate entries for IoT apps located in the "samples" section of the "start a new project" pane. This is normal and is due to the fact that multiple distinct versions of those samples are provided for Galileo, Edison and Joule development boards. Use the filter mechanism, at the upper right of the samples selection pane, to more quickly locate board-specific samples:

Improved IoT Daemon Installation Support

In this release, we have improved the IoT daemon installation and update process. The IoT daemon can now be installed or updated on a supported IoT operating system, even if the daemon is not present on the IoT target device. The Intel XDK IoT daemon has been updated for proper operation on Intel Joule platforms running the Ostro Linux distribution.

Some Intel IoT target platforms do not yet support automatic updating of the Intel XDK IoT daemon. In those instances the Intel XDK should inform you that an automatic update of the daemon cannot be performed. Please post a message on the forum for help with manual installation of the IoT daemon.

Issues Addressed

The following item has been addressed in this release:

  • For Apple* OS X*, the "about" message for the Intel® XDK application had a missing version number. See this forum post for more details.

  • The name of the Apple* OS X* installer was the same as the Intel® XDK application, creating some confusion. Now, the installer is clearly named as such.

  • As part of the Apple* OS X* installation process, an admin password for the user's machine was required. However, the wording in the dialog requesting the password was confusing. See this forum post for more details. Additionally, uninstallation of the previous version of the Intel XDK, during installation, would generate an error message that was incorrectly displayed.

Known Issues

Issue Workaround
Upgrading to the latest version of the Intel XDK results in a build error with existing projects. Some users have reported that by creating a new project, adding their plugins to that new project and then copying the www folder from the old project to the new project they are able to resolve this issue. Obviously, you also need to update your Build Settings in the new project to match those from the old project.
For IoT projects, changing the “Source Directory” to any path other than the default (i.e., the project’s root directory) causes the IoT app to not run on your IoT board. Avoid changing the “Source Directory" in your IoT project, leave the "source directory" blank on the Projects tab.
When a custom web service is added, the service does not appear in the list of available web services. After adding a custom web service via the "add-a-service wizard," restart the Intel XDK to see your new service in the list of available Web Services.
Missing or incorrectly located iOS provisioning file(s) can cause non-iOS build failures or an indication that some build settings need to be corrected, even though the iOS build tile has not selected for build. This is due to the fact that your iOS provisioning files must now be located in the package-assets folder and are being checked for existence regardless of which target tile has been selected for build. Move your iOS provisioning file(s) to the new package-assets folder and then open your iOS Build Settings panel (on the Projects tab) to locate them in the Build Settings UI. See this forum post for additional details. If you project folder does not include a package-assets folder, you can create one in the root of your project folder.
Uploading an iOS app to Apple Developer Store results in an: ITMS-90086: "Missing 64-bit support" error or an ITMS-90096: "Your binary is not optimized for iPhone 5" or an ERROR ITMS-90046: "Invalid Code Signing Entitlements" or a WARNING ITMS-90686: "The binary you uploaded was invalid" or an ERROR ITMS-90167: "No .app bundles found in the package" and similar error messages when using the iOS Application Loader tool. This is a known issue with the Apple Xcode and Application Loader tool. This is not an Intel XDK problem, it is due to changes in the way the Apple Store handles uploading apps into the store, which requires that your Mac has up-to-date Xcode tools.

Simulate tab does not support the retired intel.xdk APIs or the barcode plugin. When your app encounters those APIs it generates a dialog similar to the following:

The new Simulate tab depends on the availability of simulation code that is provided by Cordova plugin developers. This means that a more accurate emulation of specific plugins is possible in the browser environment in which the Simulator (and the old Emulator) runs in (there is no device emulation in either the old Emulate tab or in the new Simulate tab).

The old Emulate tab included legacy code that allowed the PhoneGap barcode plugin to be simulated. However, there is no Simulate tab backend for the PhoneGap barcode plugin, nor for any of the retired Intel XDK plugins. Thus the reason for the dialog shown to the left.

This is proper behavior for the Simulate tab when it encounters a third-party plugin for which there is no "simulate backend" provided by the plugin -- at which point you need to provide the "simulated response" for the API call in order to make your app continue. Additional documentation can be found here:

The Simulate tab does not retain local storage. Use the Debug tab or debug on a built app.
The Simulate tab does not include the ability to specify a starting URL like the Emulate tab did. This means you cannot test web apps using a custom URL. Since you are testing a web app, which, by definition, does not include any Cordova plugins, you can test your app using a browser and a local web server. If you prefer not to setup your own local web server, this "Web Server for Chrome" extension may be a useful alternative. Note, the Chrome browser includes a "device mode" for viewport emulation feature that can be used to simulate rendering your app on a variety of device screens.
If you manually install this version of Intel XDK for Apple* OSX* on a system with an existing Intel XDK version 3522 (or earlier) using a new installation directory, the installer may not completely remove the older version. The newly installed version should be fully functional and you can safely remove the older one, manually.
 

Keep Us Informed

To provide us with feedback, report issues, and find answers to your questions, please visit the Intel XDK forum.


Intel® XDK - Update - 2016 October 19, v3641

This update fixes installer issues encountered during the update process.

Issues Addressed

  • Some errors during (and after) the update process for Microsoft* Windows* and Apple* OS X* corresponding to this forum post and to this forum post, that prevented the previously released version from installing correctly for some users.

Intel® XDK - Release - 2016 October 11, v3619

IMPORTANT: With this release, the Debug tab, the hosted weinre server associated with the Test tab, and the Live Development pane located on the Develop tab have been deprecated and will be retired in the near future. When these features are retired you will no longer be able to use them with any version of the Intel XDK. Your project will continue to be recognized as an Intel XDK HTML5 mobile app project and it will continue to build (using the Build tab) and work within the Simulate tab. Follow the links embedded in each of the deprecated features listed above for more details and pointers to free open-source alternatives to these deprecated features.

In addition to our previously announced deprecation of support for App Framework, within the App Designer UI editor, we are also deprecating support for the use of the Framework7 and Ionic UI frameworks. You can still use these frameworks outside of the App Designer UI editor, as you have always been able to do with any UI framework. Existing projects that are using deprecated UI frameworks will continue to be recognized by App Designer and can be edited within the App Designer UI editor; however, there will be no bug fixes for deprecated frameworks and, once those frameworks are retired, the App Designer UI editor will no longer recognize those projects.

New Features

This release introduces some new minor features.

Keyword-based Filters for New Project Templates and Samples

We have added a keyword-based filter for sorting samples and projects. This filter is located in top right area of the "Start a New Project" screen. Use it to help you to quickly filter project templates based on a set of predefined keywords. Not all samples include keywords, at this time. As the samples are updated to include keywords they will automatically appear as part of this filter.

New Linux* and Apple* OSX* Installers

We have updated and streamlined the Linux and Mac OSX installers. These new installers addresses some issues and annoyances with the previous installers and unify the installation experience for those operating systems.

New IoT Project Samples using Microsoft* Azure*

Two new IoT project samples have been added to the Intel XDK that show how to interact with the Microsoft* Azure* cloud as part of this release. These samples use the azure-iot-* Node.js* packages and show how to send and receive messages from and to the Azure cloud from a network-connected IoT device.

Issues Addressed

The following items have been addressed in this release:

  • Crashes that result in "TypeError: Cannot read property 'getName' of null" and “Assertion Error: projectHandle should not be null” errors, when interacting with the Build and Develop tabs.

  • Crashes that result in "Cannot calculate a resource path of an empty project" errors, when interacting with the Publish tab.

  • Crashes that result in "Cannot read property 'getRootDirectory' of null" errors, when interacting with the Project tab.

  • Crashes that result in "Error: Cannot find module" errors, when interacting with the Simulator.

  • Crashes that happen when interacting with an IoT board and the Wi-Fi network changed, or an invalid proxy was configured.

  • Arbitrary crashes due to configuration problems in the IoT Sensor Explorer.

  • (Linux* only) crashes happening when launching the Intel XDK from the installer program, after the installation was completed.

  • (Windows* only) after cleaning the existing project on an IoT board, the following project upload would fail.

  • Simulator configuration parameters, such as geolocation coordinates, were not preserved when the target OS was changed, resulting in the need to re-enter them.

  • Simulate tab did not simulate double-click actions, as the Emulate tab did. See this forum post for additional details.

  • Simulate tab does not simulate media query properly. See this forum post for additional details.

  • In the Project tab icons and splash screens, the icon thumbnail and image captions were not properly updated when an icon file was updated. See this forum post for additional details.

  • In the Project tab build settings, any text could be entered into the “Minimum Android API” and “Target Android API” fields. Now, those fields are validated to be numeric entries.

  • App Preview would crash on Windows 10 x64 v1607 (Anniversary Update release).

  • Several issues that generated a 'build tab generates ERROR (-9) from "client:upload-manager": Http request failed:' error message have been addressed. This primarily impacted users who with low bandwidth internet connections.

  • In the Build tab, messages with timestamps did not show the time per the time zone of the development system.

Known Issues

Issue Workaround
For IoT projects, changing the “Source Directory” to any path other than the default (i.e., the project’s root directory) causes the IoT app to not run on your IoT board. Avoid changing the “Source Directory" in your IoT project.
When a custom web service is added, the service does not appear in the list of available web services. After adding a custom web service via the "add-a-service wizard," restart the Intel XDK to see your new service in the list of available Web Services.
Missing or incorrectly located iOS provisioning file(s) can cause non-iOS build failures or an indication that some build settings need to be corrected, even though the iOS build tile has not selected for build. This is due to the fact that your iOS provisioning files must now be located in the package-assets folder and are being checked for existence regardless of which target tile has been selected for build. Move your iOS provisioning file(s) to the new package-assets folder and then open your iOS Build Settings panel (on the Projects tab) to locate them in the Build Settings UI. See this forum post for additional details. If you project folder does not include a package-assets folder, you can create one in the root of your project folder.
Uploading an iOS app to Apple Developer Store results in an: ITMS-90086: "Missing 64-bit support" error or an ITMS-90096: "Your binary is not optimized for iPhone 5" or an ERROR ITMS-90046: "Invalid Code Signing Entitlements" or a WARNING ITMS-90686: "The binary you uploaded was invalid" or an ERROR ITMS-90167: "No .app bundles found in the package" and similar error messages when using the iOS Application Loader tool. This is a known issue with the Apple Xcode and Application Loader tool. This is not an Intel XDK problem, it is due to changes in the way the Apple Store handles uploading apps into the store, which requires that your Mac has up-to-date Xcode tools.

Simulate tab does not support the retired intel.xdk APIs or the barcode plugin. When your app encounters those APIs it generates a dialog similar to the following:

The new Simulate tab depends on the availability of simulation code that is provided by Cordova plugin developers. This means that a more accurate emulation of specific plugins is possible in the browser environment in which the Simulator (and the old Emulator) runs in (there is no device emulation in either the old Emulate tab or in the new Simulate tab).

The old Emulate tab included legacy code that allowed the PhoneGap barcode plugin to be simulated. However, there is no Simulate tab backend for the PhoneGap barcode plugin, nor for any of the retired Intel XDK plugins. Thus the reason for the dialog shown to the left.

This is proper behavior for the Simulate tab when it encounters a third-party plugin for which there is no "simulate backend" provided by the plugin -- at which point you need to provide the "simulated response" for the API call in order to make your app continue. Additional documentation can be found here:

The Simulate tab does not retain local storage. Use the Debug tab or debug on a built app.
The Simulate tab does not include the ability to specify a starting URL like the Emulate tab did. This means you cannot test web apps using a custom URL. Since you are testing a web app, which, by definition, does not include any Cordova plugins, you can test your app using a browser and a local web server. If you prefer not to setup your own local web server, this "Web Server for Chrome" extension may be a useful alternative. Note, the Chrome browser includes a "device mode" for viewport emulation feature that can be used to simulate rendering your app on a variety of device screens.
If you manually install this version of Intel® XDK for Apple* OSX* on a system with an existing Intel® XDK version 3522 (or earlier) using a new installation directory, the installer may not completely remove the older version. The newly installed version should be fully functional and you can safely remove the older one, manually.
 

Keep Us Informed

To provide us with feedback, report issues, and find answers to your questions, please visit our forums.


Intel® XDK - Update - 2016 August 22, v3522

Due to a security vulnerability found in Crosswalk version 18 (and earlier), we have made Crosswalk version 19 the default version for newly created projects. This update will warn you of any existing projects using Crosswalk version 18 (or lower). Google does not require that you use Crosswalk 19 (or higher), so this is just a warning, not an error.

NOTE: the debug module that is built for use with the Debug tab will be based on Crosswalk 18 when Crosswalk 19 (or higher) is selected in the Build Settings section of your Project tab. This is due to some unresolved technical issues regarding Crosswalk 19 and debug modules.

This release now properly indicates our previously announced deprecation of support for App Framework within App Designer, as it is no longer being maintained by its developers.

Issues Addressed

This Intel XDK update addresses some key issues affecting users of the 3491 release. The following items have been addressed in this update:

  • Several issues that generated a 'build tab generates ERROR (-7) from "client:upload-manager": Error in zipping package asset files:' error message have been addressed. This primarily impacted Construct2 users who were importing new projects or opening existing projects.

  • The new Simulate tab did not present the window.screen object correctly. See this forum post for additional details.

  • Attempting to run some Cordova apps that did not include any plugins would cause the app to crash or generate a 404 error in the Simulate tab. See this forum post for some examples.

  • Replacing an icon or splash screen with a new file but using the same name for that file would cause an incorrect prompt regarding an invalid resolution. See this forum post for more details.

  • Intel XDK crashes that resulted in "Error: ENOENT" and "Uncaught TypeError: undefined is not a function" errors when using the Simulate tab.

  • Use of the <head data-noxhrfix> tag causes the Simulate tab to fail or hang. See this forum post for additional details.

  • The 750x1334 splash screens (portrait and landscape) have been restored to the iOS Icons and Splash Screens UI.This forum post provides additional details.

  • A custom require() function was placed into the global namespace by the Simulate tab preventing use of require() within a user app. See this forum thread for additional details.

Known Issues

Issue Workaround
When a custom web service is added, the service does not appear in the list of available web services. After adding a custom web service via the "add-a-service wizard," restart the Intel XDK to see your new service in the list of available Web Services.
The Intel XDK Cordova CLI 5.1.1 build option is NOT compatible with Crosswalk version 17 and greater, including the shared Crosswalk library (which was version 19 as of the posting of these release notes). If you are building with CLI 5.1.1 you must select the "Crosswalk Embedded" option and you must select Crosswalk 16 or less. Because CLI 5.1.1 has been deprecated, we highly recommend that you upgrade your app to build with CLI 5.4.1 or CLI 6.2.0, as soon as possible.
The Simulate tab does not simulate double-click actions, as the Emulate tab did. Use the Debug tab or Test tab as an alternative to the Simulate tab.
Missing or incorrectly located iOS provisioning file(s) can cause non-iOS build failures or an indication that some build settings need to be corrected, even though the iOS build tile has not selected for build. This is due to the fact that your iOS provisioning files must now be located in the package-assets folder and are being checked for existence regardless of which target tile has been selected for build. Move your iOS provisioning file(s) to the new package-assets folder and then open your iOS Build Settings panel (on the Projects tab) to locate them in the Build Settings UI. See this forum post for additional details. If you project folder does not include a package-assets folder, you can create one in the root of your project folder.
Uploading an iOS app to Apple Developer Store results in an ITMS-90086 "Missing 64-bit support" error or an ITMS-90096 "Your binary is not optimized for iPhone 5" or an ERROR ITMS-90046: "Invalid Code Signing Entitlements" and similar error messages when using the iOS Application Loader tool. This is a known issue with the Apple Xcode and Application Loader tool. This is not an Intel XDK problem, it is due to changes in the way the Apple Store handles uploading apps into the store, which requires that your Mac has up-to-date Xcode tools.
There is a known security issue with Crosswalk versions 18 and below. Despite this security issue, your Android-Crosswalk application will still be accepted by the Google Play Store if it is built with CW18 or lower. The Intel XDK does not offer direct access to CW19 or CW20 (at the time these release notes were written). As long as the Intel XDK does not offer access to CW19 or CW20, you must use the technique described in this forum post to get access to those versions. NOTE: the Debug tab does not support CW19 or higher, which means you must remove the modifications from your intelxdk.config.additions.xml file to build a Debug module for use with the Debug tab.

Simulate tab does not support the retired intel.xdk APIs or the barcode plugin. When your app encounters those APIs it generates a dialog similar to the following:

The new Simulate tab depends on the availability of simulation code that is provided by Cordova plugin developers. This means that a more accurate emulation of specific plugins is possible in the browser environment in which the Simulator (and the old Emulator) runs in (there is no device emulation in either the old Emulate tab or in the new Simulate tab).

The old Emulate tab included legacy code that allowed the PhoneGap barcode plugin to be simulated. However, there is no Simulate tab backend for the PhoneGap barcode plugin, nor for any of the retired Intel XDK plugins. Thus the reason for the dialog shown to the left.

This is proper behavior for the Simulate tab when it encounters a third-party plugin for which there is no "simulate backend" provided by the plugin -- at which point you need to provide the "simulated response" for the API call in order to make your app continue. Additional documentation can be found here:

The Simulate tab does not retain local storage. Use the Debug tab or debug on a built app.
The Simulate tab does not include the ability to specify a starting URL like the Emulate tab did. This means you cannot test web apps using a custom URL. Since you are testing a web app, which, by definition, does not include any Cordova plugins, you can test your app using a browser and a local web server. If you prefer not to setup your own local web server, this "Web Server for Chrome" extension may be a useful alternative. Note, the Chrome browser includes a "device mode" for viewport emulation feature that can be used to simulate rendering your app on a variety of device screens.
 

Keep Us Informed

To provide us with feedback, report issues, and find answers to your questions, please visit our forums.


Intel® XDK - Release - 2016 August 2, v3491

New Features

Single Intel XDK Product

With this release, the Intel XDK includes the capability to develop Apache* Cordova* mobile HTML5 apps for Android*, iOS* and Windows* 10 UAP, as well as software development capabilities for creating Node.js IoT apps. With this merge of the features found in the Intel XDK IoT Edition and the Intel XDK EA Release, we will no longer be releasing a separate Intel XDK IoT Edition or a separate Intel XDK Early Access installation. Going forward, there will only be one Intel XDK release, or edition.

We are "All-In" on the Internet of Things (IoT)

With respect to IoT, you should expect us to add more functionality for IoT app development over time. As a result, we will be deprecating and eventually removing some mobile app development features that are not well used, or out of date and not worth updating. We will announce such deprecations in Joe's blog, in these Release Notes and in the Intel XDK forum.

Simulate Tab Replaces the Emulate Tab

As part of this release, a new open source simulator for Cordova and HTML5 applications has been integrated into the Intel XDK. You can find the source code for this simulator at: Cordova Simulate. This component replaces the Emulate tab, which was based on the Ripple Emulator. This change was made to improve the stability of this debug component and because it offers better simulation options for the core Cordova APIs.

Some of the new simulator key features and improvements include:

  • Improved simulation for the core Cordova plugins (APIs).
  • Built-in simulation of the Intel App Security API Cordova plugin.
  • A new workflow for managing the simulation session.
  • Faster switching between devices of the same platform.
  • Project consistency: only those plugin APIs that are part of the project are loaded and available.
  • Stability improvements (execution and debugging)

The new Simulate tab only supports those Cordova plugin APIs that include API simulation code. Most third-party Cordova plugins do not include simulation support for their plugin APIs. In those cases, your application code should account for the fact that third-party APIs may not be present when the app is run inside the Simulate tab. This is behavior is similar to the old Emulate tab.

NOTE: Unlike the old Emulate tab, the Simulate tab does not include any support for the now retired intel.xdk.* APIs. Those plugins were retired earlier this year and are no longer supported or recommended for use with the Intel XDK. Those plugins are available as third-party Cordova plugins, but should be retired from your application ASAP and replaced with equivalent third-party Cordova plugins.

For more information regarding the new simulator, please review the Simulate Tab documentation.

Cordova CLI Upgrade

In this release, the default Apache Cordova* build version has been updated to Cordova 6.2.0. The following items are part of this upgrade.

  • With this release we are deprecating CLI 5.1.1. We are recommending that you upgrade your projects to use Cordova CLI Version 5.4.1 or 6.2.0.

  • The build servers have been upgraded to allow building your HTML5 + Cordova apps with Apache Cordova 5.1.1, 5.4.1 or 6.2.0. See this FAQ for additional information regarding the differences between CLI 5.1.1, CLI 5.4.1, and CLI 6.2.0.

  • The Apache Cordova platforms (cordova-android, cordova-ios, and cordova-windows) and the core Cordova plugins have been upgraded as well to the Cordova recommended versions.

NOTE: third-party plugins are developed and maintained by independent developers who are not part of the Intel XDK project and do not work for Intel; we cannot guarantee that all third-party plugins have been updated to work properly with the latest mobile Cordova platforms!

For more information regarding what is new in the Apache Cordova project, on which Intel XDK HTML5 mobile apps are based, please review the Apache Cordova Documentation.

Cordova Operations Cancel

Many users have requested a Cancel function while fetching Cordova plugins into their mobile app project. We have added that feature as part of this release. The Cancel operation is available on the:

  • Plugin Manager UI dialog
  • CLI version change UI dialog
  • Plugin Synchronization dialog

Intel® App Security API Plugin Update

The Intel App Security API featured plugin was updated to version 2.0.0. See the App Security API documentation for more details. Also, refer to the Intel App Security API Release Notes for the latest updates.

Storing Package Assets in a Separate Folder

The Intel XDK now expects graphical assets (package icons and splach screens) and iOS* provisioning files to be put into a separate directory called package-assets located within your project's root folder. With this change, unused assets will not be included along with the final build of your project, reducing the size and improving the security of your apps. Also, when importing an HTML5 project, the Intel XDK now requires the project source directory to be a folder directly below your project's root directory. See Launch Icons and Splash Screens with the Intel XDK. This feature was present in the prior Intel XDK EA Release and has been migrated to the Intel XDK.

Deprecations and Feature Removals

Profile Tab Removed

The Profile Tab has been removed from this version of the Intel XDK. This functionality was redundant with similar features that can be found in the Chrome DevTools (CDT). If you wish to profile your app, please go to the Debug Tab and use the existing CDT profiling features.

Legacy Whitelist (Android) Removed

The Android Whitelist settings have, in the past, included three options ("whitelist," "legacy" and "block all") to control the Android whitelist settings. The "legacy" option was announced as deprecated and that support for that option would be removed in the next release of the Intel XDK. With this release of the Intel XDK, that option has been removed for all new projects and any existing projects that have selected to use the "whitelist" or the "block all" options. Only existing projects that are still set to the "legacy" option will continue to see the "legacy" whitelist option. Changing your project to use either the "whitelist" or the "block all" option will result in permanent removal of the "legacy" option from your project.

In future releases of the Intel XDK the "legacy" option will not be supported for any projects, including existing projects that have selected "legacy" as their whitelist option. Upgrade your project to use the standard Android "whitelist" option ASAP!

Cordova CLI 5.1.1 Deprecated

The Intel XDK CLI 5.1.1 build option has been deprecated. It will be retired with our September 2016 release. You should upgrade your app to CLI 5.4.1 or 6.2.0 ASAP.

Legacy Windows Build Platforms Deprecated

With this release, and the deprecation of Cordova CLI 5.1.1, Windows 8.x, Windows Phone 8.x and older legacy Windows build targets will only be available in Cordova 5.4.1. When using Cordova 6.2.0 only the Windows UAP (aka Windows 10) option will be available for building Cordova Windows applications.

Game Asset Manager (GAM) Deprecated

With this release we are deprecating the Game Asset Manager (GAM) feature of the Intel XDK. Game samples and templates for HTML5 projects will remain until that feature is removed.

Issues Addressed

In addition to the new features listed above, we concentrated on addressing a number of issues reported by our users. Some of those issues addressed include:

  • Corrected validation of the Android Target API field in the build settings to prevent a critical error detected on the Build tab.

  • Corrected an issue where the cancel operation while switching between projects put the Develop/Projects tab into an inconsistent state.

  • Fixed an issue where if a web data service was created or used in project A could result in that web data service appearing to be available in Project B until you restarted the Intel XDK.

  • Corrected an issue where the Intel XDK could crash when downloading the APK after an Android build - on Linux development systems only.

  • Added a warning icon to the "Signed" checkbox within the Android build settings to notify users about the need to sign their APK files in order to submit to a store or test on device.

Known Issues

Issue Workaround
When a custom web service is added, the service does not appear in the list of available web services. After adding a custom web service via the "add-a-service wizard," restart the Intel XDK to see your new service in the list of available Web Services.
The Intel XDK Cordova CLI 5.1.1 build option is NOT compatible with Crosswalk version 17 and greater, including the shared Crosswalk library (which was version 19 as of the posting of these release notes). If you are building with CLI 5.1.1 you must select the "Crosswalk Embedded" option and you must select Crosswalk 16 or less. Because CLI 5.1.1 has been deprecated, we highly recommend that you upgrade your app to build with CLI 5.4.1 or CLI 6.2.0, as soon as possible.
There is a known bug with the Simulate tab and the inclusion of a "data-noxhrfix" attribute in the <head> tag in your application. It appears to be a bug in the Simulate open-source tool and can be caused by adding any "data-*" attribute to the <head> tag. This data attribute is used to change the behavior of App Preview when used with certain JavaScript frameworks. Be sure to remove any "data-*" attributes from your <head> tag if you wish to debug your application in the Simulate tab. See this post for additional details.
Importing Construct2 exported projects do not work. A fix to the Construct2 export tool has been submitted. In the meantime, uninstall 3491 and go here to download and install version 3400 of the Intel XDK.
A custom require() in the global namespace of the Simulator prevents the use of same in a user's app. This is a bug in the open-source Simulator project; a fix is being investigated and will be submitted to the project. Use the Debug tab or Test tab as an alternative to the Simulate tab.
The Simulate tab does not simulate double-click actions, as the Emulate tab did. Use the Debug tab or Test tab as an alternative to the Simulate tab.
Build fails due to "Unable to upload the project files." and "Error in zipping package asset files:" error messages. See this forum thread for help.
Some projects may experience significant "preparing sources" delays with the Simulate tab. See this forum thread for help.
Missing or incorrectly located iOS provisioning file(s) can cause non-iOS build failures or an indication that some build settings need to be corrected, even though the iOS build tile has not selected for build. This is due to the fact that your iOS provisioning files must now be located in the package-assets folder and are being checked for existence regardless of which target tile has been selected for build. Move your iOS provisioning file(s) to the new package-assets folder and then open your iOS Build Settings panel (on the Projects tab) to locate them in the Build Settings UI. See this forum post for additional details. If you project folder does not include a package-assets folder, you can create one in the root of your project folder.
Uploading an iOS app to Apple Developer Store results in an ITMS-90086 "Missing 64-bit support" error or an ITMS-90096 "Your binary is not optimized for iPhone 5" error message. This is a known issue with the Apple Xcode and Application Loader tool. This is not an Intel XDK problem, it is due to changes in the way the Apple Store handles uploading apps into the store, which requires that your Mac has up-to-date Xcode tools.
There is a known security issue with Crosswalk versions 18 and below. Despite this security issue, your Android-Crosswalk application will still be accepted by the Google Play Store if it is built with CW18 or lower. The Intel XDK does not offer direct access to CW19 or CW20 (at the time these release notes were written). As long as the Intel XDK does not offer access to CW19 or CW20, you must use the technique described in this forum post to get access to those versions. NOTE: the Debug tab does not support CW19 or higher, which means you must remove the modifications from your intelxdk.config.additions.xml file to build a Debug module for use with the Debug tab.
"Uncaught module cordova-plugin-* already defined" error messages appear in the Simulate tab debug console. These error messages also appeared in the previous Emulate tab debugger, but the debug console was automatically cleared when you opened the debugger. You can safely ignore those errors. See this forum post for additional information.

Simulate tab does not support retired intel.xdk APIs or the barcode plugin. When my app encounters those APIs it generates a dialog similar to the following:

The new Simulate tab depends on the availability of simulation code that is provided by Cordova plugin developers. This means that a more accurate emulation of specific plugins is possible in the browser environment in which the Simulator (and the old Emulator) runs in (there is no device emulation in either the old Emulate tab or in the new Simulate tab).

The old Emulate tab included legacy code that allowed the PhoneGap barcode plugin to be simulated. However, there is no simulation backend for that plugin, or for any of the now retired Intel XDK plugins. Thus the reason for the dialog shown to the left.

This is proper behavior for the Simulate tab when it encounters a third-party plugin for which there is no "simulate option" -- at which point you need to provide the "simulated response" for the API call in order to make your app continue. Additional documentation can be found here:

The "deviceready" event does not trigger if your Cordova project has no plugins. This results in a variety of error messages in the Simulate and Debug JavaScript debug consoles, such as:

  • Uncaught module cordova/plugin_list not found
  • deviceready has not fired after 5 seconds

and other errors that will be application-specific.

This error condition is an issue that may afflict Construct2 applications which are exported and imported as Cordova apps, but in which no plugins have been defined within the Scirra editor.

See the image below for an example of some of these debug error messages:

This appears to be due to a change in the Cordova initialization code. Changes to the Cordova code are made by the Apache Cordova project and are not controlled or managed by the Intel XDK project or by Intel.

The workaround is to add a Cordova plugin to your project. The easiest one to add is the Cordova Device plugin, since it is very small and is strictly an "informational" plugin. It will not modify the behavior of your application nor does it require any special permissions for your application.

See this forum post for details on how to add the Cordova Device plugin to your Cordova application to workaround this problem.

The Simulate tab does not retain local storage. Use the Debug tab or debug on a built app.
The Simulate tab does not include the ability to specify a starting URL like the Emulate tab did. This means you cannot test web apps using a custom URL. Since you are testing a web app, which, by definition, does not include any Cordova plugins, you can test your app using a browser and a local web server. If you prefer not to setup your own local web server, this "Web Server for Chrome" extension may be a useful alternative. Note, the Chrome browser includes a "device mode" for viewport emulation feature that can be used to simulate rendering your app on a variety of device screens.
 

Keep Us Informed

To provide feedback, report issues and find answers to your questions, please visit our Intel XDK forum.


Versions of the Intel XDK released prior to August 2016 (3400 and older) no longer support the Build tab, Test tab and Intel App Preview. This change was necessary to improve the security and performance of our Intel XDK cloud-based build system. If you are currently running version 3400 or older you must upgrade your copy of the Intel XDK.
Last Updated: 
Wednesday, May 24, 2017
For more complete information about compiler optimizations, see our Optimization Notice.