Community
cancel
Showing results for 
Search instead for 
Did you mean: 
PaulF_IntelCorp
Employee
1,920 Views

[RETIRED] Intel XDK

Development and support for the Intel XDK has ceased.

The Intel® XDK is no longer being developed or updated for new operating systems and devices. You may continue to use the final version of Intel XDK (version 3987).

All product support is now provided by the Intel XDK community. The Intel XDK forum will no longer be actively monitored by Intel support personnel. Support for Cordova* and PhoneGap* HTML5 applications (the web app format created by the Intel XDK) can be found under the "Cordova" tag in the StackOverflow self-help forums.

The following articles may be helpful during your transition to other HTML5 web app and Node JavaScript IoT development tools:

The Intel XDK release notes contain many details and links regarding alternatives to those Intel XDK features that were retired in prior releases of the product.

If you are building IoT applications, please check out Intel® System Studio and Arduino Create*.

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

Summary of the 3983 & 3987 releases (update to 3987 if you are using 3983):

This release improves the export to PhoneGap Build and Cordova CLI feature and retires the Intel XDK online build system:

  • The 3987 hotfix corrects an issue with a malformed <platform> tag in the exported config.xml file.
  • Certificate management dialogs now properly indicate there is no support for creation and import of build certs.
  • Added support to export Cordova CLI 6.5 and Crosswalk 23 options for use with PhoneGap Build and Cordova CLI.
  • All mobile app samples and templates have been updated to reflect retirement of the Crosswalk library.
  • The Intel XDK online build system has been retired, as previously announced.

See the Intel XDK release notes for full bug-fix details and for a list of known issues.

IMPORTANT: Support for creating new App Designer projects has been retired. Existing App Designer projects can still be accessed and edited within the Intel XDK; however, there is no further technical support for the App Designer editor or for applications created using App Designer and there will be no bug fixes for that tool. Additionally, our product and engineering management team has decided there will be no open source release of the App Designer editor.

IMPORTANT: As of July 10, 2017, the Intel XDK cloud-based build servers has been retired. The build system is 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 can still be used to push your app to App Preview for on-device testing. Please see the new Cordova Build Package tile on the Build tab for alternatives to using the now retired cloud-based Cordova build system.

IMPORTANT: In February, 2017, the Crosswalk Project was 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.

If you experience this error message (or similar) during an automated update:

Screen Shot 2017-05-17 at 14.20.24 .png

Download the installer directly from the links below. Be sure to exit the Intel XDK before you run the installer.

If you are having trouble downloading the Intel XDK installation package from http://xdk.intel.com (either due to failed downloads or timeouts), you can download the files directly from the links at: https://software.intel.com/en-us/xdk/faq

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

Summary of the 3977 release:

This release resolves several issues that were introduced by the 3900 and 3972 releases:

  • Regressions in the built-in Brackets editor.
  • App Name field (from the Build Settings) is now correct in the <name> tag within the exported config.xml file.
  • The "legacy conversion" and other cert management dialogs were hidden in the dialog input fields.

See the Intel XDK release notes for full bug-fix details and for a list of known issues.

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

Summary of the 3972 release:

This release retires several features that were previously announced as deprecated, eliminates the requirement to register before using the Intel XDK and fixes several minor bugs:

  • The Linux and Mac OSX version of the Intel XDK would sometimes hang when no network connection was available.
  • The Cordova Build Package tile incorrectly reported an error when build credentials were not provided in the Build Settings.
  • The Bower "auto sync" state now defaults to "no" for all new projects.
  • You are no longer required to register for an Intel XDK account when installing and starting the Intel XDK for the very first time.
  • The Cordova Build Package tile is now usable when the Intel XDK does not have a network connection.
  • The Publish tab has been retired.
  • The alert(), confirm() and other "modal dialogs" now work on the Simulate tab.
  • A "keep-alive" feature was added to minimize lost IoT connection problems.
  • Mobile app templates and samples that depend on App Designer or App Framework have been retired.

See the Intel XDK release notes for full bug-fix details and for a list of known issues.

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

Summary of the 3922 release:

This is a "hotfix" release that addresses multiple issues encountered with the 3900 release, especially:

  • Problems with Intel XDK account login and registration have been resolved.
  • Fixed issues with selecting icons and splash screens.
  • Improved compatibility of the Cordova Build Package with PhoneGap Build.
  • Resolved editor shortcut key problems encountered on Apple OSX systems.
  • Fixed multiple crash issues, especially associated with App Designer, the Simulate tab and the Projects tab.
  • Updated the underlying Node-Webkit runtime (0.21.3).
  • Simulate tab is now based on Chromium 57 (due to the NW update).

See the Intel XDK release notes for full bug-fix details and for a list of known issues.

Significant changes as part of the 3900 release, and included in the 3922 hotfix, include:

  • 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 the 3900/3922 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.

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

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.

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

Versions of the Intel XDK released prior to August 2016 (3400 and older) no longer support the Build tab, Test tab and Intel App Preview. This change was necessary to improve the security and performance of our Intel XDK cloud-based build system. If you are currently running version 3400 or older you must upgrade your copy of the Intel XDK!!

Tags (2)
0 Kudos
65 Replies
chuju_l_
Beginner
287 Views

HI, Thanks for the reply, and after 2 day's struggle, here is the found out : The config.xml exported by XDK , <allow-navigation> part is inside the <platform>, it looks like below :

<platform name="ios" >
  <allow-navigation href='*youtube*'/>
</platform>

 but this is no use in Phonegap build, there is no this <allow-navigation> line generated in config.xml in the PhoneGap built ipa. No youtube iframe can be loaded.

but if <allow-navigation> line is moved to outside the <platform>.

<allow-navigation href='*youtube*'/>
<platform name="ios" >
 .....
</platform>


then Youtube iframe is working ...

I can't find doc if <allow-navigation> must be placed outside of <platform> ? it used to working fine built by XDK.
or it is a bug of Phonegap build? or just because PGB's different interpret from XDK build ?

Thanks ~

PaulF_IntelCorp
Employee
287 Views

chuju l. wrote:

oops, there is no <em></em> in the config.xml, it's a copy mistake. Thanks for the reply, but I put the <allow-navigation href="...."/> in intelxdk.config.additions.xml file without surrounding platform tags, it did not appear in the config.xml of the zip file.  <allow-navigation> tag appear in config.xml  only when it's surrounded by platform tags in intelxdk.config.additions.xml.

Other tags like<preference name=... /> without surrounding platform tags show up normally in config.xml,  this <allow-navigation> tag is so tricky ....

I just did a test and confirmed what you say. Putting any of those inside the intelxdk.config.additions.xml file does not result in them being emitted in the exported config.xml file. :-(

chuju l. wrote:

Now I just unzip the XDK exported file to edit config.xml and zip again, but if I can edit in intelxdk.config.additions.xml  like you said will be more handy.... Thank you very much.

I've got an external Node.js script that might work better for this situation. You can find it here > https://github.com/xmnboy/xdk-to-cli < Let me know if that works for you.

Javier_del_A_
Beginner
287 Views

Good morning, Paul. How was everything there?

I wanted to ask you something, see if you can help me as always :)

The operation of the Google Play algorithm has changed a lot and is giving priority in the rankings to apps that meet certain new criteria, such as:

- Appropriate Use of API 23 + and Request for Permissions

 (https://developer.android.com/training/permissions/requesting.html)

- Use of the new security system

(https://developer.android.com/training/best-security.html)


The truth is that I'm a little lost and scared, because all the apps that do not meet these new criteria ... it's as if they did not exist, it takes them out of the Rankings. This can be a big problem for all developers who ignore the new changes.


In my case I developed the apps with an engine called Construct2 and then switched to Intel XDK to compile.

- Would you tell me how I can implement the new permit request system when we compile?

You have to know that the permissions are divided into two groups. 1. Normal permissions 2. Risk permissions

If a permit is normal it must be configured in a specific way and if a permit is considered as a risk permit, it must be configured in a different way.

- Could you advise us on new security systems if we have to implement some additional features?

I hope you can help us, it is a very important issue for everyone, because if we do not update the apps soon this business could become a catastrophe for developers.

Thank you very much Paul

PaulF_IntelCorp
Employee
287 Views

Hello Javier,

There is no easy answer to your questions, and I am not thoroughly versed in all the intricacies associated with this change to the Android permission granting policy, but I think it can be summarized as such:

  • If you set your "Target Android API" level to 23 (which corresponds to Android 6.0) AND you submit your app to the Google store you will NOT be able to submit your app with a lower target API at a later time, once you choose to target API 23 you must continue to update your app with API 23 or higher. If you want to target a lower API level with your app the only option will be to create a new version of your app with a different App ID.
     
  • Why is the above statement important? Because of this statement in the Android document you referenced: If the device is running Android 5.1 or lower, or your app's target SDK is 22 or lower: If you list a dangerous permission in your manifest, the user has to grant the permission when they install the app; if they do not grant the permission, the system does not install the app at all.
     
  • What does the above statement mean? The easiest way to deal with this change in the handling of permissions is to set the "Target Android API" level to 22 or less (we continue to recommend that you "target" API level 21, which corresponds to Android version 5.0).
     
  • Why do we recommend you "target" API level 21? Because it means you'll continue to get the "old" permission behavior for your app.

However, at some point I would expect Google to close this "loophole" that allows apps targeted with API level 22 and lower to continue to be installed and use the older method of granting permissions at install time. I would expect them first to limit the use of the "old permission behavior" to updates to existing apps that are already in the store and ultimately I would expect them to require that all new apps must target API level 23 or higher. Per your statement, it sounds like they are currently giving some sort of search priority to apps that target API level 23 and higher. I would expect the restrictions to become tighter with time.

Javier del A. wrote:

- Would you tell me how I can implement the new permit request system when we compile?

- If a permit is normal it must be configured in a specific way and if a permit is considered as a risk permit, it must be configured in a different way. Could you advise us on new security systems if we have to implement some additional features?

As I said earlier, I am not intimately familiar with all the changes that are required to work with an app that is targeting API level 23 (or higher), so my advice is a guideline, not a solution.

  • In the simplest case, dealing with this new Android permission behavior can be handled by the Cordova plugin(s) you are using that require access to the "risky" permissions (what the Android development pages refer to as "dangerous" permissions). These are permissions like access to contacts, location, sending text messages, etc.
     
  • Some of the drawbacks to this "simplest solution" include: 1) a generic handling of the error (e.g., no way for you to provide a custom message regarding why your app needs the permissions) and 2) likely limited information provided by the plugin when permission grants fail. I'm sure there are many other drawbacks.
     
  • Dealing with apps that target API level 23 means that you MUST be sure that those Cordova plugins you use with your app that require access to "dangerous permissions" are using the new permissions APIs and are dealing with the possible permission responses correctly. In other words, if your app targets API level 23 and you include a Cordova plugin that requires access to a dangerous permission, but that plugin DOES NOT respond properly or ignores the new permission APIs, your app's attempts to utilize that plugin's APIs will likely fail.
     
  • What does the above mean? If you are going to target API level 23 you MUST insure that the plugins you are using that require access to "dangerous permissions" are written to deal with the possibility of a "no permission granted" response AND that your app will also gracefully behave if the permission is not granted by the user.

I hope this gives you some guidelines regarding how to proceed. Note that the core Cordova plugins started supporting API level 23 with the Cordova 5.x release. We recommend that you use Cordova 6.5, which means the CORE plugins that "match" that release do include support for API 23 permissions APIs. That does not necessarily mean that they will always respond to a "no permission granted" in a way that meets the needs of your app, but they will work properly in an app that is built to target API level 23. See this doc page for some additional details > https://cordova.apache.org/docs/en/latest/guide/platforms/android/upgrade.html < and help with this issue.

The hard part is understanding which third-party Cordova plugins (that is, non-CORE plugins) you use now are properly written for use with API level 23, and whether or not you can get the developers of those plugins to update them appropriately.

Javier_del_A_
Beginner
289 Views

ty very much Paul

Alejandro_S_1
Beginner
289 Views

Que tal muy buenas, pues solo con la duda de como se construye el apk en esta versión (3987) en comparación a las anteriores que el proceso era mas simple y en linea

Gracias de antemano por el apoyo y gran servicio que brinda Intel y su capital humano 

PaulF_IntelCorp
Employee
289 Views

Alejandro S. wrote:

That is very good, because only with the doubt of how the apk is built in this version (3987) in comparison to the previous ones that the process was simpler and in line

Thanks in advance for the support and great service provided by Intel and its human capital

The now retired online XDK build system was based directly on Cordova, as is the PhoneGap Build system. So the results from using any of the three are comparable. For complete control over the build process you should use Cordova CLI. If you want to use an online build system you should use PhoneGap Build.

Javier_del_A_
Beginner
289 Views

Hello everyone.
I wanted to share some evidence that I have done about the new permit system in APIS 23+

At the moment I do not know how to implement the new permissions system as google wants us to insert it.

But one solution is:

- Compile for APIS 22- and so you can make use of permissions as always.
- If we want to compile in APIS 23 + The only solution I find is to remove the dangerous permissions. This limits us greatly, since we will not be able to use many functions, but it is a temporary solution.

(I hope this helps many)

I wanted to ask you something Paul.

I am reviewing the Errors and ANRS in the console of Google Play, and I do not know why this is due and if there is a solution to fix it.
It is quite worrying since there are many errors of this type.

Thank you very much Paul

java.lang.RuntimeException:
at org.xwalk.core.XWalkView.onTouchEvent (XWalkView.java:1689)
at android.view.View.dispatchTouchEvent (View.java:7716)
at android.view.ViewGroup.dispatchTransformedTouchEvent (ViewGroup.java:2210)
at android.view.ViewGroup.dispatchTouchEvent (ViewGroup.java:1945)
at android.view.ViewGroup.dispatchTransformedTouchEvent (ViewGroup.java:2216)
at android.view.ViewGroup.dispatchTouchEvent (ViewGroup.java:1917)
at android.view.ViewGroup.dispatchTransformedTouchEvent (ViewGroup.java:2216)
at android.view.ViewGroup.dispatchTouchEvent (ViewGroup.java:1917)
at android.view.ViewGroup.dispatchTransformedTouchEvent (ViewGroup.java:2216)
at android.view.ViewGroup.dispatchTouchEvent (ViewGroup.java:1917)
at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent (PhoneWindow.java:2108)
at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent (PhoneWindow.java:1542)
at android.app.Activity.dispatchTouchEvent (Activity.java:2482)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent (PhoneWindow.java:2056)
at android.view.View.dispatchPointerEvent (View.java:7896)
at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent (ViewRootImpl.java:4011)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess (ViewRootImpl.java:3890)
at android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:3416)
at android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:3466)
at android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:3435)
at android.view.ViewRootImpl$AsyncInputStage.forward (ViewRootImpl.java:3542)
at android.view.ViewRootImpl$InputStage.apply (ViewRootImpl.java:3443)
at android.view.ViewRootImpl$AsyncInputStage.apply (ViewRootImpl.java:3599)
at android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:3416)
at android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:3466)
at android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:3435)
at android.view.ViewRootImpl$InputStage.apply (ViewRootImpl.java:3443)
at android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:3416)
at android.view.ViewRootImpl.deliverInputEvent (ViewRootImpl.java:5671)
at android.view.ViewRootImpl.doProcessInputEvents (ViewRootImpl.java:5650)
at android.view.ViewRootImpl.enqueueInputEvent (ViewRootImpl.java:5621)
at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent (ViewRootImpl.java:5759)
at android.view.InputEventReceiver.dispatchInputEvent (InputEventReceiver.java:194)
at android.os.MessageQueue.nativePollOnce (Native Method)
at android.os.MessageQueue.next (MessageQueue.java:138)
at android.os.Looper.loop (Looper.java:123)
at android.app.ActivityThread.main (ActivityThread.java:5372)
at java.lang.reflect.Method.invokeNative (Native Method)
at java.lang.reflect.Method.invoke (Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:970)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:786)
at dalvik.system.NativeStart.main (Native Method)

 

PaulF_IntelCorp
Employee
289 Views

Javier,

It's hard to say if what you are seeing is something to be concerned about. It looks like there might be a slight mismatch between the Crosswalk library and the underlying Android native library. This could be caused by specifying a target API level that is in appropriate for the Crosswalk library. I recommend a target of API 21 for the latest version of the Crosswalk library. For earlier versions I recommend using API 19 as the target.

If you build your app without Crosswalk, do you still see these errors?

Paul

Fabian_S_
Beginner
289 Views

Hi,

Now I have the XDK 3987 version.
I need to generate an APK file and I am using the same developer certificates that I used before with other applications and it always worked.

When I go to the "BUILD" tab, I only select for Android, then click on "Create Package". Save a zip with all project files but no APK file. Then it shows the following message: "Wornings and error messages included in the config.xml file (inside the exported Cordova build package)"

In the config.xml I can not find any error.

I've also tried with "Cordova CLI Version 5.4.1 and 6.2.0" and it does not work either.

What could be happening?

PaulF_IntelCorp
Employee
289 Views

The XDK build system has been retired. Please read this article > https://software.intel.com/en-us/xdk/article/export-your-intel-xdk-app-to-phonegap-build-or-cordova-cli < for details on how to use PhoneGap Build or Cordova CLI to build your app with those services and see the release notes for additional details > https://software.intel.com/en-us/xdk/docs/release-notes-information-intel-xdk

If there are errors or warnings inside your config.xml file they will be in the form of comments in that file providing recommendations. We no longer produce an APK file, due to the retirement of the build system.

Honda20
Beginner
289 Views

Hi Paul Is the create and export package going to be available or going to retire on 2018 "Creat and Export Your Mobile App to Adobe PhoneGap Build* or Apache Cordova* Software" Regards Honda20
PaulF_IntelCorp
Employee
289 Views

That feature is built into the client app that you run on your desktop and does not rely on the backend to operate. Since we will not be updating the client app (version 3987) it would be wise to learn how to create your config.xml by hand for long term development, because Cordova continues to evolve and improve. So over time the config.xml that is generated by 3987 will not support newer features that are added to Cordova and PhoneGap, but it should be useful for quite some time and certainly is useful as a starting point for generating your config.xml file by hand.

Honda20
Beginner
289 Views

Hi Paul 8 hours ago the simulate preview tab iin Xdk s not showing just white screen and when I exported to zip and run the build in phonegap and launched th app it just white screen. Is the issue from your end? Honda
PaulF_IntelCorp
Employee
289 Views

I doubt it. If you're not seeing anything in the Simulate tab and you're also not seeing anything in the built app I suspect it is something in your app. Probably something that is causing it to hang on startup.

Honda20
Beginner
289 Views

I see. I will look into it when I get home. Another question regarding the final Xdk build. Going forward will the Xdk download build always be available for Mac, just in case when I purchase new Mac machine sometime next year I need a link where I can download the Xdk for Mac. Honda
PaulF_IntelCorp
Employee
289 Views

All three installers (windows, mac and linux) are currently available here > https://software.intel.com/en-us/xdk/faq < but I have no idea how long they will remain there, so I recommend that you download all three if want them, just in case those downloads disappear. They are not scheduled to disappear when the backend is shutdown at the end of January, but I have no idea how long those downloads will continue to be available after January.

Honda20
Beginner
289 Views

Thanks Paul. I am trying to change the background color of the header bar (attached). I could not find any reference. How do we change this color on Phonegap? This color appear when viewing from multi tab view. Regards Honda
Honda20
Beginner
180 Views

Hi Paul

I couldn't find the download link to the latest version of XDK.

Can you please post the link.

Thanks

Honda

PaulF_IntelCorp
Employee
180 Views

Honda20 wrote:

I couldn't find the download link to the latest version of XDK. Can you please post the link.

Please see my previous post which contains a link to the page with the installers that you can download.

Regarding your questions about header colors, I recommend you search the Cordova tag on StackOverflow for help with Cordova programming issues.

The XDK creates a Cordova (aka PhoneGap) app, nothing more. The XDK is simply a convenient collection of an open-source HTML5 friendly editor, a Cordova plugin management tool (based on the open-source Cordova CLI), an open-source Cordova simulation tool and an export mechanism that creates a standard Cordova config.xml build file. The XDK does not include a runtime environment or compiler nor does it control how things appear on the device; all of that is a function of the underlying Cordova framework, the device and OS you are running your app on, the webview on that device and the open-source Cordova plugins you choose to use and how you choose to write your app.

Leonardo_S_
Beginner
180 Views

When I try to download the 3987 version, a message saying "access denied" is shown. How do I get access?

Reply