FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your
profile.
If I add App Security API plugin in build settings in 2323 version of XDK, the crosswalk app in android while opening, it alerts "Unfortunately, App has stopped".
I thought, there may be problems in my code, but I tried creating a empty app just with this plugin, still I am getting the same error.
Yes, I am installing x86 apk to my intel ASUS phone. It installed , but while opening, it prompts, "the app has stopped unexpectedly".
But if I remove App security API.build it and install it, I dont get any problems. I tried with an empty app with just this plugin, it is giving this problem. I am confused.
I just built an very simple crosswalk build and installed the ARM version on my samsung s4. It installed/launched with no issues with the Security API included.
Try installing the ARM version from the attached zip. If you are still having issues, attach the zip you get from the build system to your post.
Actually my phone requires x86 version, but neither versions worked, I have attached a simple app with APP security API included. See if you can find out anything wrong in what I did.
@Sam -- I tried the examples you provided and the x86 fails on my Asus x86 device, but the ARM works on my Samsung S3. Can you attach a copy of the <project-name>.xdk file from the root of the project directory AND the intelxdk.config.crosswalk.xml files from the project you used to build this example? I want to see which version of the App Security API plugin is being included.
After you post the files I requested, can you try another experiment -- build a single app using the "shared" option in the "Crosswalk Runtime" field on the Projects tab (in the Build Settings). See if that APK will run:
I'm sorry, I meant for you to add the security plugin and build it and install it to confirm that this simple app results in a failure. Then send me the two files above. I don't see the security plugin being used in the files you sent me, the app is including the device, splashscreen and inAppBrowser plugins...
I was a mistake from me that I attached wrong files, now I have attached correct .xdk file and intelxdk.config.crosswalk.xml file herewith. Please review them.
Nothing odd in those files. I tried to reproduce this with a simple project of my own and I cannot create a build that fails. Can you ZIP the entire project directory for a project that causes this and attach it to a post on this thread. There must be something else going on in the project that is causing this.
When I build that app, exactly as you have given it to me, no changes to anything, and install and run it on an x86 and an ARM device it works, there is no crash. I've attached the builds that I installed. Please let me know if these crash on your devices.
I will have access to some other android device in another 2 hours, so I will update you in 2 hours. But my concern is, previously it was working before switching to 2323 build of XDK.
Make sure you have removed any existing installs of the application before you install the copies I gave you, to be sure the new version actually got installed. I have seen situations where installing over the top of an existing app fails, but not in an obvious way. So UNINSTALL the existing test apps on your device and then install the x86 version I sent to you.
The version of the XDK does not change how the build works, since the build server is in the cloud and is not tied to the version of the XDK.
Could you please also try installing the EA version of the XDK and perform the same test with a project built from that version. In that case the build will be affected because the plugins are provided by the XDK rather than retrieved by the build system, otherwise the builds are the same. See these posts for details:
