adobe air 3.6 sdk beta released with preventBackup for ios application develop .
but when i used File.preventBackup.resolvePath(dbname) it gives,
1119: Access of possibly undefined property preventBackup through a reference with static type Class.
error,
how can i make directory do not back up with preventBackup
thx.
You get the error because there is no such method or property of File class called "preventBackup"
File class is described here: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/filesystem/File.html#propertySummary
.resolvePath is usually used in combination with a directory property, eg:
File.applicationDirectory.resolvePath(dbName);
Edit:
According to release notes for AIR 3.6 SDK:
To use this feature, application descriptor namespace 3.6 and SWF version 19 or greater would be required
So you need this at start of application descriptor file:
<application xmlns="http://ns.adobe.com/air/application/3.6">
And this in additional compiler arguments:
-swf-version=19
Related
I am new to xamarin studio.
I have added all the required packages corresponding to the target API 23 to my android xamarin studio project, set it to the right target API 23 but am still being haunted by these errors in the image below. Any help rendered will be greatly appreciated
Image contains errors from an android xamarin studio project
Your compile SDK version must match the support library's major version.
Since you are using support library v23, you need to compile against Android SDK of v23.
Alternatively you can continue compiling against v22 of the Android SDK by switching to the latest support library v22.
I have an Adobe Air application that I am packaging for iOS.
If the target is ipa-debug-interpreter or ipa-test-interpreter the app works just fine. However, any other target it crashes when trying to use assets. I have seen the following exception:
[Fault] exception, information=ReferenceError: Error #1065: Variable FlexVersion is not defined.
Fault, SpriteAsset() at SpriteAsset.as:131
131 if (appDomain.hasDefinition("mx.core::FlexVersion"))
Other times it will crash with no stack.
Why would it only work when the target includes interpreter?
Packaging with interpreter is faster than the regular debug packaging (not that I've ever noticed a timetable difference). I would hazard a guess that for it to be faster it must bypass certain processes which the normal debug would check for. From the type of error you're getting I would suggest you double check your manifest XML file for missing packages and/or the version of the AIR SDK you are targeting. Hope this provides some help.
EDIT: May also be worth revision which version of the FLEX SDK you are targeting and this can cause issues of this kind.
I have downloaded .dmg file for Qt on Android and iOS. I have installed it and tried to run examples. I am able to run examples under folder "widgets" for iOS but when I try to run example for "webkitwidgets" and run qmake on (let say for example of "browser") .pro (in this case for example browser.pro) then it gives me error : "Error unknown module(s) in Qt: webkitwidgets". Then I checked "ios" folder in installed qt directory. I found in "Include" folder there is no folder called "QtWebkitWidgets" while there is folder "QtWidgets". Let me know solution asap because I am doing some poc on Qt for iOS and need to have conclusion soon. Did I miss some steps while installation or do I have to do some extra steps to execute examples for QtWebkitWidgets. Let me know whether QtWebkitWidgets module is supported for in Qt for iOS or not. Note that I am using Qt 5.2 with XCode 5. If more detail is required then let me know.
Apple explicitly forbids that any programming language be compiled/interpreted on the iOS device itself, except by their own WebKit. So Qt’s WebKit is disallowed.
It is worthy to note thet part of the QtWebKit team has started the project QtWebEngine to explore the option of providing a Chromium/Blink based web engine instead of QtWebKit, and in addition to that, the iOS port of Qt will need their own webview API since Apple does not allow additional web engines on their iOS devices.
I've implemented a blackberry application using JRE5.0, it's running well on any device with OS5.0 and OS6.0
When I try to open the same application on 9900 which has OS 7.0, I got the following error:
Error Starting myAppName: Module 'MyAppName-4' has verification error
3337. (Codfile version 78)
where myAppName is the application name (name of the cod file)
as in the following image:
I checked the event logger, here what it contains (older to newer):
a System - VM:LINK MyAppName
a System - VM:VECPs=my.Package.Name.Containing.Screens
a System - VM:VECCs=oneOfMyScreenClassNames
a System - VM:VECMm=functionInOneOfMyClasses()
Module 'MyAppName-4' has verification error 3337 (codfile version 78)
Linker error: 'VerifyError' for MyAppName
Error starting myAppName: Module 'MyAppName-4' has verification error 3337 (codfile version 78)
Here is the content:
E System - JVM:INFOp=2100000a,a='7.0.0.296',o='4.0.0.127',h=7001204
For those who are interested, I found the solution.
In the logs there were:
a System - VM:VECCs=oneOfMyScreenClassNames
a System - VM:VECMm=functionInOneOfMyClasses()
I did the next steps in the whole class "oneOfMyScreenClassNames" indicated in logs
Here are the steps:
If you started by building a Java Archive (JAR) file and then used the RIM Application Program Compiler (RAPC) to create .cod files, make sure you turn obfuscation off when building the JAR file. The RAPC compiler performs its own obfuscation and issues may occur if the code is already obfuscated.
Remove any System.out.* calls. These generally do nothing on the BlackBerry smartphone, but they might cause verification errors.
Remove unused import statements.
Explicitly specify the access for each function or variable. For example, make sure each one is specified as public, private, or protected.
If you are working with a MIDlet, make sure the MIDlet class is declared as public.
Verification errors may occur if the COD file is corrupted or if it was not signed correctly. Make sure that you perform a clean rebuild and that you re-sign your application. Reinstall the application on the BlackBerry smartphone.
Comment out any non-executable code. Verification errors might be related to the size of the main code file and the library files. If you comment out non-executable code, the file sizes change, which may correct the problem.
If you have created any classes that inherit from RIM classes, change the name of any custom methods and members that you created in those classes. This makes sure that you have not named any methods or members of the same name in the internal RIM classes.
If your application is using BlackBerry® Device Software 3.8 or later, verification errors occur when an application that implements the javax.microedition.rms.RecordStore class is compiled using BlackBerry® Java® Development Environment (BlackBerry JDE) earlier than version 4.0. This occurs if the application uses either the addRecordListener or removeRecordListener methods of the RecordStore class. To resolve this issue, recompile the application using BlackBerry JDE 4.0 or later.
There is a problem with how the BlackBerry® Java® Virtual Machine (BlackBerry JVM) handles the referencing of a class directly within the constructor of another class. The following is an example:
Class1 class1= new Class1(Class2.class.getName()); To work around this issue, do not make the class call within a constructor
Remove references to a static instance variable from an inner class. There are a few ways you can remove these references, such as creating get/set methods for var in the outer class or modifying the logic to pull MyInnerClass out of MyOuterClass.
The build procedure normally compiles from the java source file with the javac command, and then runs preverify.exe file and then RAPC. Add the following command line arguments to javac to help avoid issues in earlier versions of the RAPC:
javac.exe -source 1.3 -target 1.1
Some methods that are very long can cause verification errors. By breaking these methods into helper methods, you can reduce the likelihood of verification errors.
Although not as likely, some very long method definitions (with 10 or more parameters), and some very long constant definitions (long package structure and/or long names) can also cause verification errors.
Source: http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800332/832062/Support_-_Preventing_verification_errors.html?nodeid=1499031&vernum=0
PS, I also removed "instanceOf" usage in code
I have implemented AES encryption in BlackBerry using code from the Knowledge Base Article "How to - Use Advanced Encryption"
I keep getting error:
Module 'net_rim_crypto' not found.
In the code I have imported net.rim.device.api.crypto.*; package, but I can't find the package net.rim.crypto.
Do I need to add any external jar for that?
You should install JRE 4.6 and set the API level to 4.6 and OS of the target device should be higher than JRE version.
If you have problem with BlackBerry API or OS version, you may consider to use bouncy castle for j2me.