Software Archive
Read-only legacy content
17061 Discussions

Stuck after updating v2366 -> v2496

Developer_A_1
Beginner
708 Views

Just updated from v2366 to v2496. Original project is asked to be converted, but there are many errors.

First some "process.exit()" errors on screen, then restarting XDK a request to upgrade plugins and some errors we cannot state because the window has been closed too soon.

Now trying again to OPEN the previous XDK we have a "ENOEN, no such file or directory"... error. Now we're stuck with 

 

0 Kudos
6 Replies
Developer_A_1
Beginner
708 Views

...trying to remove the plugin "intel.xdk.device" manually from the ".xdk" file brings this instead:

 

0 Kudos
Pamela_H_Intel
Moderator
708 Views

Do you have your projects stored on the same drive as your XDK application? 

See: https://software.intel.com/en-us/forums/intel-xdk/topic/594199#comment-1841270

Engineering is aware of this and is working on it.

 

0 Kudos
Developer_A_1
Beginner
708 Views

Pamela H. (Intel) wrote:
Do you have your projects stored on the same drive as your XDK application?

See: https://software.intel.com/en-us/forums/intel-xdk/topic/594199#comment-1...

...reference seems to be about Win: we're using a Lnx platform and anyway they're on different mount point (namely an /opt/... folder and a different /home/... for data), so maybe THIS is the problem (?)

Pamela H. (Intel) wrote:
Engineering is aware of this and is working on it.

Thank you for your job... we've downgraded back to previous version and using it 'til next upgrade, meanwhile :)

0 Kudos
Pamela_H_Intel
Moderator
708 Views

So, are your project and the XDK application stored on different drives?

0 Kudos
Developer_A_1
Beginner
708 Views

well... we could say "yes" considering different mounting points as different drives (the latter term having many meanings depending on the context :))

0 Kudos
Pamela_H_Intel
Moderator
708 Views

Being in different directories should not be a problem as long as they are physically on the same drive.

But if you are happy with 2366 (other than the much too frequent upgrade messages - we have requested these be minimized), then it may be best to use that temporarily. We are working on several issues, primarily surrounding changes in Cordova and expect to have a new XDK version out very soon.

0 Kudos
Reply