stage.fullScreenWidth returns 960
stage.fullScreenHeight returns 640
stage.stageWidth returns 1000
stage.stageHeight returns 750
If I listen to Event.Resize, the values will be the same. But the IPhone 6+ screen sizes much more.
How should I fix this ?
My options:
stage.align = StageAlign.TOP_LEFT;
stage.scaleMode = StageScaleMode.NO_SCALE;
<key>UIDeviceFamily</key> = 1, 2
<requestedDisplayResolution>high</requestedDisplayResolution>
Hi, could you update the Android xml descriptor to support xxhdpi and xxxhdpi in the compatible-screens android:screenDensity please. as documented here : Supporting Multiple Screens | Android Developers
exemple :
<compatible-screens>
<!-- all small size screens 2"-3" -->
<!--<screen android:screenSize="small" android:screenDensity="ldpi" />
<screen android:screenSize="small" android:screenDensity="mdpi" />-->
<screen android:screenSize="small" android:screenDensity="hdpi" />
<screen android:screenSize="small" android:screenDensity="xhdpi" />
<screen android:screenSize="small" android:screenDensity="xxhdpi" />
<screen android:screenSize="small" android:screenDensity="xxxhdpi" />
<!-- all normal size screens 3"-5" -->
<!--<screen android:screenSize="normal" android:screenDensity="ldpi" />-->
<screen android:screenSize="normal" android:screenDensity="mdpi" />
<screen android:screenSize="normal" android:screenDensity="hdpi" />
<screen android:screenSize="normal" android:screenDensity="xhdpi" />
<screen android:screenSize="normal" android:screenDensity="xxhdpi" />
<screen android:screenSize="normal" android:screenDensity="xxxhdpi" />
<!-- all large size screens 4"-7" -->
<!--<screen android:screenSize="large" android:screenDensity="ldpi" />-->
<screen android:screenSize="large" android:screenDensity="mdpi" />
<screen android:screenSize="large" android:screenDensity="hdpi" />
<screen android:screenSize="large" android:screenDensity="xhdpi" />
<screen android:screenSize="large" android:screenDensity="xxhdpi" />
<screen android:screenSize="large" android:screenDensity="xxxhdpi" />
<!-- all xlarge size screens 7"+ -->
<!--<screen android:screenSize="xlarge" android:screenDensity="ldpi" />-->
<screen android:screenSize="xlarge" android:screenDensity="mdpi" />
<screen android:screenSize="xlarge" android:screenDensity="hdpi" />
<screen android:screenSize="xlarge" android:screenDensity="xhdpi" />
<screen android:screenSize="xlarge" android:screenDensity="xxhdpi" />
<screen android:screenSize="xlarge" android:screenDensity="xxxhdpi" />
</compatible-screens>
this give me the following error :
Error occurred while packaging the application:
aapt tool failed:Warning: AndroidManifest.xml already defines versionCode (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines versionName (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines minSdkVersion (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines targetSdkVersion (in http://schemas.android.com/apk/res/android); using existing value in manifest.
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:132: error: Error: String types not allowed (at 'screenDensity' with value 'xxhdpi').
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:136: error: Error: String types not allowed (at 'screenDensity' with value 'xxxhdpi').
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:148: error: Error: String types not allowed (at 'screenDensity' with value 'xxhdpi').
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:152: error: Error: String types not allowed (at 'screenDensity' with value 'xxxhdpi').
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:168: error: Error: String types not allowed (at 'screenDensity' with value 'xxhdpi').
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:172: error: Error: String types not allowed (at 'screenDensity' with value 'xxxhdpi').
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:188: error: Error: String types not allowed (at 'screenDensity' with value 'xxhdpi').
C:\Users\COPYQU~1\AppData\Local\Temp\2e2bf7c2-2ea9-4b47-bdf5-ddef3e77d39f\AndroidManifest. xml:192: error: Error: String types not allowed (at 'screenDensity' with value 'xxxhdpi').
I've been encountering this dreaded error in my current project and I'm flummoxed by the scant information about it. The release notes for AIR 18 list it as a known issue:
Quick project background: A Flex AIR app with multiple distribution targets (Android, iOS, OS X, Windows). Uses AIR 18.0.0.143 overlaid on Adobe Flex 4.6.0 SDK. There's also an ANE in use that might be complicating matters: https://github.com/freshplanet/ANE-Flurry
I encounter this error when I AOT test debug my app on iPad 2 (iOS 8.4), followed by a hard app crash:
[Fault] exception, information=Error: Error #3747: Multiple application domains are not supported on this operating system.
Debugging in fast compile mode does not trigger the problem. However I'm trying to simulate the app as it will run when App Store distributed.
Partial workaround: Through use of LoaderContext(false, ApplicationDomain.currentDomain, null) on problem SWFLoaders I've been able to reduce the occurrence of the issue, but it still seems to be triggered by other mechanisms, possibly Embed directives (the debug stack is a bit opaque).
The strange thing is, the same code is not a problem for my colleague. The only difference I can see is that I'm using IntelliJ IDEA 14 as my IDE and he's using Flash Builder.
Questions:
Where can I get more information on known issue 3990014?
Is the information at https://blogs.adobe.com/airodynamics/2012/11/09/packaging-and-loading-multiple-swfs-in-air -apps-on-ios/ concerning use of multiple SWFs on iOS still relevant?
Can I get around the problem by using a previous release version of AIR?
Does adobe AIR 13 support Windows mobile app?
Apple announced WatchKit.
It will be a very good oportunity to Adobe AIR.
Hi!
The last wek I updated Adobe Flash CC 2014 and also Air SDK 17. I saw that i am not able anymore to deactivate fast compiling .
So I tried and the List component is showing that all items are selected. It looks that all items are selected.
On IPAD it looks like this. everything seems to be selected
On Desktop it is correct.
Please help.
Michael
I have previously submitted many apps with underscores in the app id. Even today I made such an app. But sometimes I repeatedly get an error 105, application.id contains invalid character.
I found two contradictory articles, one that lists hyphens as a valid character, which it seems to be, and another which says that hyphens are converted to underscores.
Given that I have apps in the stores that do have underscores in the app id, how can I convince AIR 18 to allow that character?
BTW, the issue seems to be true in AIR 17 too.
Quick question for the AIR dev team.
Will Workers for iOS be a priority for AIR 18 beta, or are there any concrete plans for iOS workers?
i've been longing for this feature for quite some time now, it kind of sucks to have to maintain 2 versions of my code to support both Android and iOS.
Hi!
When the beta for Windows 64 bits AIR runtime?
Thanks!!!!!
Hello,
I'm building an iOS ANE with a third party lib framework + resources, so, I need to add both references to options.xml
Seems OK to framework but I received the following error when I tried to include resources: error 103: platform.packaged Resources is an unexpected element/attribute
<packagedDependencies>
<packagedDependency>ThirdLibAPI.embeddedframework/ThirdLibAPI.framework</packagedDependency>
</packagedDependencies>
<packagedResources>
<packagedResource>
<packageName>ThirdLibAPIResources</packageName>
<folderName>ThirdLibAPI.embeddedframework</folderName>
</packagedResource>
</packagedResources>
Environment:
AIR 19 (final)
OSX 10.11.1
I'm trying to create ANEs with arm64 support with no success so far.
My native libraries are compiled for both armv7 and arm64 since lipo -info confirms so, however ADT still outputs:
"Error: Apple App Store allows only universal applications. This ANE must have a universal iOS binary. Please change build settings in Xcode project to "Standard Architecture" to create universal library."
Do I need to change something in my ADT commandline? I tried several ANEs and had problems with all of them. Could anyone provide further information or tips?
Long time ago I found out that you used <versionNumber> to populate both keys in CFBundleShortVersionString and CFBundleVersion in info.plist. I was disappointed that I have to write some weird script to overcome this issue.
---
#/bin/bash
ORIGINAL_FILE="$1"
NEW_FILE="$1"
VERSION="$2"
BUILD="$3"
unzip -q "$ORIGINAL_FILE" -d temp
/usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString $VERSION" temp/Payload/*.app/Info.plist
/usr/libexec/PlistBuddy -c "Set :CFBundleVersion $BUILD" temp/Payload/*.app/Info.plist
codesign -f -s "XXXXXX" --entitlements "Entitlements.plist" temp/Payload/*.app
pushd temp > /dev/null
zip -qry ../temp.ipa *
popd > /dev/null
mv temp.ipa "$NEW_FILE"
rm -rf "temp"
---
Then I read this in AIR 18 and I was happy that you finally fixed this issue.
Build Number in AIR iOS
This feature will allow developers to update only the build number while keeping the version number same so that their application is available quickly on Testflight for beta testing. Now <versionLabel> tag will be used to populate CFBundleShortVersionString and <versionNumber> for CFBundleVersion. Previously we used only <versionNumber> to populate both the keys in info.plist. CFBundleShortVersionString will be the final release version application version of the application. This is useful in case of TestFlight because if developers do only minor changes in application , then they can only update CFBundleVersion to skip the app review phase by Apple(which is time consuming).
But now I am a little disappointed again. Why have you used limited <0-999>.<0-999>.<0-999> <versionNumber> to fill CFBundleVersion? We have use the last number as build number and are currently on 5834. So I am unable to remove script we are using because I get error 105: application.versionNumber contains an invalid value. Could you please at least remove the limitation of <versionNumber>. There is no limit in CFBundleVersion as you can see in IOS documentation. Or you could make it much simpler by allowing <iPhone><InfoAdditions>to contain these CFBundleVersion and CFBundleShortVersionString for those who knows what are they doing and do whatever you want with <versionNumber> or <versionLabel>. Thank you very much.
CFBundleVersion (String - iOS, OS X) specifies the build version number of the bundle, which identifies an iteration (released or unreleased) of the bundle. The build version number should be a string comprised of three non-negative, period-separated integers with the first integer being greater than zero. The string should only contain numeric (0-9) and period (.) characters. Leading zeros are truncated from each integer and will be ignored (that is, 1.02.3 is equivalent to 1.2.3). This key is not localizable.
I'm here at Adobe MAX and find it very strange that there isn't even any sessions about mobile gaming, there wasnt any mobile games shown at the keynote. it was 100% geared to the designer.
I'd really like to know what the future of AIR is.
it really seems like Adobe doesn't care about it at all anymore.
Anyone have any thoughts on this?
Hi,
I'm trying to use adt -package ipa-app-store. I have a CI server doing this job.
Everything was fine until I've updated from AIR 17.0 to AIR 19.0. Now adt get's stuck while building the ipa.
I've tried running the adt package from command line on CI server. I am still able to build the apk with AIR 19.0, however building ipa has no reaction, just remains hanging.
AIR 18.0 has same behaviour as AIR 19.0
CI server is Windows. Using same adt package command, swf file, etc on Mac, I am able to package the ipa.
I still need to get my CI server running, if anyone can provide some ideas, would be very helpful.
Thank you.
Since upgrading to AIR 3.8, we can no longer package our AIR Application.
We are getting the following error:
internal_package-ios:
[exec] ld: -pie can only be used when targeting iOS 4.2 or later
[exec] Compilation failed while executing : ld64
Screenshot Here: http://cl.ly/image/3h2U1g271n1J
Reverting to AIR 3.7 fixes the issue... but we need 3.8 as we need the 4096 texture support that comes with BASELINE_EXTENDED profile.
From googling, this seems like it's related to the iOS SDK included with AIR, but the issue was fixed in AIR 3.7. Seems it has been regressed...
Hi,
I'm using the Flash 6 and Flash CC IDE to publish an AIR app for IOS. Our product has been in the AppStore for a few weeks, and has received quite good feedback so far. We just installed IOS7 on a test iPad, and we ran into this dialog box:
"Speakaboos" Would Like to Access the Microphone [ Dont Allow | OK ]
I believe this is a known issue that has been addressed in AIR 3.9 Beta, so I downloaded it and added it to Flash. Now when I try to publish, I get this error:
Test Movie terminated. Not supported native extensions profile.
We are using the Native Extensions from Milkman Games; StoreKit, GoViral and EasyPush. We are also using com.adobe.extension.NetworkInfo.ane.
I'm publishing from the Flash IDE to support the current version that's in the store 1.0.x. All incremental releases of our 1.0 product need to be published from the Flash IDE. We have since been developing our 1.1 product that is published from Flash Builder. When I publish this way, I don't get the error. Therefore, it seems to me that the issue has something to do with my ActionScript settings in the Flash IDE, or perhaps the packaging of the current versions of the Milkman Games ANEs with AIR 3.9/FlashIDE.
If anyone could give me some pointers about how to troubleshoot this issue, I'd be very grateful. Thanks in advance!
-steve
Using the beta sdk released today I cannot compile iOS apps anymore in Intellij Idea (64bit Windows). The last beta worked fine. I am getting an "SDK 'AirSDK' includes AIR null" error. I tried to set -swf-version=24 and changed namespace to 13.0 without luck. Is this IDE specific or is something missing in the package?
Hello,
I tried to export an existing Android-ARM to Android-x86:
This application uses to 2 ANE for In-App purchases. One for iOS and another one for Android. I repackaged the Android ANE file to be compatible with Android-x86 and I also add the new Flash Builder "-arch" with value "x86" and place it before "-storetype".
Error occurred while packaging the application:
output file is not writable
usage:
adt -checkstore SIGNING_OPTIONS
adt -certificate -cn <name> ( -ou <org-unit> )? ( -o <org-name> )? ( -c <country> )? ( -validityPeriod <years> )? ( 1024-RSA | 2048-RSA ) <pfx-file> <password>
adt -help
adt -migrate SIGNING_OPTIONS ( <air-file-in> | <airn-file-in> ) <output-file>
adt -package SIGNING_OPTIONS ( -target air )? <output-package> ( <app-desc> FILE_OPTIONS | <input-package> )
adt -package SIGNING_OPTIONS -target airn <output-package> ( <app-desc> FILE-AND-PATH-OPTIONS | <input-package> )
adt -package -target ( apk | apk-debug | apk-emulator | apk-captive-runtime ) ( CONNECT_OPTIONS? | LISTEN_OPTIONS? ) ( -airDownloadURL <url> )? ( ARCH_OPTIONS )? SIGNING_OPTIONS <output-package> ( <app-desc> PLATFORM-SDK-OPTION? FILE-AND-PATH-OPTIONS | <input-package> PLATFORM-SDK-OPTION? )
adt -package -target ( ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc | ipa-test-interpreter | ipa-debug-interpreter | ipa-test-interpreter-simulator | ipa-debug-interpreter-simulator ) ( CONNECT_OPTIONS? | LISTEN_OPTIONS? ) ( -sampler )? ANE_LINK_OPTIONS? AOT_MODE_OPTIONS? SIGNING_OPTIONS <output-package> ( <app-desc> PLATFORM-SDK-OPTION? FILE-AND-PATH-OPTIONS | <input-package> PLATFORM-SDK-OPTION? )
adt -package SIGNING_OPTIONS? -target native SIGNING_OPTIONS? <output-package> ( <app-desc> FILE-AND-PATH-OPTIONS | <input-package> )
adt -package SIGNING_OPTIONS? -migrate SIGNING_OPTIONS -target native SIGNING_OPTIONS? <output-package> <app-desc> FILE_OPTIONS PATH-OPTION
adt -package SIGNING_OPTIONS? -target bundle SIGNING_OPTIONS? <output-package> ( <app-desc> FILE-AND-PATH-OPTIONS | <input-package> )
adt -package SIGNING_OPTIONS? -target ane <output-package> <ext-desc> ANE_OPTIONS
adt -prepare <airi-file> <app-desc> FILE_AND_PATH_OPTIONS
adt -sign SIGNING_OPTIONS ( -target ( air | airn | ane ) )? ( <airi-file> | <unsigned-ane-file> ) <output-file>
adt -devices PLATFORM-OPTION PLATFORM-SDK-OPTION?
adt -installRuntime PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? ( -package <apk-file> )?
adt -installApp PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? -package <apk-file | ipa-file>
adt -uninstallRuntime PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION?
adt -uninstallApp PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? -appid <app-id>
adt -launchApp { PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? ( -debuggerPort port )? -appid <app-id> }
adt -runtimeVersion PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION?
adt -appVersion PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? -appid <app-id>
adt -version
SIGNING_OPTIONS : -storetype <type> ( -keystore <store> )? ( -storepass <pass> )? ( -alias <aliasName> )? ( -keypass <pass> )? ( -providerName <name> )? ( -tsa <url> )? ( -provisioning-profile <profile> )?
FILE_OPTIONS : <fileOrDir>* ( ( -C <dir> <fileOrDir>+ ) | ( -e <file> <path> ) )*
ARCH_OPTIONS : -arch (armv7 | x86)
CONNECT_OPTIONS : -connect <host>
LISTEN_OPTIONS : -listen <port>
ANE_LINK_OPTIONS : -hideAneLibSymbols ( yes | no )
ANE_OPTIONS : -swc <swc> ( -platform <name> (-platformoptions <file>)? <fileOrDir>* ( -C <dir> <fileOrDir>+ )* )*
FILE-AND-PATH-OPTIONS: ( PATH-OPTION | FILE-OPTIONS ) FILE-AND-PATH-OPTIONS?
PATH-OPTION : -extdir <dir>
PLATFORM-OPTION : -platform (android | ios)
PLATFORM-SDK-OPTION : -platformsdk <platform-sdk-home-dir>
DEVICE-OPTION : -device ( deviceID | ios-simulator )
AOT_MODE_OPTIONS : -useLegacyAOT ( yes | no )
Hi,
With Air 3.6, are actionscript workers now available for iOS?
Hello,
since we moved to Air 15 from Air 4.0 we getting a lot of native crashes on Google Developer Console only with Android 4.4 and Galaxy Tab 3 and 4 with 7 inch display
we used air sdk 15.0.302 and 15.0.349 beta with stage 3d initiated with :
stage.stage3Ds[0].requestContext3DMatchingProfiles(Vector.<String>([Context3DProfile.BASEL INE, Context3DProfile.BASELINE_EXTENDED]));
users reporting that the game automatically closing after opening and randomly crashing.
the first error that happens a lot is :
Native crash at /system/lib/egl/libEGL_MRVL.so
in /system/lib/egl/libEGL_MRVL.so (eglMakeCurrent+204), /system/lib/egl/libEGL_MRVL.so (eglMakeCurrent+144)
Build fingerprint: 'samsung/degaswifiue/degaswifiue:4.4.2/KOT49H/T230NUUEU0ANH1:user/release-keys'
Revision: '3'
pid: 21365, tid: 21365, name: mygame >>> air.com.mygame <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr e7cb7b04
and dump of registers state , backtrack, code around pc and lr
the other error happens less :
java.lang.IllegalStateException
java.lang.IllegalStateException: eglMakeCurrent failed EGL_BAD_CONTEXT
at android.view.HardwareRenderer$GlRenderer.createSurface(HardwareRenderer.java:1362)
at android.view.HardwareRenderer$GlRenderer.createEglSurface(HardwareRenderer.java:1243)
at android.view.HardwareRenderer$GlRenderer.initialize(HardwareRenderer.java:1060)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1877)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1256)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6632)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:813)
at android.view.Choreographer.doCallbacks(Choreographer.java:613)
at android.view.Choreographer.doFrame(Choreographer.java:583)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:799)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:146)
at android.app.ActivityThread.main(ActivityThread.java:5598)
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:1283)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099)
at dalvik.system.NativeStart.main(Native Method)
my guess it's some how related to Marvell processor or to implementation of the driver on Android 4.4
any one experience this problem?
any suggestions for solution?
Thank you,
