topic @Amr - I think you are asking in Software Archive

Downloading version 2366

Anusha_M_Intel1 — Fri, 25 Sep 2015 21:55:52 GMT

If you are experiencing issues with the 2496 release, please first try to completely uninstall the XDK and re-install version 2496 of the XDK. For instructions on how to completely uninstall Intel XDK from your system, see this forum post: https://software.intel.com/en-us/forums/intel-xdk/topic/542074

Download 2366:
If that does not resolve the issue, and you want to install 2366, you can find the install files attached to this thread. You will have to unzip the Windows installer first before you can install on Windows.

Running two versions of Intel XDK:
Make sure you install 2366 before 2496. If you have 2496 on your system during 2366 installation, it will not allow you to stating you have a higher version already installed. Please note that while you can have two versions, you cannot run them simultaneously.

On a Windows System:

Uninstall any previous versions of XDK and install 2366
Search for the Intel XDK shortcut by pressing 'Win + Q' -> 'Intel XDK'. Right click on the selection and click on 'Open File Location'
Your Intel XDK installs to AppData by default. So open windows explorer and type '%localappdata%/Intel' in the folder path and it should contain a folder called 'XDK'. Rename that folder to a name of your choice. For Example, XDK > XDK2366. Avoid spaces and special characters.
Now, go back to your shortcut found in Step 2 -> Right click to Properties. The shortcut tab will contain a field called target which is the path to the target application the shortcut points to.

Now that the path to your application (nw.exe) has changed, you need to change the path the shortcut points to. There will be two paths. Make sure to change the 'XDK' folder to 'XDK2366' in both.

Eg:
<C:\Users\myid\AppData\Local\Intel\XDK\bin\nw.exe "C:\Users\myid\AppData\Local\Intel\XDK\xdk\xdk-wrapper">
should be changed to
<C:\Users\myid\AppData\Local\Intel\XDK2366\bin\nw.exe "C:\Users\myid\AppData\Local\Intel\XDK2366\xdk\xdk-wrapper">
Apply Changes and you will find that the Icon has disappeared. Go to properties again and click on 'Change Icon...' button on the Shortcut tab and browse to your XDK2366 folder (Eg: C:\Users\myid\AppData\Local\Intel\XDK2366\bin) which contains the icon file named 'xdk.ico'. Apply Changes.
Open the shortcut to test that it opens Intel XDK and then copy paste the shortcut to Desktop renaming it. Eg: 'Intel XDK 2366'.
Install your second version (2496) of Intel XDK. It will install in the 'XDK' folder in AppData.
Make another copy of your 'Intel XDK 2366' shortcut on your desktop. Right click to Properties and change the folder name in the Target Paths from 'XDK2366' to 'XDK' so it points to the newly installed version. Rename your new shortcut to avoid confusion.

On a Mac:

Uninstall any previous versions of XDK and install 2366.
Open Finder -> Go to Applications -> Find Intel XDK.app. Right click on that and choose "Duplicate." This will create a duplicate of that application with a different name. You can rename it as you wish (e.g. XDK-2366.app).
To start the newly archived copy from the command-line, type: '$ open XDK-2366.app'. You might want to "right-click" the icon in the "Dock" and choose to Keep in Dock under the Options menu. This will make it easier to startup your archive copy later.
Install 2496 and it will install in place of Intel XDK.app.

On a Linux System:

On a Linux machine it is easiest to create your "archive copy" during installation. Rather than performing a root or sudo installation in the /opt directory (or a similar system directory), perform a local user install and choose an appropriately named directory in your $HOME directory.

Some useful tidbits:

Avoid updating 2366. Use the ‘Remind me later’ route.
Note that there is only one global-settings.xdk file on your system that is used by all the installed copies of the XDK (except IoT and Early Access editions).
There are some significant changes in the projects properties stored in the project.xdk file inside each XDK project directory, which might make going back and forth between old and new versions of the XDK somewhat difficult. Until that process has been completely ironed out you might want to keep copies of the project.xdk and project.xdke files handy in order to go back to a prior version of the XDK. Refer to question 34 of the FAQs to learn how to make a copy of an existing Intel XDK project.
Make a copy of your global-settings.xdk file, too – just in case. Refer to question 5 of the FAQs to locate this file.

i did like that but i see

Mour_D_ — Sat, 26 Sep 2015 06:24:13 GMT

i did like that but i see error

xdk:client (1443248623192): memlim: 767557632
xdk:client (1443248623197): Setting NW crash dump to: C:\Users\10312\AppData\Local\XDK
xdk:client (1443248623428): Intel XDK: 2366
xdk:client (1443248623428): Platform: win32-ia32 (6.1.7601)
xdk:client (1443248623573): could not find a file for indirect file localecss.css
xdk:client (1443248623595): could not find a file for indirect file localecss.css
xdk:client (1443248623598): could not find a file for indirect file localecss.css
xdk:client (1443248623601): could not find a file for indirect file localecss.css
xdk:client (1443248623605): Starting client process initialization
xdk:client (1443248623628): NW Cache is up-to-date.
xdk:server (1443248624389): memlim: 767557632
xdk:server (1443248624394): Setting NW crash dump to: C:\Users\10312\AppData\Local\XDK
xdk:server (1443248624637): Starting server process initialization
xdk:server (1443248624791): Http server started on the standard port 58889
xdk:server (1443248625823): Component "core:assert" starting import
xdk:server (1443248625824): Component "core:assert" finished initialization
xdk:server (1443248625824): Component "core:component-error" starting import
xdk:server (1443248625825): Component "core:component-error" finished initialization
xdk:server (1443248625825): Component "core:command-line-options" starting import
xdk:server (1443248625825): Component "core:command-line-options" finished initialization
xdk:server (1443248625825): Component "core:service-error" starting import
xdk:server (1443248625825): Component "core:service-error" finished initialization
xdk:server (1443248625825): Component "core:buffer" starting import
xdk:server (1443248625825): Component "core:buffer" finished initialization
xdk:server (1443248625825): Component "core:signaler" starting import
xdk:server (1443248625828): Component "core:signaler" finished initialization
xdk:server (1443248625828): Component "core:signaler-group" starting import
xdk:server (1443248625831): Component "core:signaler-group" finished initialization
xdk:server (1443248625831): Component "core:logger" starting import
xdk:server (1443248625832): Component "core:logger" finished initialization
xdk:server (1443248625832): Component "core:http-request" starting import
xdk:server (1443248625836): Component "core:http-request" finished initialization
xdk:server (1443248625836): Component "core:database" starting import
xdk:server (1443248625837): Component "core:database" finished initialization
xdk:server (1443248625837): Component "core:version" starting import
xdk:server (1443248625837): Component "core:version" finished initialization
xdk:server (1443248625837): Component "core:userfs-name-converter" starting import
xdk:server (1443248625838): Component "core:userfs-name-converter" finished initialization
xdk:server (1443248625838): Component "core:crash-handler" starting import
xdk:server (1443248625839): Component "core:crash-handler" finished initialization
xdk:server (1443248625839): Component "core:i18n-support" starting import
xdk:server (1443248625840): Component "core:i18n-support" finished initialization
xdk:server (1443248625840): Component "core:theme" starting import
xdk:server (1443248625895): Component "core:theme" finished initialization
xdk:server (1443248625897): Component "server:userfs" starting import
xdk:server (1443248625905): Component "server:userfs" calling init()
xdk:server (1443248625947): Component "server:userfs" finished initialization
xdk:server (1443248625947): Component "server:user-profile" starting import
xdk:server (1443248625956): Component "server:user-profile" calling init()
xdk:server (1443248625957): Component "server:user-profile" finished initialization
xdk:server (1443248625957): Component "server:ui-builder" starting import
xdk:server (1443248626039): Component "server:ui-builder" calling init()
xdk:server (1443248626041): Component "server:ui-builder" finished initialization
xdk:server (1443248626041): Component "server:emulator-notification" starting import
xdk:server (1443248626047): Component "server:emulator-notification" calling init()
xdk:server (1443248626048): Component "server:emulator-notification" finished initialization
xdk:server (1443248626048): Component "server:emulator-webserver" starting import
xdk:server (1443248626050): Component "server:emulator-webserver" calling init()
xdk:server (1443248626051): Component "server:emulator-webserver" finished initialization
xdk:server (1443248626051): Component "server:new-project-creator" starting import
xdk:server (1443248626056): Component "server:new-project-creator" calling init()
xdk:server (1443248626056): Component "server:new-project-creator" finished initialization
xdk:server (1443248626056): Component "server:zip-util" starting import
xdk:server (1443248626061): Component "server:zip-util" calling init()
xdk:server (1443248626061): Component "server:zip-util" finished initialization
xdk:server (1443248626061): Component "server:uuid-server" starting import
xdk:server (1443248626066): Component "server:uuid-server" calling init()
xdk:server (1443248626066): Component "server:uuid-server" finished initialization
xdk:server (1443248626066): Component "server:app-starter" starting import
xdk:server (1443248626076): Component "server:app-starter" calling init()
xdk:server (1443248626078): Component "server:app-starter" finished initialization
xdk:server (1443248626079): Component "server:force-download" starting import
xdk:server (1443248626083): Component "server:force-download" calling init()
xdk:server (1443248626083): Component "server:force-download" finished initialization
xdk:server (1443248626083): Component "server:updater" starting import
xdk:server (1443248626092): Component "server:updater" calling init()
server:updater (1443248626092): config.base-auto
server:updater (1443248626092): url=auto
xdk:server (1443248626093): Component "server:updater" finished initialization
xdk:server (1443248626093): Component "server:editor-node" starting import
xdk:server (1443248626127): Component "server:editor-node" calling init()
xdk:server (1443248626128): Component "server:editor-node" waiting for delayed initialization
xdk:server (1443248626128): Component "server:cordova-lib" starting import
xdk:server (1443248626211): Component "server:cordova-lib" calling init()
xdk:server (1443248626231): Component "server:cordova-lib" threw exception during initialization
xdk:server (1443248626231): Component "server:api-explorer" starting import
xdk:server (1443248626238): Component "server:api-explorer" calling init()
xdk:server (1443248626297): Component "server:api-explorer" finished initialization
xdk:server (1443248626297): Component "server:plugin-listener" starting import
xdk:server (1443248626301): Component "server:plugin-listener" calling init()
xdk:server (1443248626302): Component "server:plugin-listener" finished initialization
server:editor-node (1443248626304): Starting Brackets node process C:\Users\10312\AppData\Local\Intel\XDK2366\bin\node.exe C:\Users\10312\AppData\Local\Intel\XDK2366\bin\node-core
xdk:server (1443248626325): NW Cache is up-to-date.
server:editor-node (1443248626607): Brackets node is running on port 59462
xdk:server (1443248626608): Component "server:editor-node" finished delayed initialization
xdk:server (1443248626608): Unexpected exception while initializing "cordova-lib" (maybe crash): Error: ENOENT, no such file or directory 'C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\components\server\cordova-plugins\cordova-plugin-battery-status\plugin.xml'
Error: ENOENT, no such file or directory 'C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\components\server\cordova-plugins\cordova-plugin-battery-status\plugin.xml'
at Error (native)
at Object.fs.openSync (fs.js:500:18)
at Object.fs.readFileSync (fs.js:352:15)
at parseElementtreeSync (C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\components\server\cordova-lib\cordova-lib\src\cordova\config.js:129:23)
at Function.config.readBuiltinPlugins (C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\components\server\cordova-lib\cordova-lib\src\cordova\config.js:142:17)
at Object.exports.init (C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\components\server\cordova-lib\cordova-lib\cordova-lib.js:167:20)
at loadComponentsNode (C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\core-modules\private\main.js:17:2476)
at initServer (C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\core-modules\private\main.js:17:1356)
at C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\core-modules\private\main.js:17:14239
at _fulfilled (C:\Users\10312\AppData\Local\Intel\XDK2366\xdk\node_modules\q\q.js:797:54)
xdk:server (1443248626609): Error in common initialization
xdk:server (1443248626610): Writing an error to the server data file: [object Object]
xdk:server (1443248626612): Wrote server data to "C:\Users\10312\AppData\Local\XDK\server-data.txt"
xdk:client (1443248626634): Server data file has an error description
[Log closed from xdk:client]

@Mour, I need more

Anusha_M_Intel1 — Mon, 28 Sep 2015 17:55:00 GMT

@Mour, I need more information to help you better.

1. At which point did you get this log?

2. Are you trying to install both versions (2366 and 2496) in your system (or) to completely uninstall 2496 and only keep 2366?

3. When you open your 2366 installed folder in AppData - most probably C:\Users\10312\AppData\Local\XDK. In 'XDK' are there two folders - bin and xdk? If one folder is missing, run your installer again and choose to repair.

the best thing is to

MATRIX_R_ — Tue, 06 Oct 2015 13:06:42 GMT

the best thing is to uniinstall the old

delete all files in data/local/intel

donwload the lastest / install the lastest intel xdk

@Amr - I think you are asking

Pamela_H_Intel — Fri, 06 Nov 2015 18:12:34 GMT

@Amr - I think you are asking why the UI of the most recent XDK is different from the XDK UI shown in the sample and tutorial videos.

You may have noticed that we release a new XDK version every 6-8 weeks. The video tutorials are made with the current version of XDK, but then time passes. There are good videos that were made 6 months - a year ago that are still useful, but then, of course, the video UI will be different from the current UI.

If this is not what you asked, then please clarfy.

Pamela

Amr,

Pamela_H_Intel — Tue, 10 Nov 2015 20:44:00 GMT

Amr,

I see. Well, it is possible that you saw a video with one of XDK's "sister" products. We have 3 versions of XDK.

The classic (or mainstream) version, which today upgraded to v.2673 and is the "regular" version..
The IoT version is what you would use if you want to control hardware.
And the newest - introduced this past summer - is XDK-EA version. That is Early Release. It is the beta version that we have tested and want feedback from developers before implementing new features or processes in the mainstream version. This is for those who want to see what's coming and offer suggestions as to what could be changed to make things more useful. Of course we always like suggestions and feedback, but this beta version just gives us one more level of confidence that developers are going to be successful with the next release before we release it.

So, if it wasn't an older version, then maybe you saw one of the other two editions.

Pamela

please any one send me the

irfan_u_ — Sun, 22 Nov 2015 05:42:58 GMT

please any one send me the link of admob plugin for construct 2 or send link on my email please irfan8099836290@gmail.com..i have everything totally gave developed game but no admob plugin..i cant use new one i cant purchase it please help e