Release Notes - Intel® XDK

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

Intel® XDK - Update - 2016 August 22, v3522

NOTE: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. Updates will be released to all users within 24 hours of the public release. If you would like to update sooner, download and install the Intel XDK directly from xdk.intel.com.

Versions of the Intel XDK released prior to March 2016 (2893 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 2893 or older you must upgrade to the latest version of the Intel XDK.

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

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

NOTE: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. Updates will be released to all users within 24 hours of the public release. If you would like to update sooner, download and install the Intel XDK directly from xdk.intel.com.

New Features

Single Intel XDK Product

With this release, the Intel XDK not only has all the capabilities you have come to know and love for developing Apache* Cordova* mobile HTML5 apps for Android*, iOS* and Windows* 10 UAP, but it also includes 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. There will only be the Intel XDK release.

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.


Intel® XDK - Update - 2016 June 8, v3400

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.

Issues Addressed:

In this release, we addressed an issue where the Intel XDK could crash upon startup. The crash could have been caused by a variety of reasons; i.e., slow network speed, temporary internet outage, or no user response to the safe Intel XDK restart dialog.

Network speed can occasionally affect the Intel XDK startup time. The Intel XDK dynamically fetches the Cordova plugin information from the web server.  We improved the Intel XDK startup delay for the users under slow network circumstances, where it could take longer than expected to fetch the plugin information. The issue has been fixed by caching the plugin information in the user’s local disk, and using this static copy when we deem the network is slow or disconnected.

In addition, we also fixed the Intel XDK crash issues when the safe restart dialog is displayed upon startup,  but the user does not click any button within two (2) minutes.  This issue has been fixed by removing the time limit, allowing the user to take unlimited time to make a choice.

Keep Us Informed

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


Intel® XDK - Release - 2016 May 19, v3357

Note: Our automatic updater will notify existing Intel XDK users directly within the Intel XDK. Update notifications will be sent to all users within 24 hours of the official release. If you would like the update sooner, you can download it from xdk.intel.com.

Important Note about Old Intel XDK Versions

Beginning with our upcoming June 2016 release, versions of the Intel XDK released prior to March 2016 (2893 and older) will no longer be able to use the Build tab, the Test tab or App Preview. This change is necessary to improve the security and performance of our Intel XDK cloud-based build system. If you are currently running version 2893 or older please plan to upgrade to a newer version as soon as possible.

Version 2893 will continue to work (without the CLI 4.1.2 build option) until our June release, but it (and older versions) will no longer function following our June 2016 release. We encourage you to move to our 3357 release as soon as possible, in preparation for that significant change to our Intel XDK cloud services.

New Features

For this release of the Intel XDK we concentrated on fixing issues reported by our customers via the forums and those gleaned from the crash logs that have been sent to us. Several new features are also available in the builtin Brackets editor (Develop tab).

Editor Updates

In this release we have implemented a Tabs view of open files in the editor (on the Develop tab). To access the tab view, select the View menu item, from the edit window, and select the "Enable Working Files Tabs" option at the bottom of the "View" menu.

The Brackets Extension Manager is now available by clicking the Extension Manager icon in the Brackets toolbar, located at the right edge of the edit window. This is the standard Brackets toolbar, which was removed in prior versions of the Intel XDK. Note that the Brackets "Live Preview" toolbar icon is not present on that toolbar, as it is in a standard Brackets installation, because that function has been augmented with the Intel XDK version of it, called "Live Layout Editing."

The Brackets Git extension is now easier to access, via the Git logo icon in the Brackets toolbar, at the right edge of the editor window. You must install the Git extension to see the icon in the toolbar and to use it as a source control tool for your project. The Git extension is not installed by default. You install the extension either by using the "File > Extension Manager..." menu item or by clicking the "lego block" icon in the Brackets toolbar, at the right edge of the editor window.

Issues Addressed:

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

  • Added validation to the Certificate Alias field of the certificate management tool to allow only ASCII characters. Previously any characters were allowed which caused build errors.

  • Added a Refresh option to the informational box that gets displayed when there is an error contacting our remote build servers. In the past, you could get stuck on the build page and would have to either restart the Intel XDK or leave the build page and return.

  • Corrected an issue where large apps could not be uploaded for building.

  • Added error detection to identify invalid double dash (--) sequences in the intelxdk.config.additions.xml file that can cause builds to run without including your custom intelxdk.config.additions.xml build directives, resulting in incorrect or incomplete builds.

  • On the Build tab, when displaying the Unlock dialog box for iOS* builds the certificate name was missing. This has been corrected.

  • Added messaging to let a user know when the folder identified in the project as the "source directory" does not contain an index.html file, or an index.html does not exist at all. The Intel XDK expects all projects to include an index.html file.

  • Corrected an issue where iOS builds ignored the preference name="target-device" option in the intelxdk.config.additions.xml file.

  • Added deprecation icons and a deprecation message to the App Designer framework selection screen to clearly indicate those UI frameworks that will retired in a future release of the Intel XDK.

  • The new Android certificate signing process has been resolved so that the Intel XDK build system will sign DSA keys using "SHA1withDSA" and will sign RSA keys using "SHA1withRSA" (rather than signing with SHA256). This insures that older Android devices can install apps built with the new certificate management system.

  • An issue that prevented imported RSA keys that used Unicode (non-ASCII) characters in the alias name or the passphrase from working has been fixed. Android keystores generated by the Intel XDK are DSA keys and, therefore, were not subject to this issue.

  • Made a change to prevent the emulator from crashing or hanging when leaving the emulator with the debug window open.  The debug window will now close upon leaving or restarting the emulator.  The user will have to manually restart the debugger. 

Keep Us Informed

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


Intel® XDK - Update - 2016 April 20, v3240

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.

Issues Addressed:

This Intel XDK update addresses some key issues affecting our users. The following items are addressed in this release:

  • When selecting Apache Cordova* CLI 5.4.1 you were not limited to the minimum target of iOS 8 which resulted in developers attempting to build for unsupported platforms and then building what appear to be non-working apps.

  • If the index.html project file was not contained in the "www" directory of the project, The Emulator would display a '404: Intel XDK can't find your app' error.

  • In some cases, if the Publisher Display Name was not populated for a Windows* build, the plugin add and subsequent build for Windows would fail. Validation for requiring the Publisher Display Name has been added.

  • Corrected an issue where sometimes the plugin manager would not allow a third-party/local plugin to be added to the project.

Keep Us Informed

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


Intel® XDK - Release - 2016 March 23, v3088

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

New Features

Cordova Upgrade

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

  • With this release we no longer support Intel XDK Cordova CLI 4.1.2 builds. If you open a project that used Cordova CLI 4.1.2 (or an earlier version of CLI) you MUST update your CLI version. Go to Projects Tab > Build Settings and specify Cordova CLI Version 5.4.1 or 5.1.1. We recommend that you upgrade to CLI 5.4.1, the default CLI version for this release.

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

  • All Cordova plugins are now fetched from the NPM registry instead of the old CPR (Cordova Plugin Registry). Unfortunately, not all plugin authors have migrated their plugins to the new NPM plugin registry. If you have trouble retrieving plugins from the new registry that were available in the old registry you may have to specify that plugin's GitHub in order to add it to your project. See Adding and Managing Plugins in the Intel Docs for help with adding third-party plugins to your project.

  • The old RDN (Reverse Domain Name) dot-separated format used for plugin IDs is automatically converted to the new recommended dash-separated format for all core Cordova plugins that are part of your application and some third-party plugins (those that have entered an "ID conversion map" into the Apache Cordova plugin mapper. Some third-party plugins continue to use the dot-separated format, which is acceptable and will work; however, be aware, that many third-party plugins have converted to the dash-separated plugin ID format, so if you are looking for those plugins in the Cordova plugin registry you may have to search for a new plugin ID. PLEASE 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 versions of Apache Cordova!

  • The Apache Cordova platforms (cordova-android, cordova-ios, and cordova-windows) and the core Cordova plugins have been upgraded to support Android Marshmallow and Apple iOS* 9. PLEASE 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 platforms!

  • The simulation of Windows Phone* devices on the Emulate tab is now "prepared" using the cordova-windows platform, which is the preferred platform for Windows 8.x, Windows Phone 8.1 and Windows 10 universal apps. Formerly, the cordova-wp8 platform was being used. In most cases this change will have little or no impact on your use of the Emulate tab.

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

Certificate Management

This feature makes management of your Apple iOS* and Android* certificates easier, more secure and more flexible. The Intel XDK now helps you create or import Android certificate keystore files and iOS P12 distribution certificate files. The Build Settings section of the Projects tab was enhanced so you can select a signing certificate for the active project (your app) from among those known certificates you previously created and imported using the certificate management tool for your Intel XDK account.

Please see Managing Certificates for Your Intel XDK Account for full details on how to use this new feature, including guiding you through the creation of an iOS P12 distribution certificate file on a Windows or non-Windows development system using the Intel XDK and your Apple developer account.

New Build UI

We have completely overhauled the Build UI on the Build tab as part of this release. It takes advantage of the Certificate Management feature described above, and also allows you to select platforms and build your app for multiple targets with a single mouse click. This new Build tab UI also presents a concise visual dashboard of your build status. See Using the Build Tab and Project Tab Build Settings for complete documentation on the new UI and its use.

Android and Crosswalk* Builds Refactored

The Android and Android-Crosswalk options have been combined into a single target platform in both the Build Settings section of the Projects tab and on the Build tab. In the Android Build Settings section there is a new check-box labeled Optimize your Android build with Crosswalk. When selected, your Android builds will be built with the Crosswalk WebView (which is the recommended configuration for all Android builds). If you de-select that check-box your Android APK will be built to use the "native" Android WebView, which varies with the version of Android and the device onto which your app is installed. Read Improving Android 4.x Performance with Crosswalk to learn the difference between a native Android WebView and the Crosswalk WebView for Android.

Crosswalk Updates

Crosswalk support in the Intel XDK is now fully based on the Crosswalk Webview plugin (AKA "Cordova 4" in Crosswalk docs). When building with CLI 5.4.1 the Cordova Crosswalk 1.5.0 plugin is used to perform a Crosswalk build; with CLI 5.1.1 the Cordova Crosswalk 1.4.0 plugin is used. This includes the creation of custom debug modules for use with the Debug tab, which previously used the older "embedded" build model (aka "Cordova 3" build model) to create these custom debug modules.

The currently supported versions of Crosswalk include 14,15,16 and shared mode. Shared mode is only supported for apps that are distributed via the Google Play store. Additional useful information regarding Crosswalk builds can be find on the Crosswalk FAQs page.

Beginning with CLI 5.x builds, the Intel XDK no longer automatically adds the --ignore-gpu-blacklist Chromium command-line option to your Crosswalk-built package. Please review this FAQ and the links contained with that FAQ for details on how to insure that this option is added to your Crosswalk builds.

New Publish Tab

A new tab has been added to Intel XDK which assists you with creating application publishing assets and information, as well as assisting you with uploading those publishing assets and your Android app packages to a variety of app stores. For a complete description of this new Publish tab, please see Publishing Apps with Intel XDK.

Microsoft Windows 10* Universal Build Target

The Windows Phone target normally builds Windows Phone 8.1 apps. However, you can switch to building the (legacy XAP) cordova-wp8 platform by setting the windows-phone-target-version variable to 8.0 in your intelxdk.config.additions.xml file. This feature is intended as a troubleshooting mechanism for Windows Phone builds, especially if you are migrating an older Windows Phone app to the new build system. The line you must add to the intelxdk.config.additions.xml file is:

<preference name="windows-phone-target-version" value="8.0" />

Intel® App Security API Plugin Update

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

NOTE: The Intel XDK includes 2 technologies, App Security API 1.4.1 and Crosswalk, which support 64-bit Android in different ways. App Security API 1.4.1 adds support for 64-bit Android devices and the latest Crosswalk runtime for shared mode has support for 64-bit Android. Standard Crosswalk builds in the Intel XDK do not support 64-bit Android, but the 32-bit architecture specific APKs are packaged such that they are able to run on 64-bit devices. However, some build configurations will not work on 64-bit devices.

  • "fat" APK Crosswalk builds that include App Security API 1.4.1 will not work on 64-bit ABI devices (only applies when default build settings are overridden via the additions file).
  • Debug modules that include App Security API 1.4.1 will not work on 64-bit ABI devices (because debug modules are fat apks).
  • Crosswalk shared mode builds will not work on 64-bit ABI devices when they include a Cordova plugin with native libs but without 64-bit support (for example, App Security API 1.4.0)

Editor Updates

The built-in Brackets editor has been updated to version 1.6. The previously included Brackets extensions have been updated, and added the following new extensions have been added:

  • Brackets Beautify
  • brackets-file-tree-exclude
  • Documents Toolbar
  • JSHint Configurator
  • Quick MDN Doc
  • Show Whitespace
  • White Space Sanitizer
  • QuickDocsRegEx

Please note, you must use the Brackets extension manager (under the File menu) to add, update or delete the included Brackets extensions; they are not enabled by default in the editor.

Emulator Updates

We added a simulation of the Asus Zenfone 2 viewport and userAgent string.

NOTE: the Emulate tab should never be used to test your app for publication! You should always test a built version of your application before distributing it to end users. Please read the Emulate tab limitations for more information.

Build Settings Updates

The build setting defaults for Android target and iOS target have been updated. Android to 23 and iOS to 8.0.

Whitelist settings have been updated for the various platforms.

For Android:

  • Renamed "Cordova Whitelist" to "Cordova Android Whitelist" (selecting this option will result in cordova-plugin-whitelist 1.2.1 being added to your project). "Cordova Android Whitelist" is the default whitelist option for new projects.

  • Renamed "W3C Widget Access" to "Cordova Legacy Whitelist" (selecting this option will result in cordova-plugin-legacy-whitelist 1.1.1 being added to your project). "Cordova Legacy Whitelist" is deprecated and will be removed in the next release.

  • Entry sections text has been updated for consistency with Cordova Whitelist: Network Request (<access>), Intent (<allow-intent>), Navigation (<allow-navigation>)

For iOS:

  • Renamed "W3C Widget Access" to "Cordova iOS Whitelist."
  • Added "Intent (<allow-intent>)" and "Navigation (<allow-navigation>)" support.
  • Added support for new ATS attributes, minimum-tls-version and requires-forward-secrecy (CLI 5.4.1 only).
  • CLI 5.4.1 only supports whitelisting on iOS 9 and later.

For Windows:

  • Renamed "W3C Widget Access" to "Cordova Windows Whitelist."
  • Added "Navigation (<allow-navigation>)" (Windows 10 only).

NOTE: Upgrading or downgrading CLI only affects plugin and CLI versions, other settings must be manually changed. This is especially important for platform targets such as those previously noted and whitelist settings as specified above.

App Preview Updates

As part of this release, Intel App Preview has been updated to version 2.8.0 on all supported platforms. The following updates have been made:

  • Cordova CLI version updated to 5.4.1
  • Platform frameworks have been updated to match the CLI 5.4.1 "pinned" versions
  • Updated Cordova plugins to match the CLI 5.4.1 default core plugins
  • Only the intel.xdk.audio, cach, device, and player plugins are included in this release
  • Main screen now displays the currently logged in user
  • Switched the included Barcode scanner plugin to the Phonegap Barcode
  • Feedback is now provided when running apps to inform you if your Cordova platform version and/or selected plugins are supported in App Preview

App Designer Updates

  • Topcoat -- This UI framework has been deprecated and will be retired from App Designer in a future release of the Intel XDK. You can always use this (or any mobile) framework with the Intel XDK, but you will have to do so manually, without the help of the Intel XDK App Designer UI layout tool. If you wish to continue using Topcoat without the aid of App Designer, please visit the Topcoat project page and the Topcoat GitHub repo for documentation.

  • Ratchet -- This UI framework has been deprecated and will be retired from App Designer in a future release of the Intel XDK. You can always use this (or any mobile) framework with the Intel XDK, but you will have to do so manually, without the help of the Intel XDK App Designer UI layout tool. If you wish to continue using Ratchet without the aid of App Designer, please visit the Ratchet project page and the Ratchet GitHub repo for documentation.

  • jQuery Mobile -- This UI framework has been deprecated and will be retired from App Designer in a future release of the Intel XDK. You can always use this (or any mobile) framework with the Intel XDK, but you will have to do so manually, without the help of the Intel XDK App Designer UI layout tool. If you wish to continue using jQuery Mobile without the aid of App Designer, please visit the jQuery Mobile API page and jQuery Mobile GitHub page for documentation.

Known Issues:

Issue Workaround
When unlocking your Apple developer certificate on the iOS platform on the Build tab, the certificate name is missing from the fist sentence in the dialog box. Look at the iOS tab under Projects tab > Build Settings to determine the certificate being used.
Offline Mode ONLY: If you are working offline (i.e. not connected to a network) and you create a new project using the HTML5 + Cordova blank template and select the App Designer checkbox, You will not be able to build for Android. Create a Blank Standard HTML5 project with App Designer. Then, on the Projects Tab, Click on the Cordova icon next to Upgrade: to upgrade your project to HTML5 + Cordova
If you edit files in your plugins folder, the changes will not be seen in the emulator until you restart the Intel XDK. After editing any of the files in the plugins folder, save them, exit the Intel XDK, then restart Intel XDK.
If you change your plugin selections, the emulator will not automatically restart, even if the auto-refresh option is active. Refresh/restart the Emulator.
If the Intel XDK receives an HTTP error code from our servers while processing a build from the Build tab, the Build display may be replaced with an error message with no obvious way to get the build status page back. Either switch Intel XDK projects, or close and reopen the Intel XDK to get the build tab back.
On some devices (including Asus Zenfone 2), a timeout error occurs when debugging from Intel XDK unless Intel App Preview is started manually first. Start Intel App Preview on device prior to starting your debugging session.
If you upload an RSA cert, you will get an SHA256 APK signature which will not be compatible with some older Android devices (4.0-4.3). Either resign with jarsigner locally to use the desired algorithm (RSAwithSHA1), or use a DSA certificate instead.
The Emulate tab can generate a "404: Intel XDK can't find your app" error if project does not use "project-root/www" folder layout. Please see this forum post and this FAQ for additional information and a workaround.
 
 

Keep Us Informed

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


 

Intel® XDK - Update - 2016 January 21 v2893

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

Issues Addressed:

This Intel XDK update helps users who are impacted by Kaspersky and Norton falsely flagging one of the included files (namely binding.node) in the Intel XDK v2807 installer as Trojan. We have rebuilt the source code, producing a different timestamp, for the Intel XDK installer file and scanned this update against major Anti-virus software vendors including Norton and Kaspersky. The scan showed that this updated version is clean.

Intel has reported this problem to Kaspersky and Norton, working with them to resolve this false detection problem. Updates on the resolution progress will be posted on the Intel XDK user forum.

Keep Us Informed

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


 

Intel® XDK - Release - 2015 December 14 v2807

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

New Features

Bower Package Manager

For this release of Intel XDK we have added built-in support for Bower*: a dependency manager for handling HTML5, JavaScript* and CSS libraries and framework packages. With the Bower Package Manager you can easily manage the HTML5, JavaScript and CSS dependencies of your application. You can:
  • Browse and discover available packages to add to your project with the Bower Packages Explorer
  • Search the Bower registry by name, and filter by keywords or categories
  • Select to see the full description of the package as well as, the available versions and dependencies that requires. This helps you to quickly find the package that suite your project needs.
  • Fetch, install, update and remove packages as you need
The Bower Package Manager keeps track of your project dependencies using the bower.json file. The bower.json file is a new metadata file that will be part of your project as soon as you start using Bower. This file is the key to describe your project dependencies and their versions. You can identify your project packages as production dependencies or development dependencies, allowing usage of your packages in your development process.

Start managing your Bower packages from the Project Tab, and if you prefer to continue editing the bower.json file manually, go to the Develop Tab, open the bower.json file, and you will find some helpful shortcuts to manage your Bower packages.

Please see Installing and Maintaining Bower packages for details on how to manage dependencies with Bower Package Manager for the Intel XDK.
 

Resource Monitoring for Apple iOS*

This feature allows you to develop HTML5 code in the Intel XDK and then use the Profile tab to record performance data while your app is connected to an iOS device via a USB connection. You can use the gathered data to triage performance and memory issues for further optimization.

Please see CPU and Memory Profiling - Profile Tab for additional details.
 

App Designer WYSIWYG Editor

The App Designer now provides a WYSIWYG Editor to simplify text formatting. You can apply various formatting styles, from bold, italic, underline, headings, ordered and unordered lists to superscript and subscript.

Please see App Designer Overview for additional details.
 

Intel® App Security API Plugin Update:

The Intel App Security API featured plugin was updated to version 1.4.0. See https://software.intel.com/en-us/app-security-api/api.

Also, refer to the Intel App Security API Release Notes for the latest updates.
 

Appmobi* Secure Mobile Platform Plugin

We have added support for Appmobi's new Secure Mobile Platform which delivers a suite of secure mobile services to Cordova* apps. The platform offers the following services built on this secure framework: Push Messaging, Live Update (update deployed apps without the app store), Data Store (on server and on device), authentication integration, and Analytics. These services are integrated into the app via a Cordova plugin, which is now one of the Featured Plugins in the Intel XDK.

To learn about new AppMobi secure services, see the Appmobi Documentation or use the featured AppMobi plugin and the sample.
 

Ordering Change when Creating New Projects from Templates, Samples and Demos

Please note that in this release the order presented for creation of a new project from a template or a Sample and Demo has switched to place HTML5 + Cordova projects as the first/default choice, with HTML5 projects as the second.
 

Issues Addressed:

  • Addressed a number of issues raised by our users via the forums or support emails.
    • Missing iOS icons in projects settings
    • iOS 87x87 icon is no longer processed
    • Android App ID with leading uppercase letter will fail to install
    • XDK script "XDKLauncherDomain.js" can't read (Default) value from registry on Windows
  • Corrected an issue where the release notes pop up in a node-webkit window instead of browser on update available message.
  • Cleaned up error messaging when attempting a 3rd party plugin fetch from git with no internet.

Important Information About Removed Build Platforms

As stated in the previous Intel XDK Release Notes (see below), the following build platforms have been removed from the Build Tab for this release.
  • All build targets previously located in the Legacy Hybrid Mobile App Platforms section. Please migrate any projects that had relied on these builds to Cordova based builds.
  • The Facebook* target in the Build As A Web App section.
  • The Firefox* target in the Build As A Web App section.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
If you change your plugin selections, the emulator will not automatically restart, even if the auto-refresh option is active. Refresh/restart the Emulator.
If your "source" directory is blank or does not exist (meaning your index.html file is located at the root of your project, rather than within a source folder inside your project directory, typically named "www"), when you build your app it will include the entire contents of the "plugins" directory located within your project directory. In order to eliminate this issue and ensure future compatibility with updates to the Cordova subsystem of the Intel XDK, you should create a "source" directory (typically named "www") inside your project directory and move your index.html and other application source and asset files into that source directory. You must then also set the Intel XDK project properties to point to that new "www" directory located within your project directory. It is safest to do this with a copy of your project directory. For detailed instructions, see this forum post: https://software.intel.com/en-us/forums/intel-xdk/topic/593870#comment-1840292.
It is possible during an update of the Intel XDK that not all files get properly removed before the update and the Intel XDK will crash with an "Error: ENOENT, no such file or directory" error. This can happen if you have a file/directory open in another process during the update. In order to eliminate this issue and install the latest Intel XDK:
  1. Make sure there are no processes open that are using Intel XDK files;
  2. Remove all the files from your Intel XDK installation directory;
  3. Download the Intel XDK from intel.xdk.com;
  4. Insall the downloaded file
After an Intel XDK update on an OS X system, you may see an error when attempting to create a project. Close and restart the Intel XDK to solve this issue.
 
 

Keep Us Informed

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

 

Intel® XDK - Update - 2015 November 20 v2727

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

Issues Addressed:

  • Fixed an issue introduced in Intel XDK version 2673 App Designer where App Framework 3 widgets were being inserted into App Framework 2 projects.
  • Corrected an issue in App Designer where Ionic* Icon List Item was not showing an icon.
  • Corrected an issue where updating the ionic keyboard plugin using the plugin manager would sometimes cause a crash of the Intel XDK.

Important Information About Build Platforms Being Removed

The following build platforms have been deprecated and will be removed from the Intel XDK Build Tab on/about December 14, 2015.
  • All build targets currently located in the Legacy Hybrid Mobile App Platforms section. Please migrate any projects relying on these builds to Cordova based builds now.
  • The Facebook* target in the Build As A Web App section.
  • The FIrefox* target in the Build As A Web App section.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
If you change your plugin selections, the emulator will not automatically restart, even if the auto-refresh option is active. Refresh/restart the Emulator.
If your "source" directory is blank or does not exist (meaning your index.html file is located at the root of your project, rather than within a source folder inside your project directory, typically named "www"), when you build your app it will include the entire contents of the "plugins" directory located within your project directory. In order to eliminate this issue and ensure future compatibility with updates to the Cordova subsystem of the Intel XDK, you should create a "source" directory (typically named "www") inside your project directory and move your index.html and other application source and asset files into that source directory. You must then also set the Intel XDK project properties to point to that new "www" directory located within your project directory. It is safest to do this with a copy of your project directory. For detailed instructions, see this forum post: https://software.intel.com/en-us/forums/intel-xdk/topic/593870#comment-1840292.
It is possible during an update of the Intel XDK that not all files get properly removed before the update and the Intel XDK will crash with an "Error: ENOENT, no such file or directory" error. This can happen if you have a file/directory open in another process during the update. In order to eliminate this issue and install the latest Intel XDK:
  1. Make sure there are no processes open that are using Intel XDK files;
  2. Remove all the files from your Intel XDK installation directory;
  3. Download the Intel XDK from intel.xdk.com;
  4. Insall the downloaded file
After an Intel XDK update on an OS X system, you may see an error when attempting to create a project. Close and restart the Intel XDK to solve this issue.
 
 

Keep Us Informed

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

 

Intel® XDK - Release - 2015 November 10 v2673

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

New Features

For this release of the Intel XDK we concentrated on fixing issues reported by our customers via the forums and through crash logs sent in. We also worked to clean up some issues around plugin fetching and the upgrade to support Apache Cordova* 5.1.1. There were a few feature updates as described below.
 

Windows Phone 8.1* Build Added to Cordova Hybrid App Platform

The Intel XDK now provides a new Build tab tile under Cordova Hybrid Mobile App Platforms for Windows Phone 8.1*. In the projects tab, we have also updated the Build Settings and Launch Icons and Splash Screens sections to provide a common Windows tab to specify app settings for building and submitting of Windows 8* as well as Windows Phone 8.1 apps.

For additional details on using the Project Tab settings and the new build option, see Building Intel® XDK Cordova* Hybrid Apps. Also, see Side-Loading Windows* Phone Apps.
 

App Designer Updates

  • App Designer has been updated to support App Framework version 3.0.
  • Added the Cordova Camera Widget. When inserted into a design, this widget causes two other widgets to be inserted: a button and an img, and it hooks them up with JavaScript* for the user so that clicking the button opens the Camera. Also, selecting an image (or taking a shot) puts the resulting picture into the img widget. If used in a non-Cordova project it asks if you want to upgrade. If the project doesn’t have the Cordova Camera plugin added already, it is added for the user.
  • Framework7* has come out with a Material Design theme which helps your Framework7 designs look more like Android* and less like Apple iOS*. App Designer now supports it as a theme option.

Editor Updates

Brackets* built-in code editor has been updated to version 1.5.
 

Emulator Updates

The device emulator provides a facility during an Intel XDK session to ask the user how to handle the native code in unknown Cordova plugins for which the emulator does not have have simulated replacement routines. For details, see Unimplemented Cordova* Plugin API Support in the Device Emulator.
 

Installer Updates

Two checkboxes have been added to the last screen of the install process. One allows you to view a Getting Started video, and the second opens the Intel XDK Getting Started tutorial. These two checkboxes are not selected by default. A new Intel XDK user check these boxes to view get started information.
 

Issues Addressed:

  • Corrected the following items from the Known Issues list of build 2611.
    • If you edit files in your plugins folder, the changes will not be seen in the device emulator until you restart the Intel XDK.
    • Some 3rd-party Cordova plugins located in the new NPM Cordova plugin registry have a mismatch between the plugin‘s npm module name and the plugin’s ID.
    • An intermittent “dependency violation” error has been noticed on Windows when changing the Cordova CLI version in the Projects tab. Once this error occurs, the project becomes corrupted, and subsequent plugin operations are unreliable.
  • Fixed an issue that would sometimes cause dependent plugins to be removed when they should not have been. This occurred when two plugins each had the same dependent plugin. When deleting one of the two it would also remove the dependent plugin that the other needed.
  • Corrected an issue where the Intel XDK launch icon did not appear in the Application launcher (Linux only).
  • Corrected an issue with embedded Crosswalk builds that would prevent them from being published in the Google Play store when an app included plugins that contained native code libraries (e.g., SQLite and App Security plugins). Embedded Crosswalk APKs are now properly "scrubbed" of excess native code libraries so the Crosswalk ARM APK only contains ARM native code and the Crosswalk x86 APK only contains x86 native code.

Important Information About Build Platforms Being Removed

The following build platforms have been deprecated and will be removed from the Intel XDK Build Tab on/about December 14, 2015.
  • All build targets currently located in the Legacy Hybrid Mobile App Platforms section. Please migrate any projects relying on these builds to Cordova based builds now.
  • The Facebook* target in the Build As A Web App section.
  • The FIrefox* target in the Build As A Web App section.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
If you change your plugin selections, the emulator will not automatically restart, even if the auto-refresh option is active. Refresh/restart the Emulator.
If your "source" directory is blank (meaning your index.html file is located at the root of your project, rather than within a folder inside your project directory, typically named "www"), when you build your app it will include the entire contents of the "plugins" directory located within your project directory. In order to eliminate this issue and insure future compatibility with updates to the Cordova subsystem of the Intel XDK, you should create a "source" directory (typically named "www") inside your project directory and move your index.html and other application source and asset files into that source directory. You must then also set the Intel XDK project properties to point to that new "www" directory located within your project directory. It is safest to do this with a copy of your project directory. For detailed instructions, see this forum post: https://software.intel.com/en-us/forums/intel-xdk/topic/593870#comment-1840292.
It is possible that during an update of the Intel XDK that not all files get properly removed before the update and the Intel XDK will crash with an "Error: ENOENT, no such file or directory" error. This can happen if you have a file/directory open in another process. In order to eliminate this issue and install the latest Intel XDK, first make sure there are no processes open that are using Intel XDK files. Next, remove all the files from your Intel XDK installation directory, then download the Intel XDK from intel.xdk.com and install.
After the update on OS X, you may see an error when attempting to create a project. Restarting the Intel XDK solves this issue.
 
 

Keep Us Informed

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

 

Intel® XDK - Update - 2015 October 21 v2611

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

Issues Addressed:

  • Fixed an issue that would cause errors and some plugins to disappear when downgrading the Cordova* CLI and plugin versions.
  • Fixed an issue that would cause a plugin add to hang when adding and Intel XDK Plugin as a third party registry plugin.
  • Corrected an issue where you could no longer import a project that was created via the Cordova command line.
  • Addressed a couple of App Designer issues reported in crash logs sent in by our users.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
If you edit files in your plugins folder, the changes will not be seen in the device emulator until you restart the Intel XDK. After editing any of the files in the plugins folder, save them, exit the Intel XDK, then restart Intel XDK.
If you change your plugin selections, the emulator will not automatically restart, even if the auto-refresh option is active. Refresh/restart the Emulator.
Some 3rd-party Cordova plugins located in the new NPM* Cordova plugin registry have a mismatch between the plugin‘s NPM module name and the plugin’s ID.

The old Cordova plugin registry used reverse-domain “dot-notation” IDs (e.g., "org.apache.cordova.device”); whereas, the new Cordova plugin registry recommends using NPM package name “dash-notation” IDs (e.g., "cordova-plugin-device"). Unfortunately, this change has not been well communicated by the Cordova project and some plugin authors are using a dot-notation plugin ID with an NPM dash-notation package name. This can cause problems for the underlying Cordova “plugin add” operations used by the Intel XDK to import plugins into your Intel XDK project directory.

In the old Cordova plugin registry the plugin’s package name and ID match (X.Y.Z). In the new Cordova plugin registry, most plugins have changed their IDS to the dash-notation (X-Y-Z) to match their new NPM package names. Unfortunately, some plugins did not change the plugin ID but did change the package name when they were published to the new registry.

As the result of this inconsistency, some plugins can be fetched using an X-Y-Z style NPM module name, but the plugin ID displayed by the Intel XDK plugin manager may be displayed in the old X.Y.Z format. For adding, removing and including such plugins in a build, this situation is normally fine. However, if you try to change the version or variables associated with that plugin, using the plugin manager, this inconsistency will causes problems. Since we handle changes to any plugin that is stored in the Cordova registry by referencing its plugin by ID, we will always attempt to change such plugins via their ID (which is in X.Y.Z notation in these cases). Such changes result in a refetch of the plugin, which will be referenced by ID@version, which may not exist in either the old Cordova.io registry or new Cordova NPM registry.

This error results in a false “plugin not found” error message.
Remove the plugin manually, using the plugin manager (on the Project tab) and add back the new version of the desired plugin.
If your "source" directory is blank (meaning your index.html file is located at the root of your project, rather than within a folder inside your project directory, typically named "www"), when you build your app it will include the entire contents of the "plugins" directory located within your project directory. In order to eliminate this issue and insure future compatibility with updates to the Cordova subsystem of the Intel XDK, you should create a "source" directory (typically named "www") inside your project directory and move your index.html and other application source and asset files into that source directory. You must then also set the Intel XDK project properties to point to that new "www" directory located within your project directory. It is safest to do this with a copy of your project directory. For detailed instructions, see this forum post: https://software.intel.com/en-us/forums/intel-xdk/topic/593870#comment-1840292.
It is possible that during an update of the Intel XDK that not all files get properly removed before the update and the Intel XDK will crash with an "Error: ENOENT, no such file or directory" error. This can happen if you have a file/directory open in another process. In order to eliminate this issue and install the latest Intel XDK, first make sure there are no processes open that are using Intel XDK files. Next, remove all the files from your Intel XDK installation directory, then download the Intel XDK from intel.xdk.com and install.
After the update on OS X, you may see an error when attempting to create a project. Restarting the Intel XDK solves this issue.
An intermittent “dependency violation” error has been noticed on Windows when changing the Cordova CLI version in the Projects tab. Once this error occurs, the project becomes corrupted, and subsequent plugin operations are unreliable. The best workaround is to create a new project and copy all your sources in the old www directory to the new project. Then add all the wanted plugins using the plugin manager on the Projects Tab.
 
 

Keep Us Informed

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

 

Intel® XDK - Update - 2015 October 02 v2548

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

Issues Addressed:

  • Fixed an issue where CLI did not support a project that was created on an alternative partition or flash drive that was different from the Intel XDK installation.
  • Corrected a Proxy issue where NPM uses its own proxy variable that was not being used by the Intel XDK.
  • Added an error message to warn the user regarding a plugin checksum error before project upload to build server instead of failing on the build.
  • We now provide messaging during the build that informs the user that a minimum Android API level of 14 is requrired when using CLI 5.1.1, and automatically update the version. If a user needs to support an Android API level of less than 14, they must build with an older CLI. Also reference this forum post that provides additional information: https://software.intel.com/en-us/forums/intel-xdk/topic/594778
  • Corrected the following previously known issue: LINUX ISSUE ONLY: the Linux client may rarely crash upon closing of the Intel XDK.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
If you edit files in your plugins folder, the changes will not be seen in the device emulator until you restart the Intel XDK. After editing any of the files in the plugins folder, save them, exit the Intel XDK, then restart Intel XDK.
If you change your plugin selections, the emulator will not automatically restart, even if the auto-refresh option is active. Refresh/restart the Emulator.
Some 3rd-party Cordova plugins located in the new NPM Cordova plugin registry have a mismatch between the plugin‘s npm module name and the plugin’s ID.

The old Cordova plugin registry used reverse-domain “dot-notation” IDs (e.g., "org.apache.cordova.device”); whereas, the new Cordova plugin registry recommends using NPM package name “dash-notation” IDs (e.g., "cordova-plugin-device"). Unfortunately, this change has not been well communicated by the Cordova project and some plugin authors are using a dot-notation plugin ID with an NPM dash-notation package name. This can cause problems for the underlying Cordova “plugin add” operations used by the Intel XDK to import plugins into your Intel XDK project directory.

In the old Cordova plugin registry the plugin’s package name and ID match (X.Y.Z). In the new Cordova plugin registry, most plugins have changed their IDS to the dash-notation (X-Y-Z) to match their new NPM package names. Unfortunately, some plugins did not change the plugin ID but did change the package name when they were published to the new registry.

As the result of this inconsistency, some plugins can be fetched using an X-Y-Z style NPM module name, but the plugin ID displayed by the Intel XDK plugin manager may be displayed in the old X.Y.Z format. For adding, removing and including such plugins in a build, this situation is normally fine. However, if you try to change the version or variables associated with that plugin, using the plugin manager, this inconsistency will causes problems. Since we handle changes to any plugin that is stored in the Cordova registry by referencing its plugin by ID, we will always attempt to change such plugins via their ID (which is in X.Y.Z notation in these cases). Such changes result in a refetch of the plugin, which will be referenced by ID@version, which may not exist in either the old Cordova.io registry or new Cordova NPM registry.

This error results in a false “plugin not found” error message.
Remove the plugin manually, using the plugin manager (on the Project tab) and add back the new version of the desired plugin.
If your "source" directory is blank (meaning your index.html file is located at the root of your project, rather than within a folder inside your project directory, typically named "www"), when you build your app it will include the entire contents of the "plugins" directory located within your project directory. In order to eliminate this issue and insure future compatibility with updates to the Cordova subsystem of the Intel XDK, you should create a "source" directory (typically named "www") inside your project directory and move your index.html and other application source and asset files into that source directory. You must then also set the Intel XDK project properties to point to that new "www" directory located within your project directory. It is safest to do this with a copy of your project directory. For detailed instructions, see this forum post: https://software.intel.com/en-us/forums/intel-xdk/topic/593870#comment-1840292.
It is possible that during an update of the Intel XDK that not all files get properly removed before the update and the Intel XDK will crash with an "Error: ENOENT, no such file or directory" error. This can happen if you have a file/directory open in another process. In order to eliminate this issue and install the latest Intel XDK, first make sure there are no processes open that are using Intel XDK files. Next, remove all the files from your Intel XDK installation directory, then download the Intel XDK from intel.xdk.com and install.
After the update on OS X, you may see an error when attempting to create a project. Restarting the Intel XDK solves this issue.
An intermittent “dependency violation” error has been noticed on Windows when changing the Cordova CLI version in the Projects tab. Once this error occurs, the project becomes corrupted, and subsequent plugin operations are unreliable. The best workaround is to create a new project and copy all your sources in the old www directory to the new project. Then add all the wanted plugins using the plugin manager on the Projects Tab.
 
 

Keep Us Informed

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

 

Intel® XDK - Release - 2015 September 23 v2496

Note: Our automatic updater will notify existing Intel XDK users when a new version (update) is available within the Intel XDK. Intel XDK updates will be released to all users within 24 hours. If you would like an update sooner, download it from intel.xdk.com.
 

New Features:

Project Version Update

NOTE: With this release of the Intel XDK, the version of the project configuration files (the <project-name>.xdk/xdke files located insside your project directory) have been updated to 2.0.0 from 1.2. Project configuration files must be updated to this new 2.0 format before this new version of the Intel XDK can work on your project.

This configuration file change means that you will be prompted to upgrade your project under any of the following conditions:
  • The first time you run this new version of the Intel XDK,you will be asked you to upgrade your saved “current” project..
  • When you select a project created with an older version of the Intel XDK from your list of projects.
  • When you open a project using the OPEN AN INTEL XDK PROJECT button, and that project was created with an older version of the Intel XDK.
If you choose to cancel the upgrade you will be prompted again to upgrade that project the next time you attempt to access it using any of the above actions with this new release of the Intel XDK.

IMPORTANT: The upgrade process does not change any source files in your project directory! It only changes the <project-name>.xdk and <project-name>.xdke files located in your project's root directory. Once you have upgraded a project, it can no longer be opened by previous versions of the Intel XDK. The upgrade process does create a backup of your project configuration files named <project-name>_1.2.0.xdk_bak and <project-name>_1.2.0.xdke_bak. If for any reason you need to revert to using a previous version of the Intel XDK, you can delete the <project-name%gt;.xdk and <project-name&g;.xdke files and rename <project-name>_1.2.0.xdk_bak to <project-name>.xdk and <project-name>_1.2.0.xdke_bak to <project-name>.xdke.

Cordova Updates

  • Updated the default Apache Cordova* build version to Cordova 5.1.1. To choose the Cordova build version, visit Projects tab > Build Settings for each platform.
  • Build servers have been upgraded to allow building your HTML5 + Cordova apps with Apache Cordova 4.1.2 or 5.1.1

    NOTE: Cordova 3.3 or 3.5 builds are no longer available with this release.
  • The official Cordova Project plugin registry has moved to NPM*. The old Cordova plugin registry has been placed into a “read-only” state, so it is still accessible, but the plugins hosted by the old registry cannot be updated by the respective plugin authors. Eventually, the Cordova Project will turn off the old plugin registry, at which point any plugins in your project that are being pulled from that registry will no longer be available from that location.

    Technically, the new NPM registry requires Cordova CLI 5; however, our new plugin management system (See Plugin Fetching section below) that is part of this Intel XDK release attempts to minimize the need to move your project to CLI 5 before you are ready. This release of the Intel XDK includes a copy of CLI 5 internally, so it can retrieve plugins from the new registry, even if you choose to build a CLI 4 project. Unfortunately, we cannot fix all of the issues that may arise as a result of this transition to the new Cordova plugin registry, so some projects may require manual intervention when the old plugin registry is turned off.

    If you are using third-party plugins AND you reference them ONLY by their plugin ID, then you have been retrieving those plugins from the old Cordova plugin registry. Our new plugin management tool, will attempt to automatically retrieve those third-party plugins from the new Cordova plugin registry, if it finds the old plugin registry is no longer available. For plugins that have not been moved to the new registry by the plugin author, you will have to manually change the reference to those plugins as either a git repo plugin (fetched from a GitHub repo or a local git repo) or identify an appropriate replacement plugin that is available from the new registry.

    See this announcement from the Cordova Project for additional details.

    The Cordova Project is an open source project that the Intel XDK project contributes to. We do not control the choices made or the actions taken by the Cordova committee. Additionally, the plugins you use in your project have been written and are managed by independent plugin authors. It is the responsibility of the plugin authors to adapt their plugins to this change, the Intel XDK cannot effect that change to third-party plugins. Applications that use only the “core” Cordova plugins and the “legacy” Intel XDK plugins should not experience any significant issues with this transition.

Plugin Fetching:

In previous versions of the Intel XDK, the Apache Cordova* plugins used with your app were retrieved at build time by the cloud build system. Now, the Intel XDK fetches those plugins directly into your project directory (into the plugins directory) as soon as you specify them using the plugin manager UI on the Projects tab. The plugins are then uploaded to the cloud-based build server when you build you app.

This change means you must have a network connection to make plugin changes and the time to upload your project will increase, because the upload includes the plugins used to build your app, in addition to your application source files and other assets. It also means that you can customize the plugins used by your app (by modifying their sources inside the plugins directory) and that you will always build against the same version of a plugin, which the previous mechanism could not guarantee.

NOTE: Only the code elements of the plugins are added to your built application package (APK, IPA, etc.), so there is no increase in the size of your built application, only in the size of the bundle that must be uploaded to the build system. In future releases of the Intel XDK we will be implementing optimizations to minimize the size of the bundle that must be uploaded to the build server with each build. As part of this new plugin fetching feature, we have also modified the UI that you use to select plugins for use in your project. You can find the new settings on the Projects Tab in the Plugin Management section under the Cordova Hybrid Mobile App Settings.

Please see Adding and Managing Plugins for details on these new settings.

App Preview Custom Debug Modules

App Preview custom debug modules is a new feature of the Debug and Profile tabs (and the “Run my App” feature on the Develop tab) that enables debugging and profiling with every Cordova plugin that is part of your project. In the past, debugging and profiling was limited to use of the core Cordova plugins and the Intel XDK plugins that may or may not represent what was specified by your project settings.

This new debug feature results in building a custom debug module (for use with the Debug and Profile tabs) that matches the plugins and build settings specified on the Project tab for your application. It attempts to mimic as closely as possible the final built app for quick and accurate debugging over a USB cable to a real device.

The first release of this new feature is limited to use with Android 4.0* and higher devices and works only with the Android Crosswalk* runtime (aka webview). This is enabled by building a custom debug module for your project when you use the Debug or Profile tab. Each time you initiate a debug or profile session (via the Debug or Profile tabs), the Intel XDK will check for any changes in your project settings that affect Cordova plugin and Crosswalk settings. If changes in these settings are detected a new debug module is automatically built and installed on your USB-connected Android device.

NOTE: If you find that you cannot build a custom debug module, a “generic” debug module can be installed onto your system. This generic debug module contains only the core Cordova and Intel XDK plugin APIs. To install this generic debug module:
  • push the “start” button (from the Debug tab) to start building a debug module
  • push the “cancel” button during the custom debug module build phase
  • push the “cancel” button when the “debug module required” warning message appears
  • select the “yes” button when presented with the option to install the “generic debug module” onto your device
This “generic” debug module is included with the Intel XDK on installation, so you do not need a network connection to install this module onto your device. You will, however, have to go through the sequence above to debug using the generic debug module (the install is only required once). The generic debug module has the same limitations as the Debug feature in prior versions of the Intel XDK:
  • generic debug is limited to the core Cordova and Intel XDK APIs
  • generic debug only runs on a Crosswalk 15 runtime (aka webview)
  • generic debug is limited to a fixed set of Cordova and Intel XDK plugin versions
We highly recommend that you build a custom debug module for your projects in order to optimize the accuracy of your preview and debug experience. A new debug module will only be built if you make a change to your project that results in a significant change, such as:
  • adding or removing a plugin
  • changing the version of a plugin
  • changing the version of Crosswalk
You always have the option of skipping an update to the custom debug module after making such a change and using the existing custom module that is already installed on your device, instead. Simply push the “cancel” button upon starting the debug session and select “skip” on the “debug module is out of date” dialog that appears.

To learn more about this new feature, review Debug Tab.

Crosswalk as a Plugin

Crosswalk as a plugin is now supported in the Android-Crosswalk build target. There is nothing special a developer has to do to use this "feature". When they choose CLI 5.1.1 (rather than CLI 4.1.2) and build for Crosswalk they will automatically get a Crosswalk 15 embedded build that was made using the new Cordova "pluggable" webview feature. Crosswalk apps built this way are built using the Cordova-Android 4.1.0 framework, rather than the older Cordova-Android 3.6.3. Version 4.1.0 is compatible with the latest Cordova plugins and is more secure than the older version of Cordova-Android.

Game Development Updates:

  • For game projects, you can now change the location of your project's game asset directory within the project directory. See Using the Game Asset Manager.
  • Updated the Game Engine versions supported
    Game Engine Name Supported Version(s) Default Version (if omitted during Project Import)
    Cocos2d-HTML5* 2.2.2 or 2.2.3 Dropped support in project template creation (obsolete engine version), but still supported in project import OR sample project creation.
    Cocos2d-JS* 3.1 through 3.7 3.7
    Cocos2d-JS Lite 3.2 through 3.7 3.7
    Phaser* 2.1.1 through 2.4.2 2.4.2
    Pixi* 1.6 through 3.0.7 3.0.7
    EaselJS* 0.7 through 0.8.1 0.8.1

Editor Updates:

  • Brackets* built-in editor is updated to version 1.4.
code { font-size: 90%; /* Code font is a little too big */ } code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
If you edit files in your plugins folder, the changes will not be seen in the device emulator until you restart the Intel XDK. After editing any of the files in the plugins folder, save them, exit the Intel XDK, then restart Intel XDK.
If you change your plugin selections, the emulator will not automatically restart, even if the auto-refresh option is active. Refresh/restart the Emulator.
Some 3rd-party Cordova plugins located in the new NPM Cordova plugin registry have a mismatch between the plugin‘s npm module name and the plugin’s ID.

The old Cordova plugin registry used reverse-domain “dot-notation” IDs (e.g., "org.apache.cordova.device”); whereas, the new Cordova plugin registry recommends using NPM package name “dash-notation” IDs (e.g., "cordova-plugin-device"). Unfortunately, this change has not been well communicated by the Cordova project and some plugin authors are using a dot-notation plugin ID with an NPM dash-notation package name. This can cause problems for the underlying Cordova “plugin add” operations used by the Intel XDK to import plugins into your Intel XDK project directory.

In the old Cordova plugin registry the plugin’s package name and ID match (X.Y.Z). In the new Cordova plugin registry, most plugins have changed their IDS to the dash-notation (X-Y-Z) to match their new NPM package names. Unfortunately, some plugins did not change the plugin ID but did change the package name when they were published to the new registry.

As the result of this inconsistency, some plugins can be fetched using an X-Y-Z style NPM module name, but the plugin ID displayed by the Intel XDK plugin manager may be displayed in the old X.Y.Z format. For adding, removing and including such plugins in a build, this situation is normally fine. However, if you try to change the version or variables associated with that plugin, using the plugin manager, this inconsistency will causes problems. Since we handle changes to any plugin that is stored in the Cordova registry by referencing its plugin by ID, we will always attempt to change such plugins via their ID (which is in X.Y.Z notation in these cases). Such changes result in a refetch of the plugin, which will be referenced by ID@version, which may not exist in either the old Cordova.io registry or new Cordova NPM registry.

This error results in a false “plugin not found” error message.
Remove the plugin manually, using the plugin manager (on the Project tab) and add back the new version of the desired plugin.
If your "source" directory is blank (meaning your index.html file is located at the root of your project, rather than within a folder inside your project directory, typically named "www"), when you build your app it will include the entire contents of the "plugins" directory located within your project directory. In order to eliminate this issue and insure future compatibility with updates to the Cordova subsystem of the Intel XDK, you should create a "source" directory (typically named "www") inside your project directory and move your index.html and other application source and asset files into that source directory. You must then also set the Intel XDK project properties to point to that new "www" directory located within your project directory. It is safest to do this with a copy of your project directory. For detailed instructions, see this forum post: https://software.intel.com/en-us/forums/intel-xdk/topic/593870#comment-1840292.
It is possible that during an update of the Intel XDK that not all files get properly removed before the update and the Intel XDK will crash with an "Error: ENOENT, no such file or directory" error. This can happen if you have a file/directory open in another process. In order to eliminate this issue and install the latest Intel XDK, first make sure there are no processes open that are using Intel XDK files. Next, remove all the files from your Intel XDK installation directory, then download the Intel XDK from intel.xdk.com and install.
LINUX ISSUE ONLY: the Linux client may rarely crash upon closing of the Intel XDK. Nothing is lost and the Intel XDK can be restarted without any harm. Simply discard the dialog box presented.
 
 

Keep Us Informed

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

 

Intel® XDK - Update - 2015 August 18 v2366

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

Issue Addressed:

  • This update fixes an issue with the Intel XDK Windows updater. Node-webkit was not getting properly updated to a newer version when an automatic update was performed. If you downloaded the installer package and installed it directly instead of using the automatic updater, the proper version was used.

    The OS X and Linux updaters worked properly.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin instead of the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values.
As part of the Intel XDK 1925 release the HTML5+Cordova blank template was replaced with a simpler template. In this release of the Intel XDK that simpler template will only be used when creating a new blank HTML5+Cordova project if the Intel XDK is offline (you have no network connection). When you are online (the Intel XDK has a network connection) the older more complex blank template will be retrieved for your blank project. This is a known issue that will be fixed in an Intel XDK release in the near future. The more complex version of the blank template will work just as well as the simpler version of the blank template for starting a new HTML5+Cordova project. The primary differences between the two are more comments in the index.html file, and the addition of an app.css and init-app.js file. These additional files are instructional only and are not required to use the more complex version of the blank template.

Both blank templates are available in the "gomobile" GitHub* directory at these locations: You can download the simple blank template project directly from its GitHub repo and create a new Intel XDK project from it by using the "Open an Intel XDK Project" button at the bottom-left of the Projects tab and selecting the blank-xdk-cordova-project-lite.xdk.xdk file inside the new project directory you created when you downloaded the template. You should rename that blank-xdk-cordova-project-lite.xdk file in your new project to match the desired name of your project before you open it with the Intel XDK because the name of that file determines the name of your new project in the Projects tab list of Intel XDK projects.
Incorrect Crosswalk* shared model runtime library version presented in the Build Settings section for Android-Crosswalk builds. The Android-Crosswalk Build Settings include a new option for selecting shared or embedded. The shared option presents you with "beta" as the version of the Crosswalk shared model runtime. In fact, the version of the shared model library that will be used by your Crosswalk app that is built using the shared model option will be the "stable" version of the library. At the time of the release only the "stable" Crosswalk shared library is supported, both "beta" and "shared" versions of the shared library will be supported in a future release.
 
 

Keep Us Informed

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

 

Intel® XDK - Release - 2015 August 03 v2323

Note: Our automatic updater will notify existing Intel XDK users when a new version (update) is available within the Intel XDK. Intel XDK updates will be released to all users within 24 hours. If you would like an update sooner, download it from intel.xdk.com.
 

New Features:

Installer Update:

  • A checkbox to automatically start the Intel XDK has been added to the last screen of the install process. By default this box is selected. If you do not wish to have the Intel XDK start at completion of the install, uncheck the box.

Intel® App Security API Plugin Update:

App Designer Updates

  • Added links to layout documents in the Help (?) Menu.

Deprecation of Build Targets

  • The Facebook* and Firefox* OS targets in the Project and Build tabs are now deprecated. Support for these and previously deprecated legacy build targets will be removed from the Intel XDK in the near future.

Issues Addressed:

  • Once again, a major focus of this release was to address issues raised by our users via the forums or support emails.
  • Corrected a couple of issues in the Emulator:
    • Fixed an issue where the back button did not fire the "backbutton" event.
    • Fixed a couple issues caused by pressing/clicking the mouse wheel that cause the emulator to misbehave
    • Fixed an issue where the Emulate tab strips #href tags, causing certain HTML operations to fail.
  • On the build success screen, fixed an issue where a secure link was always sent regardless of the selection of the checkbox for sending a secure link.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin instead of the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values.
As part of the Intel XDK 1925 release the HTML5+Cordova blank template was replaced with a simpler template. In this release of the Intel XDK that simpler template will only be used when creating a new blank HTML5+Cordova project if the Intel XDK is offline (you have no network connection). When you are online (the Intel XDK has a network connection) the older more complex blank template will be retrieved for your blank project. This is a known issue that will be fixed in an Intel XDK release in the near future. The more complex version of the blank template will work just as well as the simpler version of the blank template for starting a new HTML5+Cordova project. The primary differences between the two are more comments in the index.html file, and the addition of an app.css and init-app.js file. These additional files are instructional only and are not required to use the more complex version of the blank template.

Both blank templates are available in the "gomobile" GitHub* directory at these locations: You can download the simple blank template project directly from its GitHub repo and create a new Intel XDK project from it by using the "Open an Intel XDK Project" button at the bottom-left of the Projects tab and selecting the blank-xdk-cordova-project-lite.xdk.xdk file inside the new project directory you created when you downloaded the template. You should rename that blank-xdk-cordova-project-lite.xdk file in your new project to match the desired name of your project before you open it with the Intel XDK because the name of that file determines the name of your new project in the Projects tab list of Intel XDK projects.
Incorrect Crosswalk shared model runtime library version presented in the Build Settings section for Android-Crosswalk builds. The Android-Crosswalk Build Settings include a new option for selecting shared or embedded. The shared option presents you with "beta" as the version of the Crosswalk shared model runtime. In fact, the version of the shared model library that will be used by your Crosswalk app that is built using the shared model option will be the "stable" version of the library. At the time of the release only the "stable" Crosswalk shared library is supported, both "beta" and "shared" versions of the shared library will be supported in a future release.
 
 

Keep Us Informed

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

 

Intel® XDK - Update - 2015 July 17 v2248

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from xdk.intel.com.
 

Issue Addressed:

  • This update fixes an issue where the Intel XDK would pause for several minutes during startup when the network connection was slow or misconfigured.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin instead of the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values.
As part of the Intel XDK 1925 release the HTML5+Cordova blank template was replaced with a simpler template. In this release of the Intel XDK that simpler template will only be used when creating a new blank HTML5+Cordova project if the Intel XDK is offline (you have no network connection). When you are online (the Intel XDK has a network connection) the older more complex blank template will be retrieved for your blank project. This is a known issue that will be fixed in the next release of the Intel XDK. The more complex version of the blank template will work just as well as the simpler version of the blank template for starting a new HTML5+Cordova project. The primary differences between the two are more comments in the index.html file, and the addition of an app.css and init-app.js file. These additional files are instructional only and are not required to use the more complex version of the blank template.

Both blank templates are available in the "gomobile" GitHub account at these locations: You can download the simple blank template project directly from its GitHub repo and create a new Intel XDK project from it by using the "Open an Intel XDK Project" button at the bottom-left of the Projects tab and selecting the blank-xdk-cordova-project-lite.xdk.xdk file inside the new project directory you created when you downloaded the template. You should rename that blank-xdk-cordova-project-lite.xdk file in your new project to match the desired name of your project before you open it with the Intel XDK because the name of that file determines the name of your new project in the Projects tab list of Intel XDK projects.
Incorrect Crosswalk shared model runtime library version presented in the Build Settings section for Android-Crosswalk builds. The Android-Crosswalk Build Settings include a new option for selecting shared or embedded. The shared option presents you with "beta" as the version of the Crosswalk shared model runtime. In fact, the version of the shared model library that will be used by your Crosswalk app that is built using the shared model option will be the "stable" version of the library. At the time of the release only the "stable" Crosswalk shared library is supported, both "beta" and "shared" versions of the shared library will be supported in a future release.
The Emulate tab does not handle #href tags and location history correctly. See this forum post for examples and additional details.
The Emulate tab does not handle all variations of the @media query correctly. See this forum post for examples and additional details.
When the Cordova File plugin is included as a dependent plugin the build system adds a version of the File plugin that is "too old" or incompatible with the plugin that requires it. This is most commonly encountered when including either the Media or File Transfer plugin, but third-party plugins may also specify the File plugin as a dependency. Explicitly select the File plugin from the Cordova plugins list in the Plugins section of the Projects tab (doing so should specify version 1.3.2 of the File plugin) and then rebuild your app. See this forum post for additional details.
 
 

Keep Us Informed

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

 

Intel® XDK - Release - 2015 June 29 v2170

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from intel.xdk.com.
 

New Features:

Project Tab Crosswalk* Updates:

  • In the Projects tab: Build Settings, a new option was added to the Android-Crosswalk section that lets you select between shared mode and embedded mode for the Crosswalk* runtime. See Choosing Crosswalk* Build Options: Shared or Embedded for information on choosing the correct option for your apps.
  • Couple of caution notes with Crosswalk shared-mode:
    • First, like the new system WebView in Android* 5.x, updates to Crosswalk may be downloaded automatically by the Google Play* services if there are newer versions available. You should test your app regularly with new versions of Crosswalk as they are released if you chose the shared mode option. In some cases, you might instead choose to stay with the embedded option.
    • Second, because this feature relies on the end-user’s device having Google Play installed, shared mode is not appropriate if you are distributing your app through other Android app stores.

App Designer Updates:

  • Added support for Framework 7*.
    • Framework 7 is an Apple iOS*-themed framework that includes infinite scrolling, pull to refresh and a number of new touch based widgets.
    • Even though the framework is designed for iOS, you can build it into apps running on all other platforms as well.

Editor Updates:

  • JavaScript* code hinting is extended to support APIs documentation and display more information, such as parameters and return types.
  • Code hints definitions for App Security API v1.2.
  • Brackets* built-in editor is updated to version 1.3.
  • The Brackets extensions catalog is updated to support extension's new versions.

Game Asset Manager Updates:

  • Added support for importing audio and video assets. This support includes a code-snippet generator that allows you to copy-paste the code needed to add the audio or vidwo asset to your app project.
  • Many audio and video formats can now be imported into Game Asset Manager, which can generate code snippets specific to the game engine for that project. To use audio and video formats on devices, the devices need to provide the needed CODECs. The supported audio file formats for previewing an asset in Game Asset Manager are .oga/.ogg and .wav, and the supported preview video format is .ogv. See the Audio and Video Asset Support in the Game Asset Manager document for more details.
  • Improved managing the assets in the file tree within the editor.

App Security API Featured Plugin Update:

  • Updated to version 1.2.0
  • Introduces a new secure transport API that establishes a secure channel with backend to protect data integrity and confidentiality over the web without any crypto/key management effort from the developer.

Intel XDK API plugins are now available as Cordova plugins

  • The intel.xdk namespace plugins have been recast as Cordova plugins and can be found in the o1.org GitHub repo.
  • We recommend you use a "legacy" intel.xdk API only if there is no alternative in the form of a core Cordova or third-party plugin. For details, see the Intel XDK Namespace Cordova Plugin API Details doc page.

Issues Addressed:

  • Once again, a major focus of this release was to address issues raised by our users via the forums or support emails. We also continued to address issues that increase the stability of the Intel XDK.
  • Corrected an issue which was causing some users to see a slowdown in the Intel XDK when running on Apple Mac OS X* systems (particularly those using Yosemite).
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin instead of the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values.
As part of the Intel XDK 1925 release the HTML5+Cordova blank template was replaced with a simpler template. In this release of the Intel XDK that simpler template will only be used when creating a new blank HTML5+Cordova project if the Intel XDK is offline (you have no network connection). When you are online (the Intel XDK has a network connection) the older more complex blank template will be retrieved for your blank project. This is a known issue that will be fixed in the next release of the Intel XDK. The more complex version of the blank template will work just as well as the simpler version of the blank template for starting a new HTML5+Cordova project. The primary differences between the two are more comments in the index.html file, and the addition of an app.css and init-app.js file. These additional files are instructional only and are not required to use the more complex version of the blank template.

Both blank templates are available in the "gomobile" GitHub account at these locations: You can download the simple blank template project directly from its GitHub repo and create a new Intel XDK project from it by using the "Open an Intel XDK Project" button at the bottom-left of the Projects tab and selecting the blank-xdk-cordova-project-lite.xdk.xdk file inside the new project directory you created when you downloaded the template. You should rename that blank-xdk-cordova-project-lite.xdk file in your new project to match the desired name of your project before you open it with the Intel XDK because the name of that file determines the name of your new project in the Projects tab list of Intel XDK projects.
Incorrect Crosswalk shared model runtime library version presented in the Build Settings section for Android-Crosswalk builds. The Android-Crosswalk Build Settings include a new option for selecting shared or embedded. The shared option presents you with "beta" as the version of the Crosswalk shared model runtime. In fact, the version of the shared model library that will be used by your Crosswalk app that is built using the shared model option will be the "stable" version of the library. At the time of the release only the "stable" Crosswalk shared library is supported, both "beta" and "shared" versions of the shared library will be supported in a future release.
 
 

Keep Us Informed

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

 

Intel® XDK - Release - 2015 May 12 v1995

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from intel.xdk.com.
 

New Features:

Projects Tab Updates:

  • The option to send email has been removed for security reasons. If you want other users to test your app, send them the build completion email from the Build tab after a build completes.

Develop Tab Updates:

  • Live Layout Editing (aka live preview) in Google Chrome* or Mozillia Firefox* browsers is allowed for Standard HTML5 project types, but is not allowed for HTML5+Cordova project types. This change allows the Intel XDK to improve browser Live Layout Editing support for Standard HTML5 app projects.
  • Updated the built-in Brackets* editor to version 1.2.

Profile Tab Updates:

Build Tab Updates:

  • Added a Cancel button to the build dialog that appears after you choose a build target.

Issues Addressed:

  • Once again, a major focus of this release was to address issues raised by our users via the forums or support emails. We also continued to address issues that increase the stability of the Intel XDK.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
Some users are seeing a slowdown in the Intel XDK when running on Mac OS X systems. You can refer to forum posts: https://software.intel.com/en-us/forums/topic/557192 and https://software.intel.com/en-us/forums/topic/557574 for the types of issues they are experiencing. Currently no known workaround. Our development team is working to find a root cause.
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin instead of the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values.
Intel App Preview versions < 2.2.0 will not load Cocos2d* game projects. You can build your Cocos2d game projects with the Intel XDK and run on target devices for testing.
 
 

Keep Us Informed

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

    To search for issues that may have been previously reported, you can still visit our deprecated forums. These pages are for reference only and are not being monitored. All issues should be reported on the Intel® Developer Zone (IDZ) forum provided above.

 

Intel® XDK - Update - 2015 April 14 v1912

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from intel.xdk.com.
 

Issues Addressed:

  • Corrected the issue with intel.xdk plugins where if you selected the Emulator after selecting to include a plugin, the plugin was marked as "disabled" in the project.xdk file and thus was not included in the test or build uploads. In order for the plugins to work, you had to again deselect/select the plugin.
  • Corrected and issue where sometimes 3rd party plugins were not getting included in the built application.
  • Corrected an issue where if you selected the "Standard Cordova Plugins" check box (to select/deselect all Cordova plugins) then quickly selected/deselected individual plugins the list and build packages could get out of sync.
  • Corrected an issue where if a HTML5 project is upgraded to a HTML5 + Cordova project in project tab, the Emulator would report that the index.html file could not be found.
  • Corrected an issue on the Mac version which would present you with the following dialog when starting the Intel XDK on a Apple OS X system.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin versus the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values..
Crosswalk builds fail with the message “major version 51 is newer than 50, the highest major version supported by this compiler. [javac] It is recommended that the compiler be upgraded”.

The Crosswalk build servers are compiling builds with Java 6. The compiler will be upgraded to Java 7 shortly.
If you can use an older version of the plugin try that.

The Google Play Games Services plugin and Facebook Plugin require Java 7
Intel App Preview versions < 2.2.0 will not load Cocos2d game projects. You can build your Cocos2d game projects with the Intel XDK and run on target devices for testing.
 
 

Keep Us Informed

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

    To search for issues that may have been previously reported, you can still visit our deprecated forums, however report any new issues on the new IDZ forum provided above.

 

Intel® XDK - Release - 2015 March 30 v1878

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, download it from intel.xdk.com.
 

New Features:

Project Creation/Settings Updates:

  • With an HTML5+Cordova project type, you can build and deploy it as a packaged hybrid mobile app for Android*, Crosswalk* Android, Apple iOS* and Windows 8 devices.

    Advanced users can now also build the same project's code base as hosted web apps after adding feature detection code to avoid using Cordova* plugins in the web app deployment. To build as a web app, in the Web and Packaged App Targets section of the Projects tab, click a platform button to enable it in the Build tab.

Build System Update:

  • The Legacy Hybrid Mobile Apps Platforms build category has been deprecated and will become unsupported in a future Intel XDK release, so please migrate your apps to Cordova based builds. We will not remove any Legacy build platforms before the equivalent Cordova builds are all available

Intel® App Security API Plugin Update:

  • The Intel App Security API featured plugin was updated to version 1.1.0

Game Development Updates:

  • The same game engines and their versions are supported as in the previous release (see below):
    Game Engine Name Supported Version(s) Default Version (if omitted during Project Import)
    Cocos2d* 2.2.2 or 2.2.3 2.2.3
    Cocos2d JS 3.1 or 3.2 3.2
    Cocos2d JS Lite 3.2 3.2
    Phaser* 2.1.1 2.1.1
    Pixi* 1.6 1.6
    EaselJS* 0.7 0.7

App Designer Updates:

  • Now supports the Ionic* framework

Emulator Updates:

  • Added a “limitation” message to the emulator which explains that the emulator does not accurately model a real device's processor, memory, or HTM5 rendering features. You should always test your app on real devices before you publish.

Issues Addressed:

  • One focus of this release was to address issues raised by our users via the forums or support emails. We also continued to address issues that increase the stability of the Intel XDK.
  • The Intel XDK documentation now provides a left contents pane and other navigation features to help you find content. To search within the documentation, type a search string above the title link in the contents pane.
  • Please check out the new frequently asked questions (faq) to get quick answers to common Intel XDK support questions. Click a category link (such as General or Cordova) to expand a category. You can also access this page from within the Intel XDK by selecting "Intel XDK FAQs" under the help menu.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
When starting the Intel XDK on an Apple OS X system, you may be presented with the following:
Go to the Test Tab. Select the “Run Intel XDK local server to enable test over WiFi” checkbox to turn it off.
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin versus the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values..
Crosswalk builds fail with the message “major version 51 is newer than 50, the highest major version supported by this compiler. [javac] It is recommended that the compiler be upgraded”.

The Crosswalk build servers are compiling builds with Java 6. The compiler will be upgraded to Java 7 shortly.
If you can use an older version of the plugin try that.

The Google Play Games Services plugin and Facebook Plugin require Java 7
Intel App Preview versions < 2.2.0 will not load Cocos2d game projects. You can build your Cocos2d game projects with the Intel XDK and run on target devices for testing.
 
 

Keep Us Informed

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

    To search for issues that may have been previously reported, you can still visit our deprecated forums, however report any new issues on the new IDZ forum provided above.

 

Intel® XDK - Update - 2015 March 10 v1826

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK . The updates will be released to all users within 24 hours. If you would like the update sooner, you can download it from intel.xdk.com.
 

Issues Addressed:

  • For iOS, fixed an issue that caused a build failure when an app included the Apache Cordova featured Facebook plugin. Please note this plugin only works for Cordova version 3.5 and higher.
  • Fixed an issue in App Designer where if you created a framework document with two pages and a header or footer was dragged on to the second page it was incorrectly inserted into the first mainpage.
  • Fixed an Intel XDK crash that was caused if the Brackets node process could not be launched.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
When running the emulator debugger, you may notice messages like the following in the JavaScript console:
"Failed to load resource: net::ERR_CACHE_MISS"

It then displays the URL of a file, typically index.html.
The error message does not actually indicate a failure. It's a misleading warning. The file mentioned in the URL is, in fact, successfully fetched. This issue is reported as an upstream issue of Chromium.
When starting the Intel XDK on an Apple OS X system, you may be presented with the following:
Go to the Test Tab. Select the “Run Intel XDK local server to enable test over WiFi” checkbox to turn it off.
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin versus the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values..
Crosswalk builds fail with the message “major version 51 is newer than 50, the highest major version supported by this compiler. [javac] It is recommended that the compiler be upgraded”.

The Crosswalk build servers are compiling builds with Java 6. The compiler will be upgraded to Java 7 shortly.
If you can use an older version of the plugin try that.

The Google Play Games Services plugin and Facebook Plugin require Java 7
Intel App Preview versions < 2.2.0 will not load Cocos2d game projects. You can build your Cocos2d game projects with the Intel XDK and run on target devices for testing.
 
 

Keep Us Informed

  • NOTE: In March we are moving our user forums. We already have a user forum for Intel XDK support on the Intel® Developer Zone (IDZ) site (the parent site of xdk.intel.com) – it has been up for several months: https://software.intel.com/en-us/forums/intel-xdk. Please start using this new forum to provide feedback, report issues, and find solutions to issues you may be having!

    We want to completely move off of our current Intel XDK user forums so that we can better help you. The IDZ forums provide a much better spam filter (a huge problem on our current forums), better search, and just a better forum software platform that is also used by many other Intel software products and communities.

    To view issues that have been previously reported, please visit our deprecated forums, however report any new issues on the new IDZ forum. Both forums will be monitored until the transition is complete.

 

Intel® XDK - Release - 2015 February 23 v1816

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK . The updates will be released to all users within 24 hours. If you would like the update sooner, you can download it from intel.xdk.com.
 

New Features:

Updated Project Creation Workflow

  • Now includes Web Apps creation (Standard HTML5 project type) as well as hybrid mobile apps (HTML5 + Cordova project type). For information about project types, see the Projects tab topic.
  • Added new templates and samples/demos to get you started with Standard HTML5 web apps along with our previous hybrid mobile apps (HTML5 + Cordova project type).
  • Supported Game Engine Versions
  • NOTE: With this release of the Intel XDK, the app project version is being updated to 1.2 from 1.1. Projects with a version of 1.1 will ONLY work with Intel XDK version 1621 and older.

    You will be prompted to upgrade your project to the new version in each of the following conditions:
    • The first time you run this version of the Intel XDK, if you were working on a project when you last used the previous version of the Intel XDK. That is, the Intel XDK will ask you to upgrade your saved “current” project.
    • When you select a different project from your list of projects. This will happen one time for each project you select and upgrade. If you choose not to upgrade, you will be prompted each time you attempt to select the project with this new version of the Intel XDK.
    • When you open a different project using the OPEN AN INTEL XDK PROJECT button. This will happen one time for each project you open and upgrade. If you choose not to upgrade, you will be prompted each time you attempt to open the project with this new version of the Intel XDK.


    IMPORTANT NOTE: The upgrade process makes changes to the project-name.xdk and project-name.xdke files in your project’s root directory. It does not change any other files. The changes are necessary to support new functionality in this version of the Intel XDK. Once you have upgraded a project, it can no longer be opened in previous versions of the Intel XDK. The upgrade process does create a backup of your project files named project-name.xdk11_bak and project-name.xdke11_bak. If for any reason you need to revert to using a previous version of the Intel XDK, you can delete the project-name.xdk and project-name.xdke files and rename project-name.xdk11_bak to project-name.xdk and project-name.xdke11_bak to project-name.xdke.

    Projects with a version of 1.1 will ONLY work with Intel XDK version 1621 and older

Game Development Updates:

  • Added an Asset Importing feature in the Game Asset Manager. See Using the Game Asset Manager in the Intel XDK.
  • Added Web App support for game projects. Templates can now be accessed for both Standard HTML5 and HTML5 + Cordova project types.
  • Added Cocos2d-JS* Lite Game engine and updated Cocos2d JS versions supported
    Game Engine Name Supported Version(s) Default Version (if omitted during Project Import)
    Cocos2d 2.2.2 or 2.2.3 2.2.3
    Cocos2d JS 3.1 or 3.2 3.2
    Cocos2d JS Lite 3.2 3.2
    Phaser* 2.1.1 2.1.1
    Pixi* 1.6 1.6
    EaselJS* 0.7 0.7

Cordova Updates

  • Updated the default Apache Cordova* version to Cordova 4.1.2
  • Build servers have been upgraded to allow building your HTML5 + Cordova apps with Apache Cordova 4.1 or 4.1.2

Intel XDK Package for Sublime* Text Editor is now available

  • Allows you to launch Intel XDK commands from the Sublime Text* editor
  • Download the Intel XDK package.

Previewing, Debugging, and Profiling Updates:

  • In this release, you may pick the version of Crosswalk* that you would like to preview, debug, or profile your project with. Crosswalk 10 is used by default. If you would like to use a different version of Crosswalk, go to the ‘Projects’ tab, select ‘Build Settings’ in the right panel, and then select the ‘Android-Crosswalk’ tab. Use the pull-down list for ‘Crosswalk Version’ to pick the desired version. Note that the list of supported versions of Crosswalk is based on a live feed and may change between Intel XDK releases. Check back later if the version you would like to try doesn’t show up in the pull-down list.

Code Editor Updates:

  • Brackets* has been updated to version 1.1.
  • The Brackets extension catalog has been updated.

Build System Updates:

  • You can now select the supported version of Crosswalk you would like to build with via a dropdown menu in the build settings. Previously you had to specify either “Beta” or “Stable”.

Installer Updates:

  • Windows XP is no longer a supported platform. If you attempt to download the installer from a Windows XP system, a notification will appear and the download will not be completed.

Demos/Templates Updates:

  • Templates and Blank Templates have been added to support Web Apps (Standard HTML5 project type).

Issues Addressed:

  • For improved stability of the product we continue to address issues related to logs sent in by users via the error log dialog within the Intel XDK.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
When running the emulator debugger, you may notice messages like the following in the JavaScript console:
"Failed to load resource: net::ERR_CACHE_MISS"

It then displays the URL of a file, typically index.html.
The error message does not actually indicate a failure. It's a misleading warning. The file mentioned in the URL is, in fact, successfully fetched. This issue is reported as an upstream issue of Chromium.
When starting the Intel XDK on an Apple OS X system, you may be presented with the following:
Go to the Test Tab. Select the “Run Intel XDK local server to enable test over WiFi” checkbox to turn it off.
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin versus the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values..
Crosswalk builds fail with the message “major version 51 is newer than 50, the highest major version supported by this compiler. [javac] It is recommended that the compiler be upgraded”.

The Crosswalk build servers are compiling builds with Java 6. The compiler will be upgraded to Java 7 shortly.
If you can use an older version of the plugin try that.

The Google Play Games Services plugin and Facebook Plugin require Java 7
Intel App Preview versions < 2.2.0 will not load Cocos2d game projects. You can build your Cocos2d game projects with the Intel XDK and run on target devices for testing.
 
 

Keep Us Informed

  • NOTE: In March we are moving our user forums. We already have a user forum for Intel XDK support on the Intel® Developer Zone (IDZ) site (the parent site of xdk.intel.com) – it has been up for several months: https://software.intel.com/en-us/forums/intel-xdk. Please start using this new forum to provide feedback, report issues, and find solutions to issues you may be having!

    We want to completely move off of our current Intel XDK user forums so that we can better help you. The IDZ forums provide a much better spam filter (a huge problem on our current forums), better search, and just a better forum software platform that is also used by many other Intel software products and communities.

    To view issues that have been previously reported, please visit our deprecated forums, however report any new issues on the new IDZ forum. Both forums will be monitored until the transition is complete.

 

Intel® XDK - Release - 2014 December 18 v1621

NOTICE:
If you are updating from Intel XDK 1536 you will notice that for this release the updater has changed. You are now presented with a dialog box asking you if you want to download the update or wait until later. After the download completes, a second dialog will be displayed asking if you wish to install the update or wait until later. If you have a project open in the Intel XDK, the install will work properly. If you do not have an open project, the install may not start/work. To correct this, do the following:

1) Select the Wait until later option.
2) Open a project via the projects tab.
3) Select the Install icon (next to the orange "?" in the upper right corner of the Intel XDK window) to start the install.
The install should now work as expected.

This issue will be fixed in the next planned release of the Intel XDK.

If updating from a version prior to 1536, the updater works in the same fashion it previously had.

New Features:

The Intel XDK now supports game development.

  • The Getting Started with HTML5 Game Development Using the Intel XDK document can help get you on your way.
  • Supported Game Engine Versions
  • Manage Game Assets
    • Locate game assets in the Game Asset Manager file tree
    • View game asset(s) in thumbnail or expanded detail view
    • Render or inspect a selected game asset in expanded view
    • Generate a code snippet for a selected asset which can then be used in your JavaScript* development (only supported engines)
    • For additional information you can view this short video.
  • Brackets Editor Support
    • Get CodeHint automatically for current game engine in project (only supported engines)
    • Get CodeHint automatically for names of assets in project
    • Get Asset QuickView when hovering the mouse cursor over the name of an asset
  • Game Project Creation
    • Create a game project from different blank game templates, with different game engines included (Cocos2d*, Phaser*, Pixi* and EaselJS*, supported in different versions).
    • Supported Game Engine versions for thie Intel XDK release:
      Game Engine Name Supported Version(s) Default Version (if omitted during Project Import)
      Cocos2d 2.2.2 or 2.2.3 2.2.3
      Cocos2d JS 3.1 2.2.3
      Phaser 2.1.1 2.1.1
      Pixi 1.6 1.6
      EaselJS 0.7 0.7
    • Create a game project from different game samples
    • Import an existing game project to an Intel XDK project with game engine detection. Projects imported as engine projects will display Game Asset Managre, but only those projects using supported game engine versions can generate code snippets.
  • Get CodeHint automatically for Featured Cordova Plugin(s), after enabling the plugin(s) in Project Tab
  • Use the Emulate tab to emulate your game project on a device
  • Use the Develop and Test tabs to preview your game project or test on device
  • Use the Profile tab to profile your game project on device
  • Build your game app for submission to various stores using the Build tab

Updated Project Creation

  • Removed Blank project choice, and replaced it with blank templates specific to type of project being started.
    • Game
    • Apache Cordova*
    • App Designer (frameworks)
    • HTML5/CSS/JavaScript
  • A new dialog box is displayed when importing a project. The Intel XDK will attempt to determine your project’s source directory by looking for index.html. It will also detect the game engines which are currently supported. You may modify the settings which were detected if desired.

Apple iOS* Remote debugging is now available from the Debug tab

  • You will need to enable Web Inspector in Safari* on your testing device.
  • A debuggable/signed Intel App Preview can be built (using your Apple development certificate) which can then be installed on your test devices. The Intel XDK provides walkthroughs for setting this up once it detects your device.

Cordova Updates

  • Added client/server support for Apache Cordova 3.5 CLI version to emulator.

Memory Profiling support for Android* Crosswalk

  • Allows user to see how memory is being utilized while an app is running on device helping them fine tune their app’s overall performance.
  • Available on the Profile tab.

Emulator Updates:

  • Added simulation for Apple iPhone* 6 and iPhone 6 Plus

Code Editor Updates:

  • Brackets is updated to version 1.0, first official release of the Brackets editor.
  • Editor performance is significantly improved in this version of Intel XDK

Demos/Templates Updates:

  • Templates and Blank Templates are now available within the Intel XDK when you are not logged in or on-line. This allows a user to get started with development when they do not have a network connection available.

Issues Addressed:

  • For improved stability of the product we continue to address issues related to logs sent in by users via the error log dialog within the Intel XDK.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
It is recommended that as a user you may not want to select the “Featured & Custom Cordova Plugins” check box at the top of the Plugins And Permissions section on the Projects tab. Two different Facebook* plugins will be marked as selected (unless you manually uncheck one) which will cause a build error. It is recommended that you use the Featured Facebook Connect plugin versus the Intel XDK Facebook plugin which has been deprecated.

There are plugins that require variable values to be set and you will not be prompted to provide those values. If you do select all the plugins in this fashion, click on the “wrench” icon next to the plugin name to enter the required values..
Crosswalk builds fail with the message “major version 51 is newer than 50, the highest major version supported by this compiler. [javac] It is recommended that the compiler be upgraded”.

The Crosswalk build servers are compiling builds with Java 6. The compiler will be upgraded to Java 7 shortly.
If you can use an older version of the plugin try that.

The Google Play Games Services plugin and Facebook Plugin require Java 7
AppPreview versions < 2.2.0 will not load Cocos2d game projects. You can build your Cocos2d game projects with the Intel XDK and run on target devices for testing.
 
 

Keep Us Informed

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

 

Intel® XDK - Release - 2014 November 04 v1536

New Features:

Apache Cordova* CLI and Plugin Version updates:

  • The default Cordova CLI version used for builds has been updated to 3.5 for all new projects. Existing projects created with earlier Intel XDK versions will still have 3.3 set as the CLI version. If you change your project to use CLI 3.5, you should also consider updating your plugin versions – see the next item.
  • The default versions of the included Standard Cordova Plugins have been updated to the versions tested with Cordova 3.5. One exception is the StatusBar plugin (see below) which has version 1.0.7 versus 1.0.3 which is not available in the official repo. Please see http://cordova.apache.org/announcements/2014/05/23/cordova-350.html for reference.
    • If you have an existing project that had included plugins, the versions you used will not be updated unless you specifically change them. Plugins listed that have not been selected will use this new version when selected. You may upgrade a previously created project to use the versions tested with Cordova 3.5 in the Projects tab, Plugins and Permissions, by selecting the “Reset versions” control.
    • These plugin versions have also been added in the Build system.
  • The Cordova File Transfer and StatusBar plugins have been added to the list of included plugins.

Intel App Preview Updates:

  • We recently released an App Preview Legacy app to the various app stores named “App Preview Legacy”. This version can be used for on-device testing for apps built with the Legacy Hybrid Mobile App Platforms (Build tab) option.
  • For apps built using the Cordova 3.X Hybrid Mobile App Platforms and Build as a Web App (in the Build tab), you should install and use “App Preview” app for on-device testing.

App Designer Updates:

  • App Starter has been deprecated and has now been subsumed by App Designer. This change provides the best possible UI design tool available that allows you to develop the UI for an app, and then leave the code in a readable, editable state so that it can be augmented from there. App Starter does this, but does not have enough responsive design capabilities and widgets.
  • WebRTC widgets have been added.

Code Editor Updates:

  • Updated to Brackets Sprint 44. This version allows you to view two documents side-by-side in either a horizontal or vertical split-screen view. You can also choose a theme, such as a dark background. These options can be found under the View menu in the Brackets code editor.

Web Services Updates:

  • A “Debug It” button has been added to each service to aid in the debugging of services API..

New Featured Plugin:

  • Added a Google Play* Games Services plugin to the Featured Cordova Plugins list. This plugin enables game services that can help HTML5 game developers get their apps discovered and monetized as Google Android* applications.

Build System Updates:

  • Complete build logs are now available on the final build screen for review for apps built using Cordova 3.X Hybrid Mobile App Platforms. This update will help you determine the cause of build failures. It will also help our support team better analyze a particular issue when reported by a user.
  • Now supports Apple iOS* 8 and Apple iPhone* 6 requirements.
  • NOTICE: We made some changes to the LEAN and LEAN WITH APP GAME INTERFACE build options contained on the Details tab of the iOS and Android builds under the Legacy Hybrid Mobile App Platforms build selections. These legacy options were provided as a means to reduce the overall footprint of an application that did not require certain functionality. These options are no longer necessary as Cordova build targets provide better reduced footprint options.
    • We have removed support for the LEAN WITH APP GAME INTERFACE build option that was previously available on the Details tab of the legacy iOS and Android builds interface. If you plan to use App Game Interface functionality, select the GOLD build option.
    • We plan to remove support for the LEAN build option in approximately 30 days.

Issues Addressed:

  • To improve the stability of the product we addressed a number of issues related to logs sent in by users via the error log dialog within the Intel XDK.
  • Corrected an issue where the editor would crash if a file was read-only.
  • Fixed an issue where the Refresh button in Run My App -> Run in Emulator would not bring the emulator window to the foreground, if you had navigated away from the emulator (i.e. selected the Develop Tab).
  • Fixed an issue in App Designer where an undesired footer would be added in some instances.
  • Corrected the issue when starting Google Chrome* or Mozilla Firefox* Live Layout session after closing a previous Live Layout session from the Intel XDK, it would display a message that the browser did not shut down properly.
  • Fixed the issue that would not allow opening more than 1 instance of Firefox* when using Live Layout.
  • Corrected an issue where a dialog box shown in the service explorer did not get dismissed if the current project was changed without responding to the dialog box.
code { font-size: 90%; /* Code font is a little too big */ }

Known Issues:

Issue Workaround
When using the Updater functionality to get the new version of the Intel XDK, if the download takes more than two minutes, you may see a message stating "Cannot download an update since one is not available". Despite the message, the download is still continuing in the background and will complete unless your Internet connection is lost. Allow ample time for the download to complete, exit the Intel XDK and then restart. If the download completed successfully, you should now see the Install Update icon in the upper right hand corner of the Intel XDK toolbar next to the orange (?) icon.

If the download has not completed successfully and the icon does not appear, you can try the download again or you can download the newest version of the installer from: http://xdk.intel.com.
If building your app to work on the iPhone 6+, note that it requires an additional icon and splash screens that are not currently in the UI of the Projects tab. If they are not included, others will be used. . To specify custom iPhone 6+ icon and splash screens, add the following to the intelxdk.config.additions.xml file, where the scr is the location of your image.

<icon platform="ios" src="images/ios/180x180.png" width="180" height="180" />

<splash height="2208" platform="ios" src="images/ios/1242x2208.png" width="1242" />

<splash height="1242" platform="ios" src="images/ios/2208x1242.png" width="2208" />
 
 
 

Intel® XDK - Update - 2014 October 16 v1494

Issues Addressed:

  • Addressed some issues related to logs sent in by users via the error log dialog.
  • Fixed an issue where the Standard Apache Cordova* Plugin version would not be reset to the original default value when the user selected "Reset versions" after modifying the plugin(s) version.
  • Updated the project templates used when creating projects to make use of Apache Cordova 3.5.1 to fix a security vulnerability identified in Apache Cordova for Android. Other Apache Cordova platforms such as Apple iOS* and Microsoft Windows* 8 are unaffected by this security risk. See this Apache Cordova Android 3.5.1 announcement for more details.

Known Issues:

Issue Workaround
On Apple OS X* systems, attempting to start a second Live Layout session on Firefox* will display the following error message: A copy of Firefox is already open. Only one copy of Firefox can be open at a time. None
Starting Google Chrome or Firefox Live Layout session after closing a previous Live Layout session from the Intel XDK, will display a message that the browser did not shut down properly. Simply dismiss the warning. The functionality of Live Layout should not be affected.
When working with Services on the Develop tab, a dialog box shown in the service explorer does not get dismissed if the current project is changed without responding to the dialog box. Click the ‘Dismiss’ or ‘Thanks’ button and the dialog will be dismissed and should not affect the services for the new project.
When using the Updater functionality to get the new version of the Intel XDK, if the download takes more than two minutes, you may see a message stating "Cannot download an update since one is not available". Despite the message, the download is still continuing in the background and will complete unless your Internet connection is lost. Allow ample time for the download to complete, exit the Intel XDK and then restart. If the download completed successfully, you should now see the Install Update icon in the upper right hand corner of the Intel XDK toolbar next to the orange (?) icon.

If the download has not completed successfully and the icon does not appear, you can try the download again or you can download the newest version of the installer from: http://xdk.intel.com.
If you create an app based on the new blank project AND the following is true:
  • you use the sample init code from the init-app.js file in the blank project for detecting touch or click events
  • you run your app using “Live Layout Editing” in a browseron a machine that does not support touch
your app may not detect any click events, because it will be looking for non-existent touch events.
To fix this, in the blank project template code, change this if statement:
if( navigator.msPointerEnabled )
to this:
if( navigator.msPointerEnabled || !('ontouchend' in window))
in the init-app.js file.
 
 
 

Intel XDK - Release - 2014 September 08 v1332

Note: Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. The updates will be released to all users within 24 hours. If you would like the update sooner, just download from https://xdk-software.intel.com and the installer will update it as well.

New Features:

Live Development Updates:

  • Live Layout (formerly known as “Live Preview") is accessible on the Develop tab and lets you preview your app in:
    • Desktop browsers (Google* Chrome* and Mozilla* Firefox*).
    • On Android* and Apple iOS* devices running the new App Preview 2.0 while connected to your development system over a local WiFi connection.
  • Run My App (formerly known as “Active Sync”) lets you run your app either in an undocked emulator window or on your Android* device via a USB connection.

Improvements to the Apache Cordova* Plugins UI:

  • Added a “Featured Plugins” list for non-core plugins that are integrated into the Intel XDK and tested with the Intel XDK. Two featured plugins are included in that list with this release:
    • The Intel App Security APIs (described below).
    • A Dolby Audio* plugin from Dolby Corporation that provides for some amazing audio quality for certain hardware enabled mobile devices (the plugin gracefully falls back to normal operation if the special Dolby hardware is not present).

The Intel App Security API plugin is included as a Featured Plugin. This plugin provides new APIs to aid in security for on-device app data and storage.

  • It offers security services for HTML5 developers via a JavaScript API and middleware.
  • It delivers on-device secure data (for data-in-use) and secure storage (for data-at-rest). The middleware protects the confidentiality and integrity of storage elements and data access
  • Secure data and secure storage are the foundation for future enhancements and extension to the Intel App Securiety API for applications such as those in domains like transportation, identity, input and output.

Intel® App Preview version 2.0 Released:

  • Intel App Preview (version 2.0) is now based on Apache* Cordova 3.5. The Intel XDK APIs (intel.xdk.*) are now supported via Cordova plugins. See this detailed list of Intel XDK APIs supported in this version of App Preview. See the Project tab plugins and permissions section for documentation regarding the core Apache Cordova APIs that are suported.
  • Previous versions of Intel App Preview were based on the Intel XDK Legacy container, a hybrid application container developed originally by AppMobi. Version 2.0 of Intel App Preview is based on the Cordova 3.5 hybrid app framework in order to provide a better preview experience for Intel XDK projects based on the new Cordova build system.
  • The Intel XDK legacy build container has been deprecated and will be retired in 2015. In order to support existing projects that use the Intel XDK legacy container, a new application called Intel® App Preview Legacy will be published to the respective app stores in the near future.
  • AGI (Accelerated Graphics Interface) is not supported by Intel App Preview 2.0.
  • AppMobi services are not supported in Intel App Preview 2.0. This includes the AppMobi push notification and live update APIs.
  • Intel App Preview now uses the Intel Clear Sans font: https://01.org/clear-sans for a cleaner look.
  • New Features in Intel App Preview 2.0 include:
    • 3-finger tap to stop previewing and return to the Intel App Preview main menu.
    • 5-finger tap for Intel App Preview version information and plugin details.
    • Configuration-based plugin loading:

      The Cordova plugins available to your app running in Intel App Preview are based on your Intel XDK project configuration. This gives you a better idea of whether your project is correctly configured, for a more valid "preview" experience. See Projects tab topic for more information about configuring your Intel XDK project.

    • Live Layout Editing allows you to see the effect of edits on your app running in Intel App Preview as you make them in Intel XDK Develop tab (while editing your source code using the builtin Brackets editor).

New Features for Android:

  • Remote debugging on Android 4.4+ devices using Google Chrome and remote Chrome DevTools*. For set-up info and requirements refer to this Android developer article.
  • App Preview Crosswalk, which is used when working with the Debug and Profile tabs and when using the new Live Development feature on the Develop tab has been updated.
    • It is now based on Crosswalk* version 8.
    • Contains the latest versions of the Intel XDK plugins and includes the App Security plugin mentioned above.

Web Services Updates:

  • The explore and integrate tool for web service APIs is now located as a mini service explorer in the Develop tab (formerly this was located in a dedicated Services tab). Third party services can be easily integrated into an app by using the mini explorer during the development process. Data bindings created in the explorer can be used in your own code (choose the editor option) or directly from within App Designer widgets.
  • A new search feature helps you quickly find the most appropriate services. Services are now tagged with keywords to guide you in finding the right service.
  • OAuth 2.0 authentication is supported.
  • Several new web services were added, such as jambase, tms and soundcloud.

App Designer Updates:

  • A new DOM Tree control has been added to browse the App Designer DOM tree.
  • The DOM tree entries are paired with a new HTML preview pane so users can view or edit the HTML of an individual entry.
  • Service method instances now appear directly within App Designer. They can be dragged to widgets to set up data bindings.
  • Text Input widgets can be dragged to service method instances to drive a service request with user input.
  • Search has been added to the Controls pane to help you find individual widgets

Other Updates:

  • Added new demo applications which help users get started with the implementation of Ads and Monetization in their apps.
  • The build system now supports both Cordova 3.3 and 3.5 versions. You can set the Cordova CLI Version field, under Build Settings on the Projects tab, to specify which version you would like to build your app with.
  • Updated Intel XDK launch icons and splash screens.
  • Portrait and landscape splash screens are now properly supported on Android platforms.

Issues Addressed:

  • Corrected the issue when using the undocked emulator, if you switched between projects or went back and forth between the docked and undocked emulator without letting the emulator fully load first, you may have seen a crash.
  • Fixed an issue where apps built using Crosswalk builds would display an “Unfortunately, <project-name> has stopped.” Message upon using the Android “Back” button.
  • Fixed an issue where the build system was swapping splash screen height and width in the <splash> tag in Cordova for iOS builds.
  • Corrected an issue on the Debug tab where it would not start app on device and a non-ending spinning "prepare" screen was shown.
  • On Apple OS X* systems, fixed a bug where the Intel XDK showed a different version than the About Intel XDK dialog box.
  • For improved stability we addressed a number of issues related to logs sent in by users via the error log dialog within the Intel.

Known Issues:

Issue Workaround
On Apple OS X* systems, attempting to start a second Live Layout session on Firefox* will display the following error message: A copy of Firefox is already open. Only one copy of Firefox can be open at a time. None
Starting Google Chrome or Firefox Live Layout session after closing a previous Live Layout session from the Intel XDK, will display a message that the browser did not shut down properly. Simply dismiss the warning. The functionality of Live Layout should not be affected.
When working with Services on the Develop tab, a dialog box shown in the service explorer does not get dismissed if the current project is changed without responding to the dialog box. Click the ‘Dismiss’ or ‘Thanks’ button and the dialog will be dismissed and should not affect the services for the new project.
When using the Updater functionality to get the new version of the Intel XDK, if the download takes more than two minutes, you may see a message stating "Cannot download an update since one is not available". Despite the message, the download is still continuing in the background and will complete unless your Internet connection is lost. Allow ample time for the download to complete, exit the Intel XDK and then restart. If the download completed successfully, you should now see the Install Update icon in the upper right hand corner of the Intel XDK toolbar next to the orange (?) icon.

If the download has not completed successfully and the icon does not appear, you can try the download again or you can download the newest version of the installer from: http://xdk.intel.com.
If you create an app based on the new blank project AND the following is true:
  • you use the sample init code from the init-app.js file in the blank project for detecting touch or click events
  • you run your app using “Live Layout Editing” in a browseron a machine that does not support touch
your app may not detect any click events, because it will be looking for non-existent touch events.
To fix this, in the blank project template code, change this if statement:
if( navigator.msPointerEnabled )
to this:
if( navigator.msPointerEnabled || !('ontouchend' in window))
in the init-app.js file.
 
 
 

Intel XDK - Release - 2014 July 29 v1199

New Features:

Updates:

The Crosswalk build system was changed to eliminate the "GPU blacklist" problem which should resolve those problems where a Crosswalk built app would run at very low frame rates, or not at all, on some Android devices. If you continue to have problems of this sort with Crosswalk builds please report them on the Intel XDK forum.

  • With this release of the Intel XDK, the HTML5 app project version is being updated to 1.1 from 1.0. Projects with a version of 1.0 will ONLY work with Intel XDK version 0876 and older.

    You will be prompted to upgrade your project to the new version in each of the following conditions:
    • The first time you run this version of the Intel XDK, if you were working on a project when you last used the previous version of the Intel XDK. That is, the Intel XDK will ask you to upgrade your saved “current” project.
    • When you request to open a different project from your list of projects. This will happen one time for each project you open and upgrade. If you choose not to upgrade, you will be prompted each time you attempt to open the project with this new version of the Intel XDK.

      IMPORTANT NOTE: The upgrade process makes changes to the project-name.xdk and project-name.xdke files in your project’s root directory. It does not change any other files. The changes are necessary to support new functionality in this version of the Intel XDK. Once you have upgraded a project, it can no longer be opened in previous versions of the Intel XDK. The upgrade process does create a backup of your project file named project-name.xdk10.bak. If for any reason you need to revert to using a previous version of the Intel XDK, you can delete the project-name.xdk and project-name.xdke files and rename project-name.xdk10.bak to project-name.xdk.

      Projects with a version of 1.0 will ONLY work with Intel XDK version 0876 and older.
  • We now have full support for Cordova APIs and Cordova (aka PhoneGap) plugins on iOS*, Android* and Windows* 8. The main difference between Cordova 2.x and Cordova 3.x is that the monolithic Cordova API has been replaced by a collection of independently selectable “plugins”. To use/test 3rd party plugins you must build your app and install it on device (see details under Known Issues below).

    A new UI on the Projects Tab allows you to select from a list of Cordova plugins that include the core Cordova API and standard Intel XDK APIs, which you can include in the app package you build. There are many consequences to this change that are discussed in detail in these articles:
    Adding Plugins to Your Intel® XDK Cordova App
    Add special build options to your Intel XDK Cordova app
  • Projects Tab Updates:
    • When you have a project selected on the Projects tab, there is a new section with the heading of “CORDOVA 3.x HYBRID MOBILE APP SETTINGS” on the project’s information screen where you can enter/edit build settings for an application that will use the Cordova 3.x architecture. These settings are only used when building with Cordova 3.x; they DO NOT affect building a “Legacy Hybrid Mobile App” or a “Web App”.

      In the previous release of the Intel XDK, you were required to create an intelxdk.config.xml file to specify the settings when building with Cordova 3.x. This is no longer supported and you must enter your settings from the Projects tab. The settings are divided into 3 main sections:
      • PLUGINS AND PERMISSIONS - here you can select from a list of Cordova plugins that include the core Cordova API and standard Intel XDK APIs, add custom (Third Party) plugins, and add any additional permissions that your application requires.

        NOTE: When adding third party plugins the UI only indicates to the build system what to upload, and that upload is only done during build time. If you want to include a custom plugin in the project directory while editing, you will need to manually download it and place in your project.
        Reference the following related article:
        Adding Plugins to Your Intel XDK Cordova App

      • BUILD SETTINGS – here you enter other settings for your application such as its name and ID.
      • LAUNCH ICONS AND SPLASH SCREENS - here you enter splash screens and icons for your application




































      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      •  
      When you select one of the “CORDOVA 3.x HYBRID MOBILE APP PLATFORMS” build tiles and upload your project sources, the Intel XDK will generate intelxdk.config.platform.xml files in your project root directory. These files contain the settings that you have made in the Projects tab and are used by the build server. You CANNOT edit these files as they are re-generated every time that the project’s sources are uploaded to the build server. A mechanism is provided to modify the automatically generated config file by creating an intelxdk.additions.xml file. For Reference:
      Adding Build Options to Your Intel® XDK Cordova App Using intelxdk.config.additions.xml

      Please refer to the following web page for additional information on working with the Projects tab:
      Projects tab
  • Added sorting options to the Your Intel XDK Projects list while on the projects tab.
    • Name – Sorts your projects alphabetically by name
    • Opened – Sorts your projects by last opened/touched date
      • Note that this sort only works with projects that have been upgraded to the new project version of 1.1 (See above Note)
  • App Preview Crosswalk, which is used when working with the debug, profile, and auto sync features of the Intel XDK, has been updated to use Crosswalk version 6.
  • The Emulator can now run in a separate window as well as in the Emulate tab. To undock the emulator into a separate window, click the up arrow icon in the corner of the Emulate tab. To run docked in the Emulate tab, close the undocked window (if open) either by clicking on the close control or by clicking the down arrow icon on the Emulate tab. You can then click the Emulate tab to run docked.
  • A mechanism to download and install App Preview from the cloud on to a user device if the user so chooses, has been implemented. The guides for the TEST, DEBUG, and PROFILE tabs have been updated to include a link to App Preview on the cloud server or you can email the link.
  • Editor Updates:
    • Brackets has been updated to Release 40
    • XLint extension now includes HTML and Media support – potential incompatibility issues are reported on HTML files and HTML media tags.
  • Services Updates:
    • Many new services have been added (Flickr, Weather Underground, and many more)
    • OAuth2 support has been added (the new FourSquare and Instagram services use it)
  • App Designer Updates:
    • New UI with draggable panels
    • Service Methods (from Services pane) now appear in App Designer and can be drag/dropped onto any control
    • In the Projects pane you can change the UI Framework for App Designer projects
    • A Google Maps data feed has been added
  • Firefox OS builds have been added to the Build a Web App section of the Build Tab

Known issues:

Issue Workaround
When using the undocked emulator, if you switch between projects or go back and forth between the docked and undocked emulator without letting the emulator fully load first, you may see a crash. Allow the Emulator to fully load before attempting to switch between docked and undocked mode. The Emulator should then work as expected in either mode. The dock/undock icon in the Emulate tab is disabled during Emulator startup, but this does not provide complete protection against the crash.
The Intel XDK Emulate tab, App Preview, Test tab and Debug tab do not support third-party plugins for test and emulation. Attempting to call a third-party plugin API within the Emulator or App Preview will result in JavaScript errors that will likely result in halting your application. Workaround #1: The build system does allow the use of third-party plugins. Build your app using the Cordova 3.x Hybrid Mobile App Platform from the Build tab to test your app with plugins directly on device (e.g., build and install you test app on device, you can include the weinre script from the Test tab to perform simple console.log debugging, be sure to remove the weinre script tag before you build the production version of your application).

Workaround #2: Utilize feature detection before calling the third-party plugin APIs to first determine if the third-party APIs are present (they will not be present when running in the Emulate tab or inside of App Preview). If you detect that the API is not present you will have to simply skip that part of your application or substitute an alert or console.log message or perform some other action that is appropriate to your application and debug/test scenario. This will allow you to quickly debug those parts of your application that do not depend on third-party plugins using the Emulate tab or App Preview.
After you create a new project then work with that project using other tabs, when you return to the Start a New Project screen there will be no default selection for project type selected and text on right side of screen is not correctly shown. Reselect a project type from the left side menu and the right side screen will be properly refreshed to the correct project type.
 
 
 

Intel XDK - Release - 2014 May 05 v876

New Features:

  • The “Work with a Demo” panel has been updated to provide a more consistent look with the “Start with a Template” panel, including a banner on apps that are App Designer ready.
  • Editor - Updated to Brackets Sprint 38.
  • App Preview Crosswalk, which is used when working with the debug, profile, and auto sync features of the Intel XDK, is now being distributed to the device from the cloud versus the Intel XDK directly. You will be prompted to install the correct version (0.20) if already using an older version.
  • App Designer - now provides support for App Framework side-menus.
  • App Starter - Custom widgets support has been added.
  • Emulator – A “STOP” button was added which stops the emulation. To restart emulation for the app, you simply need to select the Refresh icon.

Issues Addressed:

  • Corrected an issue when exiting the Intel XDK either by using CMD+Q or by selecting “Quit Intel XDK” from the Intel XDK Menu on Mac OS X, you would momentarily see an error dialog.
  • Corrected an issue with the Intel XDK updater that caused the user to see the Safe/Normal restart option upon restart of Intel XDK after an install via the updater.
  • Corrected the following issue in the emulator:
    • The container supplies a file named "xhr.js" that is used to enable XMLHttpRequests to work without triggering cross-domain violations. Since this file does not exist in the project directory, the emulator must take steps to avoid a 404 (not found) error during emulation.

      Unfortunately, the solution the emulator applied effectively ignored files named "xhr.js" that did exist in the project directory. This corrupts the behavior of apps that rely on that source being included during emulation.

      Now the emulator correctly supplies its own content for xhr.js ONLY if that file does not exist in the project.
  • Corrected an issue which prevented creating two apps using the same demo back to back.
  • Addressed a number of issues related to logs sent in by users via the error log dialog.

Known issues:

Issue Workaround
Cannot drag/drop "textarea" element to a page in AppStarter project while working in the Design mode of the Develop tab. You will have to create the textarea manually in your HTML code.

<div class='textarea_element form_element' style='width:100%;overflow:hidden'>
    <label>Textarea</label>
    <textarea></textarea>
</div>
While running the updater from the within the Intel XDK, you may receive the following error message, "Cannot download an update since one is not availble". This message indicates that the download of the update did not successfully complete. After receiving this message, you can exit the Intel XDK, reopen the Intel XDK and try the download again. Or, you can download the installer for the new version at http://xdk-software.intel.com and install from that.
If updating to this version from our April Release Version (v0714) - While performing the install of the update from within the Intel XDK, when the Intel XDK restarts you will see a Safe/Normal restart dialog. Select the Normal Restart option and the Intel XDK should run normally. This issue has been corrected in the updater for any updates after 0714.
 
 
 

Intel XDK - Update - 2014 Apr 21 v769

Issues Addressed:

  • Addressed a number of issues related to logs sent in by users via the error log dialog.
  • Corrected a bad tooltip on the Emulator Back button.
  • Made an update to the Import Project screen to properly reflect the directory the project is stored in. Previously the information you entered in the “Name your project” field appeared to be adding a directory to the “Import From” path on the screen while it actually did not.
  • Corrected an issue with intel.xdk.player.playSound() method where it did not play on Cordova apps.
  • Cleaned up the following App Preview Crosswalk compatibility issues:
    • “Missing file” error due to xhr.js
    • reference to AppMobi in “useViewport” in display plugin
    • AppMobi reference in geolocation plugin
  • Fixed the following issues listed in the Known Issues section of the 2014 Apr 09 v714 release notes.
    • If your project contains any files that are all uppercase in name (i.e. LICENSE) and zero length in size, the bundle created during sync to the test server (Test tab), or sync to the build server (Build tab) may become corrupt when downloaded to your device for test or submitted for build.
    • If your app uses HTML files that don't include a <head> or <html> or <!DOCTYPE> tag the emulator thinks it is not a valid HTML file and won't load it.
    • When trying to test a project using the Test tab and the mobile wifi option (testing over your local wifi with App Preview) you may encounter a blank screen on your device after the app loads into App Preview.

Known issues:

Issue Workaround
While running the updater from the within the Intel XDK, you may receive the following error message, "Cannot download an update since one is not availble". This message indicates that the download of the update did not successfully complete. After receiving this message, you can exit the Intel XDK, reopen the Intel XDK and try the download again. Or, you can download the installer for the new version at http://xdk-software.intel.com and install from that.
While performing the install of the update from within the Intel XDK, when the Intel XDK restarts you will see a Safe/Normal restart dialog. Select the Normal Restart option and the Intel XDK should run normally. This issue is being worked and will be corrected in the next version of the updater.
While testing any of the App Designer created App Framework Templates on an Android 4.4 or higher tablet through the TEST or BUILD tab, you may notice that the entire application may be 80% of the device's width. After noticing this issue, you can edit the afui-header.less file to resolve this issue. In the projectname/css/index/afui-header.less file, change the css rule's selector from #afui header to #afui .header header.
 
 
 

Intel XDK - Release - 2014 Apr 09 v714

New Features:

  • Added new “Developer Preview” Cordova* for iOS* and Windows 8* build targets to build system – Android* was released in our February release, Windows Phone 8* is coming soon.
  • Added “Live Preview” support using a desktop Chrome browser window.
    • When using the Brackets editor in the Intel XDK, you can preview an HTML file from your project in a separate Chrome browser window. Modify the HTML and CSS in the editor to see the page modified "live" in this Chrome browser window.
  • Added “Preview on Device” support for Android devices.
    • When using the Brackets editor in the Intel XDK, you can preview an HTML file from your project on your Android device. Modify the static HTML and CSS in the editor, then save and see the page modified on the device.
  • Added a "Start with a Template" option to the Start a New Project pane.
    • Using this option you can start a new project based on an "empty" UI project template.
    • Templates differ from "Demo" projects in that they are not fully functional. They are shell apps, each providing a common UI experience (list, flip, grid view, login page, side menu, etc.).
    • The templates are based on App Framework and are fully compatible with App Designer.
  • Added capability for seamlessly integrating Web Services into your app.
    • The services tab now allows for management, exploration, and embedding web service APIs.
    • Embedded web service APIs are available for use from within all aspects of the Intel XDK: Brackets, App Designer, App Starter, the emulator and App Preview.
    • The list of built-in services include appMobi and several Mashery-managed services (USA Today Census, Klout, and Rotten Tomatoes)
  • Added a “Settings Dialog Box” – this is a Preview Implementation.
    • At this time only a few settings are available on this dialog. Access the settings dialog by clicking the gear symbol near the user login symbol in the top right corner of the Intel XDK window. Two tabs are present in the settings dialog: “general” and “services.”
    • From the “general” settings dialog tab you can suppress the quick tour message after creating a new project and you can specify a list of file and directory names to be ignored by the Intel XDK. Files and directories that match the ignored file list will not be submitted to the cloud when you use the Build or Test tabs. Note that the wildcard (*) character is supported as part of this list. We recommend that you maintain the initial default list, as this covers many of the typical hidden files and directories that could be found in your project folder. (Note that you cannot change this to be ignored list on a per project basis. If that level of control is important to you, we would appreciate receiving your feedback. Please provide feedback via the Intel XDK forum.)
    • On the “services” settings dialog tab you can set or clear whether the services JavaScript helper libraries automatically created by the Services tab should be minified and compressed or left in an easy to read format. Normally this code is minimized, but for debugging and inspection it is useful to turn this feature off. Y1u can also specify the directories used by the Services tab to store services-specific files. These directories are relative to your top-level project directory; you cannot enter an arbitrary absolute directory name. The directory finder will not prevent you from attempting to use an arbitrary path, but only directories located within your project folder will be accepte1. Unlike the “general” settings tab, the “services” settings tab values are set on a per project basis. The values displayed represent the current project (the project selected in the project tab). If you have no current project selected, this tab displays nothing.
    • In a future version of the Intel XDK, the Emulator tab settings will be merged with this dialog. When working from the Emulator tab you will see two “gear” icons: the Emulator settings icon in the upper left corner of the screen and the Settings dialog icon in the upper right corner.
  • Node Webkit updated to version 0.8.5 and all node modules updated.
  • Editor Updates:
    • Updated to Brackets Sprint 37.
    • Fixed git on Linux.
    • Made improvements to editor startup performance.
    • The editor extensions catalog was updated with newer versions of extensions. Post your suggestions on our forums.
  • Emulator Updates:
    • Added a new "Multi-Page Testing" panel. Enter any absolute URL and see that content in the emulator. This is useful for testing web applications that rely on server side support but want to be mobile-friendly. Note that API emulation does not work on pages loaded in this manner.
    • The Back button in the Devices Panel now implements "back" in the program under test, not "back" in the Intel XDK itself.
  • Crosswalk Updates:
    • The version of the Crosswalk build targets available via the Intel XDK’s “Build” tab has been updated. The stable version of Crosswalk has been upgraded to version 4.32.76.6 and the beta version has been updated to 5.34.104.2 Several new features are included in Crosswalk-5 including a new SIMD JavaScript API that takes advantage of SIMD support on Intel processors.
      Crosswalk-4 release notes can be found at: https://crosswalk-project.org/#wiki/Crosswalk-4-release-notes
      Crosswalk-5 release notes can be found at: https://crosswalk-project.org/#wiki/Crosswalk-5-release-notes
    • The version of Crosswalk used to enable the debug and profile features in the Intel XDK has been updated to match the beta version - Crosswalk 5.34.104.
  • App Starter:
    • Updated to App Framework 2.1.
    • UI updates to toggle between widgets and full screen modes.
    • Widget sections can be collapsed/expanded.
    • Added title under each icon in widgets sections.
  • App Designer updated to use App Framework 2.1.
  • Added a Twitter Feed icon to top navbar so you can follow Tweets about the Intel XDK.
  • In conjunction with this release, App Preview has been updated for iOS, Windows, Windows Phone and Android.
    • Updates for all platforms:
      • Bug fixes, branding updates and feature enhancements.
      • LOTS of bugs have been reported and fixed in the build system since the last release - this release fixes all of those bugs in App Preview as well.
      • We have a new icon.
      • The most visible feature change is that you can now filter your list of apps - other usability changes are sprinkled throughout.
    • Additionally, for Android:
      • When previewing an app, you can now use the device back button to exit preview mode and return to App Preview (previously you had to close the app to return to App Preview).
      • Preview mode remote debugging is now enabled for KitKat devices from Chrome (while previewing your app, it will be listed as an inspection target in Chrome).

    Issues Addressed:

    • Based on customer feedback about slowness, we enhanced the performance of the Intel XDK when working with large projects that contain many files.
    • Added path information to projects list and project dropdown for duplicate project names stored in separate locations to provide disambiguation. Note: project names are not disambiguated in the build system.
    • Corrected an issue in App Designer that was causing the user_scripts.js file to be overwritten.
    • Corrected an issue in the emulator where the change orientation icons were acting as a “back” button.
    • Emulator now correctly uses the UserAgent string for the device under test, not the UserAgent string for the host system.
    • Addressed multiple crash items that were reported in the previous release.

    Known issues:

    Issue Workaround
    If Preview on Devices, the Debug tab, and the Profile tab seem to not be responding, especially when you start the process, it may be that App Preview is not running. The component that makes these function work, App Preview Crosswalk, requires that App Preview be running whenever you start these functions. Look for App Preview in your Android multitasking list or in the "running" list in the apps settings page of your device. If App Preview is not running kill the App Preview Crosswalk task by swiping it to the side (from the multitasking list) or by choosing "Force Stop" from the application manager in the settings section of your device. Re-launch App Preview manually. This process should restore the functionality of those features.
    If your project contains any files that are all uppercase in name (i.e. LICENSE) and zero length in size, the bundle created during sync to the test server (Test tab) or sync to the build server (Build tab) may become corrupt when downloaded to your device for test or submitted for build. Rename any such files to be lower case or remove them if they are not a necessary part of your project.
    The Live Preview feature requires the Chrome browser to work properly. If you are using a Linux system and running Chromium, you will not be able to use Live Preview. Install Google Chrome on your Ubuntu system
    On Mac OS X, if you exit the Intel XDK either by using CMD+Q or by selecting "Quit Intel XDK" from the Intel XDK menu, you will momentarily see an error dialog. This error does not affect the functionality of the Intel XDK and will be fixed in an upcoming release.
    If your app uses HTML files that don't include a <head> or <html> or <!DOCTYPE> tag the emulator thinks it is not a valid HTML file and won't load it. If you are using the Angular framework you may have some of these files in your project, which is normally okay, until you try to run your app in the emulator. (Your app will continue to run in App Preview, from the Test tab and from the Debug tab, it just fails in the Emulator tab.) You can work around the problem by inserting a <!DOCTYPE html> tag at the top of those files that won't load. This issue will be addressed in a future edition of the Intel XDK.
    When you create a new app from a template and then open that app inside of the UI editor (App Designer), you may be unable to select or modify some of the elements on the new app created from that template. Push the "recycle" button (the refresh button) in the toolbar, which will force App Designer to reread the new application. Now the sample elements in your new application should be selectable.
    When trying to test a project using the Test tab and the mobile wifi option (testing over your local wifi with App Preview) you may encounter a blank screen on your device after the app loads into App Preview. The Test tab is not observing the location of the index.html file in your application, as specified by the SOURCE DIRECTORY pathname specified on the Projects tab; the Test tab is looking for your application (e.g., the index.html file) in the PROJECT PATH directory. Move your application files up so they reside in the PROJECT PATH directory and change the SOURCE DIRECTORY so it is blank (points to the same directory as the PROJECT PATH) by pushing the pencil icon to the right of the SOURCE DIRECTORY pathname. Other tools within the Intel XDK will honor the location specified by the SOURCE DIRECTORY, so you must make sure this parameter points to the location of your index.html file.
     
     
     

    Intel XDK - Release - 2014 Feb 24 v505

    The main focus of this release was to address issues reported through testing and by our end users. We added some new features including a developer preview of our new Cordova Build.

    New Features:

    • Added "Developer Preview” of Cordova for Android build target to build system
      • Android only (Windows 8, iOS and Windows Phone 8 will be added in future releases
      • Based on Cordova 3.3.1-0.1.2
      • Features and settings are configurable via "intelxdk.config.xml" in your Intel XDK project
      • All Cordova "base” plugins are supported (version is configurable)
      • A subset of Intel XDK APIs are supported via Cordova plugins
      • The HTML assets for a project may be put into a subdirectory of the project root directory. For example, the Intel XDK ‘blank’ project will put the assets into a ‘www’ subdirectory. You may set/modify this directory in the Projects tab in the Source Directory field by selecting the edit icon.
      • Developer Preview means that this functionality has received minimal QA. Feedback is requested via our forums.
      • Additional details will be made available via forum and/or blog posts soon
    • Editor Updates:
      • Brackets updated to Sprint-36.
      • Editor extensions are enabled in this release. Use File->Extension manager to install and use them.
      • Open files in Editor using Drag and Drop
      • External changes to the project file are automatically reflected in the editor. It includes adding, deleting, moving and changing the content of the files
    • GIT Integration - Git users can use Brackets Git extension to manage the repository directly from the editor.
    • Static Checking - XLint, a compatibility static checker for Intel XDK is available starting this release as an editor extension. For more information, refer to http://software.intel.com/en-us/xdk/docs/xlint-intelxdk
    • Emulator Updates:
      • Cordova Audio Recording API functions now work under emulation
      • Cordova Beep notification function actually beeps under emulation
      • There is a "Back” button in the Device Emulator Panel. Currently this functions as a Back button would in a browser.
      • Emulator will work even if the HTML file doesn’t contain any <html> or <head> tag
    • App Starter updated with App Framework 2.0.6
    • App Designer can now create custom CSS classes and edit them directly within App Designer
    • Individual help topics have been added to the help menu for each tab which take you directly to documentation related to the current tab.
    • Added ‘safe’ restart mode on crash recovery.

    Issues Addressed:

    • Issues with the updater on MacOS systems that did not properly update to new version
    • Geolocation details tab issues in emulator
    • Emulator does not properly emulate appMobi pay services
    • Over 100 smaller issues addressed

    Known issues:

    Issue Workaround
    If selecting Help icon while working with an App Designer project, the Help becomes stuck on App Designer help. There is no known workaround.
    The User Agent string used under emulation does not match that of the selected device. The emulator attempts to set the navigator.userAgent property according with the device being emulated, but node-webkit treats this property as read-only so the emulator cannot modify it.
    This defect means that data returned from servers that sniff the User-Agent header may return inappropriate content. One such server is Google Maps.
    This problem is fixed in node-webkit version 0.9.x, but the Intel XDK currently requires node-webkit 0.8.x. When the user agent fix is back-ported in node-webkit version 0.8.5, upgrading to that version of node-webkit should fix the problem. This will require an Intel XDK update.
    There is no user-level workaround.
     
     
     

    Intel XDK NEW - Update - 2014 Feb 10 v419

    • Intel XDK can now be installed on Windows XP* platform. While it can be installed, XP is not a fully supported platform.
    • Made the Country list for signup a local file so that it is always available to users regardless of connectivity.
    • Emulator - The emulator synthesizes touch events from mouse events. Made improvements to these synthesized events where they did not behave properly for some higher level frameworks like Google Maps, which respond to both touch and mouse events.
    • Corrected an issue that caused an error when attempting to upload large projects to the build system.
     
     

    Intel XDK NEW - Update - 2014 Jan 10 v277

    • Updated to Node-webkit version 0.8.4
    • Build tab - corrected an error message thrown when network connection is lost.
    • XDK can now upload a bundle larger than 25 MB to the build system.
    • Prevent hot keys from being triggered by [AltGR] + [number] combo on foreign keyboards as this was overriding normal keys on some of those keyboards.
    • Corrected an issue when pasting text from clipboard into Find within the editor. Previously it would paste the text into the content of the file versus the Find input box.
    • Emulate Tab - corrected an issue (on Mac and Windows versions) where the Chrome Debug Tool window did not always restart in the same position and size when you changed devices. On Linux the size will be retained but the location is not retained. We will continue to work to correct that issue.
     
     
     

    Intel XDK NEW - Release - 2013 Dec 17 v240

    What’s new:

    • Added two new tabs: Debug and Profile. Make use of these tabs to remote debug your app on device or analyze the performance of the JavaScript used in your app using App Analyzer.
    • Remote Debugging allows user to debug on Android 4.x based mobile device connected via USB.
    • App Analyzer allows users to set breakpoints in code, inspect variables, and single step through source code.
    • App Analyzer supports the Crosswalk APIs and provide similar performance as apps built using the Intel XDK Crosswalk target build.
    • Improved Tizen app builds allowing Tizen code-signing to submit apps to Tizen App Store.
    • Added Hot-Keys to Switch between tabs in the XDX:
      • ['Ctrl'] + ['Tab'] = Switch to previous tab (show tab-switcher UI). (or if ['Ctrl'] is held and ['Tab'] pressed cycle trough tabs in switcher UI)
      • ['Ctrl'] + ['Shift'] + ['Tab'] = Show tab-switcher (or if ['Ctrl'] is held and ['Tab'] pressed cycle trough in reverse ordertabs in switcher UI)
      • ['Ctrl'] + [Number Key] = Switch to tab based on order in tab bar
      • Example: ['Ctrl'] + ['1'] = Switch to the first tab in the list (currently develop)
      • ['Ctrl'] + ['0'] = Switch to the projects tab
      • Note: on OS X the shorcuts that do not contain a ['Tab'] key can be used by substituting ['Command'] for ['Ctrl'] (but ['Ctrl'] can still be used if desired)
    • App Designer multiple page support, themes, and interactivity.
    • App Designer allows page and sub-pages creation, button hookup to pages, sidebars, popups or custom scripts.
    • App Designer allows animated transition selection for a link to a page and more.
    • App Designer allows users to “drop in” third party themes for frameworks that support it.
    • App Designer allows basic javascript editing within App Designer.
    • Brackets updated to Sprint 34.1.
    • Editor supports autocompletion for Cordova 2.9.0 and intel.xdk APIs.
    • Better editor integration with the OS:
      • File->Open lets open any file on the filesystem
      • File->Save As allows saving to any location on the local filesystem
      • “Show in OS” context menu in the file tree opens OS file manager (e.g. Explorer, Finder) at the project file location.
      • Editor uses JSHint instead of JSLint as in previous versions. JSHint can be configured using .jshintrc in the project root. For the documentation on configuration options and configuration file format, refer to JSHint Docs.
      • Added copy/cut/paste context menu in the editor.
    • Images can be previewed in the editor. In previous version they appeared as binary content.
    • Code/Design buttons are always displayed when using AppDesigner and AppStarter projects. Design button is only enabled on .html files in these projects.
    • Emulator now supports apps that use the synchronous form of XMLHttpRequest (XHR).
    • Emulator settings now let you choose whether the JavaScript console should be cleared each time the app restarts (default is to clear). App restarts when you click reload, change projects, change devices, or change source when the always reload setting is selected.
    • Emulator automatically restarts debugger if debugger is running when the app restarts. Debugger must still close during the restart operation itself.
    • Emulator correctly initializes Accelerometer panel to +9.81 in z-axis, not -9.81.
    • App Designer gets automatically opened when creating a new project.
     

    Known issues:

    Issue Workaround
    Cannot access project files on Windows via a UNC path. Make sure all your files are stored on a local drive.
     
     
     

    Intel XDK NEW - Update - 2013 Nov 07 v154

    • First Time users of Intel XDK NEW are required to either perform an initial login (if they already have an Intel XDK - Original account), or create an account if they don't already have one.
    • The text and link provided within "Email Invitation to Test Your App" on the Projects tab has been updated to use App Preview versus app.lab.
    • The following Intel XDK NEW and Intel XDK original conflict issues identified in the October release have been resolved:
      • Original Intel XDK cannot be started if Intel XDK NEW is already running
      • XDK NEW may not start if Original Intel XDK is already started.
    • Links for downloading App Preview from the various stores are provided on the Test tab for first time users who have not yet installed App Preview.
     
     
     

    Intel XDK NEW - Release - 2013 Oct 20 v115

    What’s new:

    • Brackets Editor updated to version Sprint 32
    • Mac* OS X and Ubuntu* Linux versions are now available as well as Windows*. Windows 8.1 supported.
    • Intel App Preview released to Google* Play Store and Apple* App Store. Intel XDK NEW now uses Intel App Preview for testing on device.
    • Test using Local WiFi is now available in Test Tab
    • App Starter has been integrated into Intel XDK and is an available option when creating a new project
    • App Designer and AppStarter are only available in projects of the corresponding type (see known issues)
    • Improved Intel XDK NEW documentation
    • An Intel XDK Overview Quick Tour has been added. It is available the first time you create a project, or always available from the Help menu
    • Added “Visit the Forums” and “Submit a Bug” items under the Help menu so users can better provide feedback or report issues.
    • Added additional tool tips and Info popups to aid users
    • App Designer now supports Adobe* Topcoat
    • Several new demo apps have been added to the “Work with a Demo” option when creating a new app.
    • Web App builds now work
    • Fixed bug where Intel XDK NEW crashed when switching devices in the Emulator while debug window open.
    • Fixed crash when attempting to select a project no longer on local file system.
    • Build page now closes when switching projects.
    • Script tag to embed for using the weinre* debugger has been corrected.
    • Links to PDF files from Build screens are now functional
    • Many other bug fixes based on user reports and feedback. Thank You.

    Known issues:

    Issue Workaround
    Original Intel XDK cannot be started if Intel XDK NEW is already running. Install Intel XDK New version 0154 update.
    - or -
    If using October 2013 release, start original Intel XDK first, then Intel XDK NEW
    Automatic Updates from some previous Mac versions won’t restart Intel XDK NEW after update. Manually start the updated Intel XDK NEW after the update completes.
    Updates from some previous Linux versions won’t work. Download the appropriate Linux version and run the installer manually.
    Old App Designer projects no longer open as App Designer projects. Modify the project-name.xdk file located in the project directory to change the type: field to   “type”: “App Designer”,.
     

     

*Other names and brands may be claimed as the property of others. table {display:block; overflow-x:auto;} table th { text-align: left; padding-left: 1.25em; padding-right: 1.25em; } @media all and (max-width: 720px) { /* Flip Scroll from http://elvery.net/demo/responsive-tables/ */ .flip-scroll .cf:after { visibility: hidden; display: block; font-size: 0; content: " "; clear: both; height: 0; } .flip-scroll * html .cf { zoom: 1; } .flip-scroll *:first-child+html .cf { zoom: 1; } .flip-scroll table { width: 100%; border-collapse: collapse; border-spacing: 0; -webkit-overflow-scrolling:touch; -moz-overflow-scrolling:touch; -ie-overflow-scrolling:touch; -o-overflow-scrolling:touch; overflow-scrolling:touch; } .flip-scroll th, .flip-scroll td { margin: 0; vertical-align: top; min-height: 1.25em; padding:3px; } .flip-scroll table { display: block; position: relative; width: 100%; } .flip-scroll thead { display: block; float: left; width: 33%; overflow: hidden; white-space: nowrap; } .flip-scroll tbody { display: block; width: auto; position: relative; overflow-x: auto; white-space: nowrap; } .flip-scroll thead tr { display: block; } .flip-scroll th { display: block; text-align: right; } .flip-scroll tbody tr { display: inline-block; vertical-align: top; } .flip-scroll td { display: block; min-height: 1.25em; text-align: left; } /* sort out borders */ .flip-scroll th { border-bottom: 0; border-left: 0; } .flip-scroll td { border-left: 0; border-right: 0; border-bottom: 0; } .flip-scroll tbody tr { border-left: 1px solid #babcbf; } .flip-scroll th:last-child, .flip-scroll td:last-child { border-bottom: 1px solid #babcbf; } }
For more complete information about compiler optimizations, see our Optimization Notice.