Intel XDK updated to v 2496

[John_H_Intel2]

We have just released the September 2015 Intel XDK.  The version number is 2496.

Here are some of the new features released:

• Support for Cordova 5.1.1 has been implemented
• Plugin fetching is now part of the Intel XDK 
• App Preview custom debug modules
• Crosswalk as a plugin
• You can now modify the location of your Game assets directory

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

You can also read Joe’s blog at:  https://software.intel.com/en-us/blogs/2015/09/23/september-2015-intel-xdk-update-hello-cordova-5

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 xdk.intel.com  and install.

If you are experiencing issues, please create a new thread with all the info.

[Barry_Johnson]

Failed during project conversion (while updating the plugins it appeared). The error message is among the less useful produced by the XDK (almost as bad as the "build failed...check your project assets" message which gives absolutely zero information).

Clearly, I clicked cancel.

Now it does not recognize the xdk file as being the proper version. ("Type Error: Invalid version")

Problem One: the XDK upgrade process does not update the Cordova CLI version to a supported version (since I only been doing crosswalk builds with this, I hadn't really paid much attention to the Cordova build settings). If I manually change the project/buildConfigurations/android/cordovaCLIVersion to "5.1.1" (from the obviously unsupported 3.3.0, I can make some progress at this point. Now opening the .xdk project results in this actually useful message:

(While I am reminded of it - it is hard to imagine a more cumbersome process for including screen caps than the one this forum uses - particularly when many platforms now support capturing and handling the pasting of images from the clipboard).

Choosing "Use Project File" in the above dialog will reprise the "unexpected error to process.exit()" shown above.

Choosing "Use Directory" in the above dialog will result in:

At this point, if I then go into the .xdk file and manually strip out the two offending plugins (I will note that the SocialSharing plugin is the which was in the upper portion of the "featured" list on the right) - I can actually open the project. Very exciting.

I only had the ionic keyboard in there from a prior test when the XDK build was failing with various plugins and I wanted to make sure it wasn't an "all plugins" issue. I do use the SocialSharing functionality. I figured no big deal, I'll just add it back in via the interface:

I pop into the new plugin interface (which is lovely, really). Select Social Sharing, then "add plugin"...and then this:

Did I mention how annoying the file upload process is on this forum? :-)

Thoughts, suggestions, guidance?

[Miguel_R_1]

Crosswalk 15 bulid Fail :

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all dependencies for configuration ':_armv7DebugCompile'.
   > Could not find any version that matches com.google.android.gms:play-services-gcm:+.
     Searched in the following locations:
         https://repo1.maven.org/maven2/com/google/android/gms/play-services-gcm/maven-metadata.xml
         https://repo1.maven.org/maven2/com/google/android/gms/play-services-gcm/
         https://download.01.org/crosswalk/releases/crosswalk/android/maven2/com/google/android/gms/play-services-gcm/maven-metadata.xml
         https://download.01.org/crosswalk/releases/crosswalk/android/maven2/com/google/android/gms/play-services-gcm/
     Required by:
         :android:unspecified
   > Could not find any version that matches com.android.support:support-v4:+.
     Searched in the following locations:
         https://repo1.maven.org/maven2/com/android/support/support-v4/maven-metadata.xml
         https://repo1.maven.org/maven2/com/android/support/support-v4/
         https://download.01.org/crosswalk/releases/crosswalk/android/maven2/com/android/support/support-v4/maven-metadata.xml
         https://download.01.org/crosswalk/releases/crosswalk/android/maven2/com/android/support/support-v4/
     Required by:
         :android:unspecified

[John_H_Intel2]

I tried to create a project from build #1995 with the CLI version 3.3.0.
Added social sharing plugin and com.ionic.keyboard as the user included in the project.
The upgrade process went smoothly without any issue for me.
I saw something in the forum that the user manually modified the <project>.xdk file.

So, it may have caused the project file invalid.
I guess the work around is to remove all plugins and add them back.

• Remove the <project>/plugins directory
• Open the project in the XDK, which will show the “inconsistent plugins” dialog.
• Choose “use directory” which are marked “plugin not found”
• Add all the plugins back in the plugin manager UI (social sharing and ionic keyboard)

If this does not help, I need to look at the whole project source if possible.

Otherwise, the user can create a new project by copying all his <project>/www source into a separate directory, and “start a new project”->”import your html5 code base”

[Barry_Johnson]

Hi John-

Thanks for your reply.

I actually did create a new project as I assumed that if the CLI version isn't even getting updated automatically in the upgrade, who knows what other detritus is not getting cleaned up.

Let me tell you my story.

Take 1:

Selected the HTML5+Cordova "blank" project. (created be default to CLI 5.1.1)

I replaced in its entirety the provided /www content with the source of my app.

I manually added a handful of "standard" plugins (InAppBrowser, Capture, Camera, Notifications, Vibration) - so far so good.

I added the "Social Sharing" plugin. Click "add" - boom "unexpected call to process exit) (same as the last screen shot in my post above)

OK - starting over

I created a new project. Selected HTML5+Cordova "blank" project.

I TOUCHED NOTHING.

I went to plugins, attempted to add Social Sharing. - unexpected call to process exit. 

You may find this project in the attached zip xdk-test-1

Take 3

I created a new project. Selected HTML5+Cordova "blank" project.

I went to the build settings and changed the CLI version from 5.1.1 to 4.1.2 - I selected the "downgrade CLI & plugins" button.

(Care to guess what happens next?)

I went to plugins, attempted to add Social Sharing. - unexpected call to process exit.

I am sensing a theme here. :-)

You may find this project in the attached zip xdk-test-2

Thoughts? Happy to send you any diagnostic info you would like. I am on Windows 10 (not even the tech preview on this machine - I keep it pretty vanilla.)

Thanks.

P.S. As an aside, these problems are a real shame, as the IDE is itself looking better than ever (although the on-screen emulator running while debug mode is active is, other than being a neat trick, mostly annoying since a) it is redundant to what is being display on device b) cannot fully render what is on the device anyway (i.e. if a call is made to plugin, also the fidelity even just with the HTML content is so-so) and c) crowds out the real show on that screen, which is the develop tools.

[John_H_Intel2]

OK - starting over

I created a new project. Selected HTML5+Cordova "blank" project.

I TOUCHED NOTHING.

I went to plugins, attempted to add Social Sharing. - unexpected call to process exit. 

I did the above and got the attached image. Everything worked as it should. It would seem that you are having some sort of permissions issues connecting/downloading the plugin from the web.

What kind of firewall/proxy are you behind?
What do you have installed for security/antivirus?
Are you and Admin of your computer?
 

[John_H_Intel2]

I had no issues adding the social plugin on windows 8 or 10.

[Barry_Johnson]

Windows Defender; Windows Firewall; no proxy - Have a Netgear nighthawk between my desk and Comcast.And yes, I am admin of my computer.

It would be very puzzling if this were a firewall issue, since I have not other difficulties connecting to either the servers for builds or when directly accessing (e.g.) Github via the desktop app or the command prompt.

I also question it being a network issue because I would find it puzzling if you are making network calls to remove plugins, yet, that produces an error as well:

If it may be helpful,  I have tried this with several other of the 3rd party plugins. There is a mix of complete failure and partial failure.

For example, this plugin fails entirely:

Yet, this one works "partially" - i.e. it reports an error, but the plugin is actually added (you can see the dimmed success dialog behind the error dialog).

Have to run for now. Will check back later. Thanks!

[PaulF_IntelCorp]

@Miguel -- what you are seeing is a known issue, we do not yet have a solution. One of the plugins you are using is trying to retrieve a required Android library but is not locating it. When using something like Cordova CLI that library module would be found on your development system as part of your Android Studio installation, but since the build system is in the cloud, the library either needs to be in one of the Maven repos (see the error messages) or installed on the build system.

I will refer this to engineering.

p.s. Please start a new post, this thread is about a different subject and having two issues in the same thread is very difficult to support.

[Barry_Johnson]

BTW - quick follow-up on a couple of items.

1) There was no "attached image" in the message you sent above. It was not important, but, I am assuming you are proxying feedback from someone in development. It may be helpful to see what exactly he or she saw. As an aside, regarding the first comment: starting with v1999 is great, but would not simulate my original experience unless it was upgraded through successive XDK version, at least one of which (and I think two) made breaking changes to the .xdk file.

2) As a clarification, I realize I wrote "third party plugins" in my prior message, but should have more specifically stated "featured plugins." To the extent one scrutinized the (relevant) dimmed content in the background, one would see that, but thought I would point out the issue specifically.

A general comment:

it should be obvious, but I will say it: it is hard not to believe that diagnosing or resolving this issue would be facilitated by providing error messages with actual content. While this thread is by no means an exhaustive catalog of the XDK's failing without providing a meaningful error message, it is remarkable that I was able to provide six screenshots (out of seven) that offer error messages with absolutely no information whatsoever: two displaying what appears to be an empty JSON object; two of provide an "unknown" message as a bullet point; and two which are just titled "Unknown error" with mention of the unexpected call to process.exit()

A final,tangential, item - in the course of probing the success or failure of including various plugins, I noticed the content error in the following screen cap, in which the description text for the Push (pushwoosh) plugin is older text for the Fullscreen  plugin (note that it does in fact vary slightly from the copy for "Full Screen for Android" in the same list).

[PaulF_IntelCorp]

@Barry, can you attach the contents of the xdk.log file that is generated after one of these errors happens? Once you get an error, close the XDK and attach the xdk.log file to your post, explaining/showing the error. Make sure you get the xdk.log file BEFORE you restart the XDK, it is wiped clean when the XDK starts.

You'll find the xdk.log file here, on a Windows machine: %LocalAppData%\XDK\xdk.log

p.s. I am in full agreement with your assessment of the machinations required to get an image into a post. I've brought this up with the folks that maintain the forum, for what it's worth. :)

[PaulF_IntelCorp]

@Barry -- thanks for pointing out the snafu in the pushwoosh plugin description. We will get that cleaned up.

Regarding your comment:

P.S. As an aside, these problems are a real shame, as the IDE is itself looking better than ever (although the on-screen emulator running while debug mode is active is, other than being a neat trick, mostly annoying since a) it is redundant to what is being display on device b) cannot fully render what is on the device anyway (i.e. if a call is made to plugin, also the fidelity even just with the HTML content is so-so) and c) crowds out the real show on that screen, which is the develop tools.

This is actually a "feature" of the CDT that is embedded in the Debug panel, it is not being presented by the XDK, but by CDT, and is a function of the Chrome runtime that you are interacting with in the debug module on the device, so it does not show up with all versions of Crosswalk/Chrome. To turn off that big screen cast image, there should be a small device icon, sometimes at the top and sometimes at the bottom of the CDT window (again, it varies with the version of Chrome in the debug module, Google keeps changing it). Touch that "device icon" to make the device screen cast go away.

[Son_V_]

Hi,

I've just update to this latest version and can not turn off the asset management window. That window took a big part of my laptop screen. Anyone know how to turn it off, please show me! Thank you.

[Barry_Johnson]

Hi Paul-

First - thanks for letting me know about the screencast/emulation being part of CDT and how to disable it as well as for your comments regarding image posting on these forums.

Regarding the main substance of the conversation - I was actually one step ahead here - I was getting ready to do an uninstall and reinstall, since I figured once the tech support tropes of "your firewall" get brought up, a clean install is a likely pending suggestion. I may actually test it on another Windows box I have with virtually nothing on it other than Virtual Box.

In any case, I figured I would try and preserve the settings data, for forensic value if nothing else. I had not closed the XDK from the experiments earlier, and had a nearly 10k-line log file, most of them being like:

xdk:server (1443058090551): memmrk:	29741180	36888832
xdk:client (1443058090630): memmrk:	51800444	61334912

I have attached that file zipped in big-xdk-log.zip.

I then opened the XDK again to collect the diagnostics. you wanted. When it reopened the last test project I had been in, it presented the following dialog:

I selected "Use Project File" - it attempted to resolve them, spun for a bit, and then presented the following. I almost didn't include the screen cap, but it is subtly different than any that I have posted in this thread, so might be relevant.

I canceled and was popped into the project. I attempted to remove, via the circle-minus button, the two plugins mentioned in the above dialog. In each case, I was presented with the small "Unknown Error: An unknown issue occurred during the plugin operation:{}" dialog. (The last image of my post of 13:40 today)

I then closed the XDK. I am attaching that xdk log file as reopening-xdk-log.zip.

I then removed the project from the XDK file list. It went to the more vanilla xdk-test-1 which I created based on the second set of steps in an earlier message. I then closed and relaunched the XDK, cleanly. This takes me to line 515 in a new xdk log file. 

I then created a new project / blank HTML+Cordova named xdk-test-3, clicked add plugins, added Social Sharing, got the expected error message. Acknowledged error dialog. Closed plugin dialog. Closed XDK via the title bar "X".

This file is attached in new-project-xdk-log

I really appreciate your assistance. Please let me know if there is further diagnostic information I can provide. Thanks again.

[Nadeem_N_]

I regret updating as i was about to patch critical things for my app and to submit to live but yesterday update pushed everything to wall. As a request please resolve this issue as soon as possible. @Paul F.

[John_H_Intel2]

I am locking this topic so we can better support those of you that are having issues.

Please create a new topic with a link back to any details you have provided here.

It is very difficult to support everyone in one thread.