Really disappointed with the - Page 4

PaulF_IntelCorp · ‎03-14-2017

Summary of the 3900 release:

With this release of the Intel XDK the Intel XDK cloud-based build servers and the Publish tab are deprecated and will be retired at the end of June, 2017. Until then, expect no further upgrades and limited support for these features. We have also addressed several bugs and issues found in prior releases. See the Intel XDK release notes for full details.

Significant changes as part of this release include:

Updated the underlying Node-Webkit runtime (0.18.9).
Simulate tab is now based on Chromium 54 (due to the NW update).
The built-in Brackets editor has been updated to the latest version.
Samples have been updated to support Intel® Gateway IoT development platforms.
Improved IoT daemon installation, especially for newer Intel IoT platforms.
Export to Cordova CLI or PhoneGap Build feature.

Features deprecated with this release:

The Build tab's cloud-based Cordova build system will be retired at the end of June, 2017.
The Publish tab will also be retired at the end of June, 2017.

When the Intel XDK cloud-based build system is retired itwill no longer be available for use with any version of the Intel XDK. Your mobile app projects will still be recognized as Intel XDK mobile app projects and will continue to work within the Simulate tab. Additionally, the Test tab is still present and can still be used to push your app to App Preview for on-device testing. Please see the new a ref="/en-us/xdk/docs/build-xdk-app-with-phonegap-cordova-cli">Cordova Build Package tile on the Build tab for an alternative to using the now deprecated on-line Cordova build system.

IMPORTANT: As of February, 2017, the Crosswalk Project has been retired. Crosswalk 23 was the last version of the Crosswalk library produced by the Crosswalk Project team. You can continue to build with the Crosswalk library using Cordova CLI or PhoneGap Build, but no further updates to the Crosswalk library will occur beyond version 23 (FYI: the Crosswalk 23 library for Android is based on the Chromium 53 runtime release).

Our automatic updater will notify existing Intel XDK users when the update is available within the Intel XDK. Updates will be released to all users within 24 hours. If you would like the update sooner, you can download it directly from xdk.intel.com and install it manually.

Important note about Intel XDK versions 2893 and older!

Versions of the Intel XDK released prior to March 2016 (2893 and older) can no longer use the Build tab, the Test tab or App Preview and can no longer be used to create custom debug modules for use with the Debug and Profile tabs. This change was necessary to improve the security and performance of our Intel XDK cloud-based build system. If you are currently running version 2893 or older, of the Intel XDK, you must upgrade to the latest version of the Intel XDK!!

------------------------------------------------

Summary of the 3759 release:

With this release of the Intel XDK we officially retired several features that were deprecated in previous product releases. We have also addressed several bugs and issues found in prior releases. See the Intel XDK release notes for full details.

New features added with this release include:

Web Services Explorer supports IoT projects
Brackets Live Preview added to Develop tab
Samples added to support the Intel® Joule™ IoT development board
Improved IoT daemon installation, especially for Intel Joule platforms

Features retired with this release:

The Debug tab has been retired.
The hosted weinre debug server used by the Test tab has been retired.
The Live Development Pane in the Develop tab has been retired.
The Game Asset Manager and related samples and templates have been retired.
Samples and templates that are not useful to developing IoT companion apps have been retired.
Featured Cordova plugins that are not useful to developing IoT companion apps have been removed.

IMPORTANT: Retirement means no longer available for use with any version of the Intel XDK. Your mobile app projects will still be recognized as Intel XDK mobile app projects and will continue to build (using the Build tab) and work within the Simulate tab. Additionally, the Test tab is still present and can still be used to push your app to App Preview for on-device testing.

Alternatives to using the Debug tab, the hosted weinre server and the Live Development pane can be found in the Intel XDK release notes.

------------------------------------------------

Summary of the 3641 update:

This Intel XDK release addresses installation issues introduced in the prior release. See the release notes for details.

------------------------------------------------

Summary of the 3619 release:

This Intel XDK release addresses several bugs and issues found in prior releases. See the release notes for bug fix details. New features added with this release include:

Keyword-based filters for new project templates and samples
New Linux* and Apple* OSX* installers
New IoT project samples using Microsoft* Azure*

Feature deprecations with this release:

Debug tab has been deprecated and will be removed in a future release.
The hosted weinre debug server used by the Test tab has been deprecated and will be removed in a future release.
The Live Development Pane in the Develop tab has been deprecated and will be removed in a future release.
The Framework7 and Ionic UI frameworks have been deprecated from App Designer and will be removed in a future release.

IMPORTANT: With this release, the Debug tab, the hosted weinre server associated with the Test tab, and the Live Development pane located on the Develop tab have been deprecated and will be retired in the near future. When these features are retired you will no longer be able to use them with any version of the Intel XDK. Your project will continue to be recognized as an Intel XDK HTML5 mobile app project and it will continue to build (using the Build tab) and work within the Simulate tab. Follow the links embedded in each of the deprecated features listed above for more details and pointers to free open-source alternatives to these deprecated features.

Why is the Debug tab being deprecated and removed from the Intel XDK?

In addition to our previously announced deprecation of support for App Framework, within the App Designer UI editor, we are also deprecating support for the use of the Framework7 and Ionic UI frameworks. You can still use these frameworks outside of the App Designer UI editor, as you have always been able to do with any UI framework. Existing projects that are using deprecated UI frameworks will continue to be recognized by App Designer and can be edited within the App Designer UI editor; however, there will be no bug fixes for deprecated frameworks and, once those frameworks are retired, the App Designer UI editor will no longer recognize those projects.

------------------------------------------------

Summary of the 3522 release:

This Intel XDK release is a hot-fix that addresses several bugs and issues found in the 3491 release:

Crosswalk version 19 is now the default version for newly created projects. This update will warn you of any existing projects using Crosswalk version 18 (or lower). Google does not require that you use Crosswalk 19 (or higher), so this is just a warning, not an error.
Several issues that generated a 'build tab generates ERROR (-7) from "client:upload-manager": Error in zipping package asset files:' error message have been addressed. This primarily impacted Construct2 users who were importing new projects or opening existing projects.
The new Simulate tab did not present the window.screen object correctly. See this forum post for additional details.
Attempting to run some Cordova apps that did not include any plugins would cause the app to crash or generate a 404 error in the Simulate tab. See this forum post for some examples.
Replacing an icon or splash screen with a new file but using the same name for that file would cause an incorrect prompt regarding an invalid resolution. See this forum post for more details.
Intel XDK crashes that resulted in "Error: ENOENT" and "Uncaught TypeError: undefined is not a function" errors when using the Simulate tab.
Use of the <head data-noxhrfix> tag causes the Simulate tab to fail or hang. See this forum post for additional details.
The 750x1334 splash screens (portrait and landscape) have been restored to the iOS Icons and Splash Screens UI.This forum post provides additional details.
A custom require() function was placed into the global namespace by the Simulate tab preventing use of require() within a user app. See this forum thread for additional details.

------------------------------------------------

Summary of the 3491 release:

This very important release merges the Intel XDK IoT Edition and the Intel XDK Early Access into a single release of the Intel XDK. We are moving in the direction of supporting Internet of Things (IoT) app development. Since mobile devices are part of that equation, we continue our support of the development of hybrid Cordova mobile HTML5 apps. For more details regarding this new direction, please read Joe's blog. a

We have made some significant improvements for both IoT and mobile Cordova app development with this release:

Replacing the Emulate tab with a new Simulate tab.
Added a new Cordova CLI 6.2.0 build option (CLI 5.1.1 has been deprecated).
Moved iOS mobile provisioning files, icons and splash screens to a new "package-assets" folder.
Stability improvements and many bug fixes.

In future releases we will be adding more functionality for IoT app development. We will also be fine-tuning our Cordova mobile app support to align with the needs of IoT app development. As a result, we are deprecating some mobile app development features that are not heavily used or are inconsistent with IoT app development needs.

Feature deprecations and removals with this release:

Profile tab has been removed. Please use the profiling features available in the Chrome Debug Tool (on the Debug tab).
Cordova CLI 5.1.1 has been deprecated and will be removed in our next release, likely in September 2016.
Legacy Windows 8.x build platforms have been deprecated. They are only available using CLI 5.1.1 and 5.4.1. Only Windows 10 UAP builds are supported with CLI 6.2.0. These older Windows 8.x platform builds will be removed in September 2016.
Game Asset Manager, samples and templates have been deprecated and will be removed in a future release.
Legacy Whitelist (Android only) was previously deprecated and is no longer available for new projects.

------------------------------------------------

Summary of fixes in the 3400 release:

This Intel XDK release is a hot-fix that addresses several bugs and issues:

Crashes at startup due to a variety of timeout problems.
Long startup times due to slow or spotty network connections.

------------------------------------------------

Summary of fixes in the 3357 release:

The built-in Brackets editor now includes a new "tab view" making it easier to switch between all of your active source files.
The standard Brackets Extension Manager toolbar is now exposed at the right-hand side of the edit window, where you will find it in a stand-alone install of the Brackets editor.
The Brackets Git Extension is now more easily accessed, via the standard Brackets Extension Manager toolbar (see above).
To minimize crashes due to the Emulate tab, the CDT debug window will automatically close when switching away from the Emulate tab, if you have enabled the "auto-refresh" feature of the Emulate tab (this is the default condition).

------------------------------------------------

Summary of fixes in 3240 hotfix release:

When selecting Apache Cordova* CLI 5.4.1 you were not limited to the minimum target of iOS 8 which resulted in developers attempting to build for unsupported platforms and then building what appear to be non-working apps.
If the index.html project file was not contained in the "www" directory of the project, The Emulator would display a '404: Intel XDK can't find your app' error.
In some cases, if the Publisher Display Name was not populated for a Windows* build, the plugin add and subsequent build for Windows would fail. Validation for requiring the Publisher Display Name has been added.
Corrected an issue where sometimes the plugin manager would not allow a third-party/local plugin to be added to the project.

------------------------------------------------

Summary of new features in 3088/3042:

We no longer support CLI 4.1.2 builds. Projects that use CLI 4.1.2 MUST be updated.
Added Cordova CLI 5.4.1 to the Intel XDK build system. See this FAQ for details.
A new Certificate Management feature allows you to create or import Android certificate keystore files and iOS P12 distribution certificate files.
The Build tab allows you to build your app for multiple targets with a single mouse click.
Android and Android-Crosswalk options have been combined into a single target platform in the Build Settings section of the Projects tab.
Crosswalk support in the Intel XDK is now based on the Crosswalk Webview plugin (AKA "Cordova 4" in Crosswalk docs).
A new Publish tab has been added to assist you with creating and publishing application assets and information to a variety of Android stores.
The Windows and Windows Phone build options have been expanded and significantly updated to include Windows 10 Universal Apps. Please use the CLI 5.4.1 build option for your Windows and Windows Phone builds.
The built-in Brackets editor has been updated to version 1.6 and several new Brackets extensions have been added.
Whitelist settings in the Build Settings section of the Projects tab have been updated.
App Preview has been updated (to version 2.8.0). Check the respective stores to be sure you have the latest version.
Updates to our project file format will require that all projects be "updated" before you can use them with this release.

This release also addresses the Google App Store warning regarding the use of older versions of Cordova-Android. You must migrate your app to our CLI 5.1.1 or CLI 5.4.1 build system to eliminate this warning and to be able to publish apps in the Google App Store after May 9, 2016. Our CLI 5.1.1 build system has been updated to address this issue (see this FAQ for specific details).

Alessandro_S_ · ‎03-16-2017

Hello, I cannot understand:

Now building with Phonegap export I Produce only one .apk, while before I produced 2 apk (x86 and arm). What's happening?

I have a free account on PhoneGap, Can I still update my app into Stores? (Android/iOs)

And finally, My Android app compiled has not launch icon or splashes now. VERY SAD, I need to update my app on the store

Again when I submit to iTunes, the app is discarded with this motivation:

Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data.

Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data.

Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.

Please Help, I know that I still can use Cloud for a while but I want to understand how to set up environment before it's too late.

Thank You

PaulF_IntelCorp · ‎03-16-2017

aykut y. wrote:

Edit: Seems it's an known issue (https://software.intel.com/en-us/xdk/docs/release-notes-information-inte...)

To work around this issue, you can reference your icons and splash screen images using the intelxdk.config.additions.xml file. See this sample intelxdk.config.additions.xml file, which is part of the "hello cordova" demo app, for additional information and an example of how this is done. You must still locate your icon and splash screen images within the "package-assets" folder, to insure they will be included with your build package when submitting to our on-line build system or to PhoneGap Build and Cordova CLI.

With this solution, you'll loose simulate capabilities in xdk app. so waiting a hot fix.

You won't lose any simulate capabilities, the Simulate tab does not do anything with your icons and splash screens, it simply runs your HTML5 stuff inside a dedicated Chromium browser window. You'll only see the icons and splash screens when you build your app. For building whether you reference those files using the additions file or the GUI, you'll get the same results.

PaulF_IntelCorp · ‎03-16-2017

Ernani Torquato wrote:

After the update 3900 I am with the following problem, when opening the simulator the xdk displays a modal that was encountered a problem. Attached the log.

Can you provide a screenshot showing what happens?

PaulF_IntelCorp · ‎03-16-2017

Alessandro S. wrote:

Now building with Phonegap export I Produce only one .apk, while before I produced 2 apk (x86 and arm). What's happening?

I have a free account on PhoneGap, Can I still update my app into Stores? (Android/iOs)

Build for Crosswalk on PhoneGap Build is different than on the XDK. When you choose to build with Crosswalk PhoneGap build will return only a single APK, so the build preferences in the exported config.xml file are set to deliver a "multi-architecture" APK file that contains both the ARM and the x86 Crosswalk libraries (unzip the APK you get from PhoneGap Build and look for the Crosswalk libraries and you'll see what I mean). Thus, you only need to submit a single APK to the store (because it contains both Crosswalk libraries: ARM and x86).

Alessandro S. wrote:

And finally, My Android app compiled has not launch icon or splashes now. VERY SAD, I need to update my app on the store

Sorry, not sure what you mean by this, further details needed to help resolve.

Alessandro S. wrote:

Again when I submit to iTunes, the app is discarded with this motivation:

Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data.

Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data.

Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.

For the plist issues I suggest you search Stack Overflow for something like "phonegap build missing Info.plist key" and you'll probably find the solution you need. This might require doing some editing of the exported config.xml file. You can also put the required PhoneGap build preferences into the intelxdk.config.additions.xml file and then the exported config.xml file will contain those additions.

Alessandro_S_ · ‎03-16-2017

Hello by changing variables in plugins I solved the iOs problem.

It remains that one on Android still not solved:

Attached my config.xml (renamed as .txt) generated by XDK and a screenshot of the content of zip file generated to be imported in PhoneGap (icons and splash are inside package-assets folder).

What's wrong?

Alessandro_S_ · ‎03-16-2017

Well I found the problem (BUG) about missing icons and splashes when I compile to PhoneGap

XDK doesn't keep "density" info that is present in xdk configuration file when creates config.xml

I added density info (just copying from intelxdk.config.addistions.xml) to the config.xml file and icons appear!

Fix this please!

PaulF_IntelCorp · ‎03-16-2017

Alessandro S. wrote:

Hello by changing variables in plugins I solved the iOs problem.

It remains that one on Android still not solved:

Attached my config.xml (renamed as .txt) generated by XDK and a screenshot of the content of zip file generated to be imported in PhoneGap (icons and splash are inside package-assets folder).

What's wrong?

Do you get an APK with icons and splash screens when you build with the XDK? (for comparison).

Alessandro_S_ · ‎03-16-2017

Paul F. (Intel) wrote:

Quote:

Alessandro S. wrote:

Hello by changing variables in plugins I solved the iOs problem.

It remains that one on Android still not solved:

Attached my config.xml (renamed as .txt) generated by XDK and a screenshot of the content of zip file generated to be imported in PhoneGap (icons and splash are inside package-assets folder).

What's wrong?

Do you get an APK with icons and splash screens when you build with the XDK? (for comparison).

yes I found the bug. In config.xml XDK doesn't take density info needed by PhoneGap. I added it manually in config.xml (extract then zipped again) and icons appear!!!

Alessandro_S_ · ‎03-17-2017

and again I notice differences between PhoneGap build and XDK.

In example there is a ugly intermediate screen before splash with title of the window. I found this solution: adding this to config.xml

<gap:config-file platform="android" parent="/manifest">
    <application android:theme="@android:style/Theme.NoTitleBar"></application>
</gap:config-file>

but phonegap crashes compiling (even without gap: ), it says: malformed xml, but this snippet is for phonegap config file found on internet

PaulF_IntelCorp · ‎03-17-2017

Alessandro S. wrote:

Quote:

Paul F. (Intel) wrote:
Do you get an APK with icons and splash screens when you build with the XDK? (for comparison).

yes I found the bug. In config.xml XDK doesn't take density info needed by PhoneGap. I added it manually in config.xml (extract then zipped again) and icons appear!!!

Thank you, I have confirmed that this is not working. Despite the fact that Cordova docs say the density is optional, that does not appear to be the case for PhoneGap Buid. :( I have filed a bug report with engineering.

Alessandro_S_ · ‎03-18-2017

Thank you Paul, do You have idea for my other question?

Alessandro S. wrote:

and again I notice differences between PhoneGap build and XDK.

In example there is a ugly intermediate screen before splash with title of the window. I found this solution: adding this to config.xml
<gap:config-file platform="android" parent="/manifest">
    <application android:theme="@android:style/Theme.NoTitleBar"></application>
</gap:config-file>
but phonegap crashes compiling (even without gap: ), it says: malformed xml, but this snippet is for phonegap config file found on internet

PaulF_IntelCorp · ‎03-18-2017

Alessandro -- I'm not familiar with those specific PhoneGap Build instructions. I recommend you check their documentation to determine if this is still the right thing to do. Many of those special PhoneGap Build directives no longer apply, since they improved their compatibility with standard Cordova CLI during the past year (2016).

You might also try using the latest version of PhoneGap Build for you builds. You can do that by removing the PhoneGap Build CLI version tag (I don't recall the specific name, but it is pretty obvious) from the config.xml file before you submit to PhoneGap Build.

Alessandro_S_ · ‎03-19-2017

Hello I've tried to compile with latest version (removing cli tag) but while Ios has been complied without errors, android build fails: Build Date: 2017-03-19 09:07:27 +0000 Subproject Path: CordovaLib Configuration on demand is an incubating feature. null org.xwalk:xwalk_core_library:19+ Incremental java compilation is an incubating feature. Download https://repo1.maven.org/maven2/com/pushwoosh/pushwoosh/4.6.3/pushwoosh-4.6.3.pom Download https://repo1.maven.org/maven2/com/pushwoosh/pushwoosh/4.6.3/pushwoosh-4.6.3.aar :preBuild UP-TO-DATE :preReleaseBuild UP-TO-DATE :checkReleaseManifest :preDebugBuild UP-TO-DATE :CordovaLib:preBuild UP-TO-DATE :CordovaLib:preDebugBuild UP-TO-DATE :CordovaLib:checkDebugManifest :CordovaLib:prepareDebugDependencies :CordovaLib:compileDebugAidl :CordovaLib:compileDebugNdk UP-TO-DATE :CordovaLib:compileLint :CordovaLib:copyDebugLint UP-TO-DATE :CordovaLib:mergeDebugShaders :CordovaLib:compileDebugShaders :CordovaLib:generateDebugAssets :CordovaLib:mergeDebugAssets :CordovaLib:mergeDebugProguardFiles :CordovaLib:packageDebugRenderscript UP-TO-DATE :CordovaLib:compileDebugRenderscript :CordovaLib:generateDebugResValues :CordovaLib:generateDebugResources :CordovaLib:packageDebugResources :CordovaLib:processDebugManifest :CordovaLib:generateDebugBuildConfig :CordovaLib:processDebugResources :CordovaLib:generateDebugSources :CordovaLib:incrementalDebugJavaCompilationSafeguard :CordovaLib:compileDebugJavaWithJavac :CordovaLib:compileDebugJavaWithJavac - is not incremental (e.g. outputs have changed, no previous execution, etc.). Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. :CordovaLib:processDebugJavaRes UP-TO-DATE :CordovaLib:transformResourcesWithMergeJavaResForDebug :CordovaLib:transformClassesAndResourcesWithSyncLibJarsForDebug :CordovaLib:mergeDebugJniLibFolders :CordovaLib:transformNative_libsWithMergeJniLibsForDebug :CordovaLib:transformNative_libsWithSyncJniLibsForDebug :CordovaLib:bundleDebug :CordovaLib:preReleaseBuild UP-TO-DATE :CordovaLib:checkReleaseManifest :CordovaLib:prepareReleaseDependencies :CordovaLib:compileReleaseAidl :CordovaLib:compileReleaseNdk UP-TO-DATE :CordovaLib:copyReleaseLint UP-TO-DATE :CordovaLib:mergeReleaseShaders :CordovaLib:compileReleaseShaders :CordovaLib:generateReleaseAssets :CordovaLib:mergeReleaseAssets :CordovaLib:mergeReleaseProguardFiles :CordovaLib:packageReleaseRenderscript UP-TO-DATE :CordovaLib:compileReleaseRenderscript :CordovaLib:generateReleaseResValues :CordovaLib:generateReleaseResources :CordovaLib:packageReleaseResources :CordovaLib:processReleaseManifest :CordovaLib:generateReleaseBuildConfig :CordovaLib:processReleaseResources :CordovaLib:generateReleaseSources :CordovaLib:incrementalReleaseJavaCompilationSafeguard :CordovaLib:compileReleaseJavaWithJavac :CordovaLib:compileReleaseJavaWithJavac - is not incremental (e.g. outputs have changed, no previous execution, etc.). Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. :CordovaLib:processReleaseJavaRes UP-TO-DATE :CordovaLib:transformResourcesWithMergeJavaResForRelease :CordovaLib:transformClassesAndResourcesWithSyncLibJarsForRelease :CordovaLib:mergeReleaseJniLibFolders :CordovaLib:transformNative_libsWithMergeJniLibsForRelease :CordovaLib:transformNative_libsWithSyncJniLibsForRelease :CordovaLib:bundleRelease :prepareBarcodescannerLibrary :prepareComAndroidSupportCardviewV72340Library :prepareComAndroidSupportCustomtabs2340Library :prepareComAndroidSupportSupportCompat2520Library :prepareComAndroidSupportSupportCoreUi2520Library :prepareComAndroidSupportSupportCoreUtils2520Library :prepareComAndroidSupportSupportFragment2520Library :prepareComAndroidSupportSupportMediaCompat2520Library :prepareComAndroidSupportSupportV42520Library :prepareComFacebookAndroidFacebookAndroidSdk4132Library :prepareComGoogleAndroidGmsPlayServicesBase1020Library :prepareComGoogleAndroidGmsPlayServicesBasement1020Library :prepareComGoogleAndroidGmsPlayServicesGcm1020Library :prepareComGoogleAndroidGmsPlayServicesIid1020Library :prepareComGoogleAndroidGmsPlayServicesLocation1020Library :prepareComGoogleAndroidGmsPlayServicesTasks1020Library :prepareComPushwooshPushwoosh463Library :prepareOrgXwalkXwalk_core_library19495145Library :prepareProjectCordovaLibUnspecifiedReleaseLibrary :prepareReleaseDependencies :compileReleaseAidl :compileReleaseRenderscript :generateReleaseBuildConfig :mergeReleaseShaders :compileReleaseShaders :generateReleaseAssets :mergeReleaseAssets :createXwalkCommandLineFileRelease :generateReleaseResValues :generateReleaseResources :mergeReleaseResources :processReleaseManifest :processReleaseResources :generateReleaseSources :incrementalReleaseJavaCompilationSafeguard :compileReleaseJavaWithJavac :compileReleaseJavaWithJavac - is not incremental (e.g. outputs have changed, no previous execution, etc.). /project/src/org/crosswalk/engine/XWalkWebViewEngine.java:55: error: XWalkWebViewEngine is not abstract and does not override abstract method evaluateJavascript(String,ValueCallback) in CordovaWebViewEngine public class XWalkWebViewEngine implements CordovaWebViewEngine { ^ Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. 1 error :compileReleaseJavaWithJavac FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':compileReleaseJavaWithJavac'. > Compilation failed; see the compiler error output for details. * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 7.706 secs Error: /project/gradlew: Command failed with exit code 1 Error output: Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. /project/src/org/crosswalk/engine/XWalkWebViewEngine.java:55: error: XWalkWebViewEngine is not abstract and does not override abstract method evaluateJavascript(String,ValueCallback) in CordovaWebViewEngine public class XWalkWebViewEngine implements CordovaWebViewEngine { ^ Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. 1 error FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':compileReleaseJavaWithJavac'. > Compilation failed; see the compiler error output for details. * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. at ChildProcess.whenDone (/project/cordova/node_modules/cordova-common/src/superspawn.js:169:23) at emitTwo (events.js:106:13) at ChildProcess.emit (events.js:191:7) at maybeClose (internal/child_process.js:877:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

Nick_F_2 · ‎03-19-2017

Really disappointed with the way XDK has gone.

XDK was a very good all inclusive development package and I have some decent Enterprise Apps working that were developed using XDK. I feel that Intel are letting down their core users by stripping out function and moving to IoT. IoT does not help those that have used XDK since the beginning and are now struggling to find a replacement tool that works in the way XDK did.

I can understand the need for change and that is acceptable, however change need to embrace the community that have supported this project from the start and I for one feel bitterly let down.

I can no longer work on previously created projects they just fail to load well. The lack of Debug facilities is a nightmare. Even if I can get it to work the way I want, the development timescale has increased dramatically.

Alessandro_S_ · ‎03-19-2017

Nick I'm disappointed too. I also have a couple of apps downloaded thousands of times by users and now I'm scared about what XDK is doing. I think that XDK will go on working, without building cloud platform, but we will able to use the RAD....at least...I hope it, or we should be let aware clearly by Intel and suggested about how to migrate without pain to some other compatible RAD. I THINK Intel as a serious company.

PaulF_IntelCorp · ‎03-19-2017

Alessandro S. wrote:

Hello I've tried to compile with latest version (removing cli tag) but while Ios has been complied without errors, android build fails:

Build Date: 2017-03-19 09:07:27 +0000
Subproject Path: CordovaLib

... stuff deleted...

Please start a new thread specific to your issue, and please attach detailed build logs as text file attachments using the "Attach Files to Post" link below the forum edit window. It is very difficult to work with long posts like that. Also, is that build log coming from the XDK build system or PhoneGap Build?

PaulF_IntelCorp · ‎03-19-2017

Nick and Alessandro: please read this blog > https://software.intel.com/en-us/blogs/2017/03/03/intel-xdk-february-2017-release-exporting-apps-and-going-all-in-on-iot < for some answers regarding why we are changing the XDK.

Alessandro -- sorry, what do you mean by "RAD"?

Please note that the XDK has always created standard Cordova apps, from the very beginning. So building with PhoneGap Build or Cordova CLI results in the identical output. The process may change, but your ability to keep up with the rapidly changing development tools and to get the most from those tools is dramatically improved.

Alessandro_S_ · ‎03-20-2017

Paul F. (Intel) wrote:

Nick and Alessandro: please read this blog > https://software.intel.com/en-us/blogs/2017/03/03/intel-xdk-february-201... < for some answers regarding why we are changing the XDK.

I've already read that post, and I didn't understand what I have to do. The title is "exporting All-In to IoT" but in the article nothing is specified about it, and it's not clear if XDK as we use will be available in the future even if we should use PhoneGap to compile.

Alessandro_S_ · ‎03-20-2017

Paul F. (Intel) wrote:

Alessandro -- sorry, what do you mean by "RAD"?

RAD I mean Rapid App Development

Alessandro_S_ · ‎03-20-2017

Paul F. (Intel) wrote:

Please start a new thread specific to your issue, and please attach detailed build logs as text file attachments using the "Attach Files to Post" link below the forum edit window. It is very difficult to work with long posts like that. Also, is that build log coming from the XDK build system or PhoneGap Build?

Hello Paul this is my new thread:

https://software.intel.com/en-us/forums/intel-xdk/topic/721012

Nick_F_2 · ‎03-20-2017

Paul F. (Intel) wrote:

Nick and Alessandro: please read this blog > https://software.intel.com/en-us/blogs/2017/03/03/intel-xdk-february-201... < for some answers regarding why we are changing the XDK.

Alessandro -- sorry, what do you mean by "RAD"?

Please note that the XDK has always created standard Cordova apps, from the very beginning. So building with PhoneGap Build or Cordova CLI results in the identical output. The process may change, but your ability to keep up with the rapidly changing development tools and to get the most from those tools is dramatically improved.

Hi Paul

Have read this and understand the methodology, its just clunky and does increase the work flow timescales because of the constant need to export and compile separately. The restrictions on PhoneGap a frustrating. 25 Private apps is nothing when we are developing Enterprise apps for businesses. What ever we pay Adobe we cannot exceed that number. OK we don't have 25 yet, but we will hit that limit at some point.

Our app's are not for the public domain.

Intel XDK Release 3900, March 14, 2017