Intel XDK Login (Authentication) Process Changing

[PaulF_IntelCorp]

We are unifying your Intel XDK login with intel.com for a simpler and more secure login. This unification process means that we are automatically creating an account that you can use to login to this Intel XDK forum and the Intel Developer Zone using the same username and password that you now use to login to the Intel XDK. Other than this login unification no other Intel XDK functionality or settings are affected. If you experience any issues with this process, please leave a detailed post on this thread or send an email to html5tools@intel.com.

[Arve_S_]

Today after signing in to intel xdk I can't build to any platform and Intel XDK shuts down. It says that Intel XDK has encountered a problem and must restart.

I get this error log

xdk:client (1435586418607): Intel XDK: 1826
xdk:client (1435586418609): Platform: win32-ia32 (6.1.7601)
xdk:client (1435586418685): Starting client process initialization
xdk:server (1435586419478): Starting server process initialization
xdk:server (1435586419657): Http server started on the standard port 58889
xdk:server (1435586419692): Component "core:assert" starting import
xdk:server (1435586419693): Component "core:assert" finished initialization
xdk:server (1435586419693): Component "core:component-error" starting import

edit: When I logged in on my windows 7 computer it worked, but not from the windows server 2008 we use to publish our app. When using the Windows Server 2008 this error message appear.

[Pamela_H_Intel]

Arve,

When you attempted the builds, were you logging in to the same account on both machines?

[Arve_S_]

Yes, I used the same account on both machines.

[Pamela_H_Intel]

@Arve - Have you logged out and logged back in to XDK on the server? I know you said "after signing in" but I want to make sure we are on the same page . . .  It's possible, if you just stay logged in, that our switch to Single Sign On on Friday, caused XDK to think that your login was incorrect. So, please try closing XDK, ending any remaining xdk/apk processes in the task manager and logging in and building again.

[Arve_S_]

Yes, I have tried signing out and in. This error occures 2 seconds after I click "upload project" after clicking the build button.

[Swati_S_Intel1]

@Arve, I would recommend upgrading to the latest version of XDK (2170) and try building. If the issue still persists, please send us your account info i.e. userid and email.

Swati

[Arve_S_]

@Swati, Upgrading to the latest version of XDK is not an option for us as of now. We need to build the app using the legacy option because tap events and other events does not work when we build using the cordova options. We need to rewrite the code in order for this to work and that may take a few weeks, and we need to be able to build the app now. It seems odd that you can't build on the windows server, but it works fine on a windows 7 PC. They both run the same version of intel xdk(v1826)

[PaulF_IntelCorp]

The build system is independent of the XDK -- when you build with 2170 you are building with the same system that builds for 1995 or 1826. Both have access to the legacy build options, and both use the same build server and build process. There is no difference on that front. The differences are how the XDK handles things like settings, the Emulate tab, Debug tab, etc. The build process is not tightly linked to the XDK, it is a loosely-coupled arrangement.

[Arve_S_]

Ok, I will try upgrading if that is the case. But last time I upgraded the legacy build was removed from the Build tab, so we had to reinstall XDK again to the 1826 version. Also last time we upgraded the Emulate tab did not work, just presented a 404 error message.

Still it seems odd that the same version of XDK that dows work on a Windows 7 computer does not work on a Windows Server 2008.

And can you please point me in a direction to find how to convert my app to be able to build using the Cordova option? I can't get the tap events or any other events from App Framework to fire on the mobile device when I build using cordova option.

[Arve_S_]

I tried building again using the 1826 version and now it worked as expected.

[PaulF_IntelCorp]

Not sure why you were not seeing the legacy build options, they are still there, including the 2170 version. They look a little different, but they are still there, on the Build tab.

Regarding the Emulate tab, yes, some things can change there with new releases, since the Emulator is built into the XDK, only the Build system is remote in the cloud (and some features of the Test tab).

When building for Android we highly recommend you use the Crosswalk build option. Their are many problems with the Android webviews. See this article for some background: http://blogs.intel.com/evangelists/2014/09/02/html5-web-app-webview-app/

[kelvine_N_]

i have already signed up but the login screen is not appearing so that i can log in xdk. 

[PaulF_IntelCorp]

@kelvine -- can you try on another network, you might be experiencing a proxy problem or some other network interference. Check your firewall settings, as well. Be sure that the process nw or nw.exe can go through your firewall.