Intel XDK Early Access 3172 Release

Intel XDK Early Access 3172 Release

 

---- version 3172 Early Access announcement ----

On April 7, 2016 we released the sixth Intel XDK Intel XDK Early Access release (3172).

The Intel XDK Early Access release is provided as a way for you to try out and provide feedback on features we are considering for the mainstream release of the Intel XDK. The complete set of features we are previewing are detailed in the Intel XDK Early Access Release Notes.

NOTE: You can install both the Intel XDK and the Intel XDK Early Access release at the same time on your development system; however, you cannot run both at the same time. It is best to make a copy of an existing project before opening it with the Intel XDK Early Access release, especially if you only wish to experiment with the new features in the EA release. See this FAQ for instructions on how to make a copy of an existing Intel XDK project.

Below is a summary of the preview features in this EA release:

  • Crosswalk support for the Windows desktop.
  • Project assets (icons and splash screens) are now located in a folder outside of your source folder.
  • Real-time Resource Monitoring of HTML5 apps in the Debug tab.
  • The Intel XDK Profiling Tools are not integrated in the Chrome DevTools inside the Debug tab.

More details can be found in the release notes and in Joe's blog.

Download the Early Access installer here: https://software.intel.com/en-us/intel-xdk/early-access#downloadea

---- version 2866 Early Access announcement ----

On January 13, 2016 we released the fifth Intel XDK Early Access release (version 2866).

The Intel® XDK Early Access is a separate product and download. In this special version of the product we offer you the opportunity to try new features and, of course, gather feedback from you regarding those new features. We intend for Intel XDK Early Access releases to be fully functional and tested, but since they contain experimental features you should expect some instability or odd behavior relative to the mainstream Intel XDK releases.

In addition to the standard features found in version 2807 of the Intel XDK, the features being previewed in version 2866 of the Intel XDK Early Access include:

  • A new Build UI that can build for multiple targets with a single request.
  • Certificate Management Tool for direct control of your app signing certificates.
  • Combining Android and Crosswalk Build Settings for simpler configuration.
  • A new Publish Tab to help with publishing apps to stores.
  • Microsoft Windows 10 Universal build option for Windows and Windows Phone platforms.
  • Deprecation of the CLI 4.1.2 build option (expected to be retired in March, 2016).

Release notes can be found here > https://software.intel.com/en-us/xdk/docs/release-notes-information-inte... and Joe's blog regarding this release can be found here > https://software.intel.com/en-us/blogs/2015/12/15/intel-xdk-update-for-j....

You can download the early access release here: https://software.intel.com/en-us/intel-xdk/early-access#downloadea

You can safely install both the mainstream Intel XDK and the Intel XDK Early Access release onto your system (they are installed into different locations on your system). You CANNOT run both releases at the same time. Projects created by release 2496 or later of the mainstream Intel XDK are compatible, so it is not necessary to make a copy of existing projects before trying them with the Intel XDK Early Access.

The Intel XDK build system used by the Intel XDK Early Access is the same as that used by the Intel XDK.

Documentation specific to the Intel XDK Early Access release are available here: https://software.intel.com/en-us/xdk/docs/lp-early-access

---- version 2682 Early Access announcement ----

On November 10, 2015 we released the fourth Intel XDK Early Access release (version 2682).

The Intel® XDK Early Access is a separate product and download. In this special version of the product we offer you the opportunity to try new features and, of course, gather feedback from you regarding those new features. We intend for Intel XDK Early Access releases to be fully functional and tested, but since they contain experimental features you should expect some instability or odd behavior relative to the mainstream Intel XDK releases.

In addition to the standard features found in version 2673 of the Intel XDK, the features being previewed in version 2682 of the Intel XDK Early Access include:

  • Built in support for the Bower Package Manager
  • Resource Monitoring (via the Profile tab) for Apple iOS devices

Release notes can be found here: https://software.intel.com/en-us/xdk/docs/release-notes-information-inte....

You can download the early access release here: https://software.intel.com/en-us/intel-xdk/early-access#downloadea

You can safely install both the mainstream Intel XDK and the Intel XDK Early Access release onto your system (they are installed into different locations on your system). You CANNOT run both releases at the same time. Projects created by release 2496 or later of the mainstream Intel XDK are compatible, so it is not necessary to make a copy of existing projects before trying them with the Intel XDK Early Access.

The Intel XDK build system used by the Intel XDK Early Access is the same as that used by the Intel XDK.

Documentation specific to the Intel XDK Early Access release are available here: https://software.intel.com/en-us/xdk/docs/lp-early-access

---- version 2337 Early Access announcement ----

On October 12, 2015 we released the third Intel XDK Early Access release (version 2567).

The Intel® XDK Early Access is a separate product and download. In this special version of the product we offer you the opportunity to try new features and, of course, gather feedback from you regarding those new features. We intend for Intel XDK Early Access releases to be fully functional and tested, but since they contain experimental features you should expect some instability or odd behavior relative to the mainstream Intel XDK releases.

In addition to the standard features found in version 2548 of the Intel XDK, the features being previewed in version 2567 of the Intel XDK Early Access include:

  • Built in support for the Bower Package Manager
  • Resource Monitoring (via the Profile tab) for Apple iOS devices

Release notes can be found here: https://software.intel.com/en-us/xdk/docs/release-notes-information-inte....

You can download the early access release here: https://software.intel.com/en-us/intel-xdk/early-access#downloadea

You can safely install both the mainstream Intel XDK and the Intel XDK Early Access release onto your system (they are installed into different locations on your system). You CANNOT run both releases at the same time. Projects created by release 2496 or later of the mainstream Intel XDK are compatible, so it is not necessary to make a copy of existing projects before trying them with the Intel XDK Early Access.

The Intel XDK build system used by the Intel XDK Early Access is the same as that used by the Intel XDK.

Documentation specific to the Intel XDK Early Access release are available here: https://software.intel.com/en-us/xdk/docs/lp-early-access

---- version 2337 Early Access announcement ----

On August 6, 2015 we released the second Intel XDK Early Access release (version 2337).

The Intel® XDK Early Access is a separate product and download. In this special version of the product we offer you the opportunity to try new features and, of course, gather feedback from you regarding those new features. We intend for Intel XDK Early Access releases to be fully functional and tested, but since they contain experimental features you should expect some instability or odd behavior relative to the Intel XDK releases.

Features we are previewing in version 2337 of the Intel XDK Early Access include:

  • Plugin Fetching for better control of your Cordova plugin versions in your project
  • App Preview Debug Modules for customized debugging of your apps, including the use of third-party plugins
  • Language support for simplified and traditional Chinese. Change the locale in the "settings dialog" (gear icon in the upper right).

For detailed information on the release, please see the release notes here: https://software.intel.com/en-us/xdk/docs/release-notes-information-inte....

If you want to try it out, you can download it from: https://software.intel.com/en-us/intel-xdk/early-access#downloadea

IMPORTANT: You can install both the Intel XDK and the Intel XDK Early Access release onto your system (they are installed to different locations). However, you CANNOT run both releases at the same time. Also, projects are not compatible, so we STRONGLY ADVISE that you make a copy of any existing projects before testing them with the Intel XDK Early Access.

The build system used by the Intel XDK Early Access is the same as that used by the Intel XDK. There are some differences in how each version interacts with the build system, but the Cordova CLI build systems are the same.

Documentation specific to the Intel XDK Early Access release are available here: https://software.intel.com/en-us/xdk/docs/lp-early-access

---- version 2201 Early Access announcement ----

On July 6, 2015 we released the first Intel XDK Early Access release (version 2201).

The Intel® XDK Early Access is a separate product and download. In this special version of the product we offer you the opportunity to try new features and, of course, gather feedback from you regarding those new features. We intend for Intel XDK Early Access releases to be fully functional and tested, but since they contain experimental features you should expect some instability or odd behavior relative to the Intel XDK releases.

The new features we are previewing in version 2201 of the Intel XDK Early Access are:

  • Plugin Fetching for better control of your Cordova plugin versions in your project
  • App Preview Debug Modules for customized debugging of your apps, including the use of third-party plugins

For detailed information on the release, please see the release notes here: https://software.intel.com/en-us/xdk/docs/release-notes-information-inte... or read Joe’s blog at: https://software.intel.com/en-us/blogs/2015/06/15/intel-xdk-early-access

If you want to try it out, you can download it from: https://software.intel.com/en-us/intel-xdk/early-access#downloadea

IMPORTANT: You can install both the Intel XDK and the Intel XDK Early Access release onto your system (they are installed to different locations). However, you CANNOT run both releases at the same time. Also, projects are not compatible, so we STRONGLY ADVISE that you make a copy of any existing projects before testing them with the Intel XDK Early Access.

The build system used by the Intel XDK Early Access is the same as that used by the Intel XDK. There are some differences in how each version interacts with the build system, but the actual Cordova CLI build systems are the same.

Documentation specific to the Intel XDK Early Access release are available here: https://software.intel.com/en-us/xdk/docs/lp-early-access

26 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

i can not install Early Access with an existing version of XDK.

the installer only ask me to remove or repair installation.

how to install this release without removing xdk ?

Hi Ven,

The Early Access download page can be a little confusing.  I am guessing that the download package you selected was from the download button at the top of the page.    That download is the Intel XDK and is probably the version you already have.    The Intel XDK Early Access download is at the bottom of the page.   If you download from there, you should see that the package being downloaded starts with xdk-ea.....

You should then be able to install that version along side the Intel XDK as it installs in a separate directory by default.

 

Hi Hans,

you were right ! the download link was at the bottom ^^.

thank you !

Dear Paul

When I am trying to add a plugin via the core plugins --> Geolocation --> Add plugin button

It says "Unknown error" 

Is it a problem with this release?

This is not a problem I have seen, especially if you are trying to use the core Cordova plugins. The EA version pulls plugins directly into your project directory. You should see a plugins directory in your project that contains the plugin sources that correspond to the plugins you have selected -- do you see the plugins you've selected in that directory? Does this happen only with the geo plugin or with any plugin?

@Rahul, I had come across this  issue with Early Access release and it is being addressed. For now, please  close the XDK and restart your plugin will show up. It will show a dialog box to choose plugins, select the plugin from the directory and your plugin will be added successfully.

 

 

Hi Swati,

I installed  Intel XDK Early Access and removed Intel XDK. But I cant build windows 8.1 as I posted early...

 

 

 

 

When is the XDK IoT going to get updated again?  The non-IoT version is at version 2496 now while the IoT has been stuck on 2170.  I have been having to maintain two computers with different installations (one IoT and one non-IoT) just to use the latest features (i.e. the latest version of Cordova) and IoT features at the same time.  Can you please fix this so we can use one version (i.e. the IoT version) for everything by keeping the IoT version it up to date with the non-IoT version?

 

The IoT was also updated, I see that the IoT team has not updated it on the download site. I'll make a request to get it there.

- - - - edit - - - -

The IoT edition is released on a different cadence, which is a function of the larger IoT development kit. They have a release schedule for later this year, at which time the IoT edition of the XDK will be released. It will be based on the current release of the XDK, possibly with a few updates. Sorry, I misspoke, it is not available in a new update at this time.

p.s. You can install both versions on your system at the same time, they install into different locations, you may have troubles if you try to run both at the same time, but you don't have to install them on a separate machines.

Quick question for you - it is stated that:

Projects created by release 2496 or later of the mainstream Intel XDK are compatible, so it is not necessary to make a copy of existing projects before trying them with the Intel XDK Early Access.

I want to confirm that you mean it will not in any way make it incompatible with the mainstream tool?  So I can use XDKea on one machine, and whatever code changes are made will work on my other machine, running 2548?

Sorry if that's obvious, just want to be sure!  Thanks

43Folders Technology Solutions

Yes, you can open a project with the mainstream XDK (2548) and also open that same project with the EA release (2567) -- you cannot do that simultaneously! Meaning, you cannot run the two versions of the XDK at the same time. You do not have to install them on separate machines, they can be installed on the same machine, because the EA release gets installed into it's own directory on your system and maintains a separate project list.

If you use the Bower feature it will add some directories and files into your www directory. This will not interfere with your ability to use the mainstream version, just that the mainstream version will not "manage" those Bower-managed libraries (you can still use them in your app when using the mainstream edition, just not manage them).

Downloaded (Y) 
Thanks ^_^ 

Loved the interface ! :)

Thanks for a very nice EA update.

I tried the new Android signing feature.

App's install fine on recent devices, but install fails on older Android devices. Apparently it has something to do with SHA256 not being supported on older devices:

http://stackoverflow.com/questions/33149140/play-store-cant-install-app-error-code-103

I did it the old way, and it worked fine.

Andrzej -- how old are the devices that had a problem? If they were Android 2.x or 3.x they cannot install apps built with CLI 5.x -- Only Android 4.0 and above are supported by the CLI5 and greater Cordova build systems.

Two phones had the problem, both running 4.0. More recent phones didn't have the problem.

I rebuilt the app and signed manually with signapk.jar and zipAlign. After that, it installs fine.

Did you submit a keystore of your own to the EA cert management system and that failed? Or did you use a keystore that was generated by the XDK and that one caused the failure? You can submit your own keystore to the build system (in the EA release).

I submitted my own keystore because I had to be able to update an existing app. I have never used the keystore before, as I just signed directly with a .pem and .pk8

I followed this guide creating the keystore:

http://stackoverflow.com/questions/22212869/how-can-i-generate-an-android-keystore-from-a-key-pk8-and-certificate-pem

Just so I am clear, are you saying that everything works fine with your keystore?

Did the keystore created by the XDK work or fail?

Please clarify. I'm trying to understand if we created a keystore that did not work on your older 4.0 devices of if that keystore was one that you provided. I need this information in order to help engineering understand if we have a problem.

Ok, I will try to be precise:

I never tried a keystore created by XDK.

The first version of my app was done years ago in AppMobi. I generated a .pk8 certificate and a .pem file, and AppMobi would sign the app, and everything was fine.

When Intel took over, my app was transfered, but the certificate was lost in the process. So ever since, I have done the signing myself using the original two files.

Now, I tried creating a keystore based on those files and use that in XDK. It works on 4.4 devices, but not 4.0. So, it can either be a problem with the keystore itself, or with the signing by XDK.

 

Thank you, Andrzej, that makes sense to me.

I suspect it is a problem with the way you created the keystore, there is a "SHA1" version of the keystore and a "SHA256" version. You usually get the SHA256 by default when using JDK 1.8; SHA256 won't work with older devices. See this SO post for some options that need to be added if you are using jarsigner in the JDK 1.8 > http://stackoverflow.com/a/34875983/2914328 < you have to add -sigalg SHA1withRSA -digestalg SHA1 to the command-line.

We are confirming that our new signing tools are doing this correctly. Thanks for bringing it to our attention.

Thanks Paul,

I will be updating my app during next week. I will try to recreate the keystore.

Will keep you posted.

Andrzej

Andrzej -- can you run the following command on your keystore and provide the output, so we can see if it is a DSA with SHA-1 or an RSA with SHA-256 signature? This will help us to understand more about what was happening and, potentially, how to prevent it in the future.

  • keytool -list -v -keystore <keystore file name>

Here you go:

 

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

Alias name: hn.android.key
Creation date: 11-02-2015
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=xxxxxxxxxxxxxxxx
Issuer: CN=xxxxxxxxxxxxxxxx
Serial number: xxxxxxxxxxxxxxx
Valid from: Tue Aug 21 11:49:56 CEST 2012 until: Fri Jan 06 10:49:56 CET 2040
Certificate fingerprints:
         MD5:  xxxxxxxxxxxxxxxxxx
         SHA1: xxxxxxxxxxxxxxxxxx
         SHA256: xxxxxxxxxxxxxxxxxxx
         Signature algorithm name: SHA1withRSA
         Version: 1

*******************************************
*******************************************

Thank you, Andrzej.

Leave a Comment

Please sign in to add a comment. Not a member? Join today