I try to build a metro-style-app with Javascript and when I run the Windows App Cert Kit (WACK) Certification tool the test always fails on the performance test with the following message:
Following errors were detected when tested the byte code generation:
This package was made available for the development or Authoringmodus. Uninstall the package and reinstall it in the normal way.
I’m using jquery and some jquery-mobile libraries inside my app. Is that the problem? The error doesn’t make sense for me, because it doesn’t say which package I should reinstall. I also try to uninstall the App itself (by right click onto the app) and build it again in the Release-Modus of VS2012, but the WACK tool always prompts this error :(
Find out that the WACK Tool allways shows this error if you don't run Store -> Create App Package and select "No" and press the next button. After that the WACK-Tool is started automatically and it passes the bytecode generation.
First save the all javascript files with encoding utf 8 format with signature
then create the app package
http://msdn.microsoft.com/en-us/library/windows/apps/hh975357.aspx
then if u already install the latest windows app certification kit then u will be able to see run with windows app certification kit button after creating app package .
Related
I am trying to sequence an application in V5.1 that currently works fine in v4.6. I have tried to do the conversion and also do a brand new sequence but on both occasions, when the sequenced app is run it errors with "The program can't start because Vcl50.bpl is missing from your computer. Try reinstalling the program to fix the problem".
This file is installed to 'C:\Windows\System32' when I install the client along with a load of other .bpl files. These files are related to the BDE Administrator that it installs.
If I open the bubble for amendment the application works fine and I can see all the .bpl files in the 'C:\Windows\System32' folder.
I have been trying to use android studio and every time I deploy an app on a device, it gives me an error saying:
Installation failed since the device possibly has stale dexed jars that don't match the current version (dexopt error).
In order to proceed, you have to uninstall the existing application.
I have tried using Build->Clean Project and yet it seems to do no good.
I have also tried deleting the file from /data/local/tmp on device (as my phone is a rooted one), but, all in vain.
If anyone knows a way out, please, please help.
Uninstall the application from the device.
Check the storage space.
Once Restart the mobile and try to install it
I have a hybrid app that was created with WL 6.1 that uses the included dojolib. Currently it is in production for iphone and we are adding the android flavor of it. When running the code from the mobile simulator on the console, both the android and iphone work fine. The ipa file works fine. When I run the hybrid on an android device (Samsung S4), the application throws errors in the log on app startup. I have the "provide dojo libraries" turned off. In the DDMS log I see statements like the following:
09-09 12:47:12.092: E/AndroidProtocolHandler(20324): Unable to open asset URL: file:///android_asset/www/default/dojo/_base/declare.js
09-09 12:47:12.263: E/AndroidProtocolHandler(20324): Unable to open asset URL: file:///android_asset/www/default/dojo/_base/connect.js
09-09 12:47:12.303: E/AndroidProtocolHandler(20324): Unable to open asset URL: file:///android_asset/www/default/dojo/_base/event.js
Looking out in the android project in eclipse, I see those files in the "assets/www/default/dojo/_base" directory. The issue is when I look in the APK file, the "_base" directory is not there. Any help as to understanding why it is missing?
Your application should be using the compiled version of the dojo files, it seem that its not.
i would check
These files : core-web-layer.js and mobile-ui-layer are in your www folder
That the wlCommonInit function includes below:
function wlCommonInit() {
require([ "layers/core-web-layer", "layers/mobile-ui-layer" ], dojoInit);
}
I've also found an alternative way to get around the android packaging bug. As I mentioned earlier one way is to use the DojoBuildFactory to create a new layer that would have the files imbedded in them. This is the same process that WL uses to create the core-web-layer and mobile-ui-layer. I have a team working on this, but the documentation is ... scant and it is a time consuming process.
While they were doing that, I found what I think is a cleaner way of addressing the issue. Effectively open up an unsigned apk, insert the files, and then sign the APK. Worked like a charm. Here are the steps I used:
Build from working pointing to the correct worklight server and with the provide missing dojo libraries turned off
Export as Android project as an unsigned apk
Open command prompt with right env settings pointing to JDK and ADT
Create keystore (if not already done)
Unpack into temp using jar
Copy dojo files over from android/native/www/default
Pack back into apk using jar
Sign the jar
Zipalign the jar
Now you have a working apk that includes the files/directories in asset that begin with a "_".
I prepared a simple quiz app for Windows 8 store. My app successfully passes on WACK just after building and creating local packages without login to store account, however it fails (perf test: launch was not detected) when I login to my store account, associate the app with a reserved app name and create packages to submit.
So, I submitted my app three times and it always failed requirement 3.8 since those packages fail. What should I do? Is there anything I miss? I'm dealing with this issue for many days but I can't find the right solution.
Regards,
Hakan
I downloaded and installed Visual Studio 2012 Update 1. WACK tool I use is the latest one. My Windows 8 account and Windows 8 Store account are same. However; I still have the problem.
That's what I'm doing;
I recreated my app project. Successfully builded the app and created (not store associated) app packages without login to store account on Visual Studio. After creating those packages, I started WACK on Visual Studio and app passed successfully. Then; I cleaned the solution and created the packages to upload store (I logged in to my store account on visual studio and chose the app name I reserved). After creating packages I started WACK again, but this time app failed with; "Launch was not detected" error.
I don't think there is anything else to do. I get bored after each unsuccessful submitting. What should I do? Does anyone have any idea?
Requirement 3.8 is very specific, and has nothing to do with your app's name. From the App Store Requirements:
3.8 Your app must meet the basic performance criteria on a low-power computer
The app must launch in 5 seconds or less
The app must suspend in 2 seconds or less
Did you test your app on an ARM based device? How much time does your app take to start up/ suspend?
Update:
If you are using the standalone WACK, it is possible that you are trying to certify the old version of your application. As I recall, when you associate your app with the App Store, your app's name AND package ID change. However, bits of the old app may still be around, which can cause the certification to be run on an app that no longer exists.
Something that may help is to first uninstall your app prior to creating the package. The other thing to try is to run the certification from within Visual Studio. I have found it to be more reliable than the standalone app.
Adobe Air brings following exception:
The application could not be installed because the AIR file is
damaged. Try obtaining a new AIR file from the application author.
Please add the different reasons which may lead to this error.
We had the same error as this guy:
The file ~/.airappinstall contains the following error:
failed while unpackaging: [ErrorEvent type="error" bubbles=false
cancelable=false eventPhase=2 text="invalid package signature"
errorID=5022]
The actual reason was not a damaged file or something like this, but our machine had a date from the past, which was not valid for the given certificate. After correcting the date/time on the computer, the installation worked just fine.
Even I faced the same error=5022, after thinking a lot on this issue, I finally got the
solution for this problem. It is simple, before installing the air app set the correct Date & Time for the system, WALLA it installs smoothly.
No need of changing the png name or anything else.
I faced this problem yesterday because my antivirus (avast pro/silent mode) was blocking access to file until finishing scanning, looks like installer don't like to wait, so when I switched off silent mode I made antivirus ignore scanning the file and installation completed successfully.
I have a virtual drive mapped to S: so that paths are the same between my home computer and work computer. I was trying to install the AIR app from an S: path. I guess it did it like it. Moving app to my desktop and launching there, worked.
Make sure you are signing the Application distributable and distributing the certificate along with the .air file.
I ran into same problems and solved it this way.
I had this issue when using Flash Builder 4, but building a Flex 3 application.
Basically, the installed AIR SDK in the Flex 3 SDK folder was AIR 1.5.3 (if I remember correctly), but the Flex 4 SDK folder had the AIR 2.0 SDK files (I'm not completely what the problem was).
My solution was to download the AIR 2.0 SDK, and unzip it over the Flex 3 SDK folder. Once I did that, the installation file worked fine. There is actually an article on Adobe about overwriting the AIR SDK files this way, although it didn't mention anything about installations or Flash Builder 4.
Mine was failing because I had another app on my system with the same name. Not a version of the app, a completely different app--native, not AIR.
Once I removed that app it worked fine.
For odd installation errors, keep in mind that Chrome uses a version of Flash that does not support AIR badge installation.
I encountered this error when trying to install an AIR file from an external / network drive. Copied the file locally, and installation proceeded normally.