Using Flash Builder 4.6 & SDK 4.6
Away3d and Starling Interoperation
device - samsung galuxy s3
debugging on device, its run well.
install exported apk on the device, its just white background.
[app name]_app.xml file setting is
<renderMode>direct</renderMode>
<!-- Whether or not to pan when a soft keyboard is raised or lowered (either "pan" or "none"). Optional. Defaults "pan." -->
<!-- <softKeyboardBehavior></softKeyboardBehavior> -->
<autoOrients>false</autoOrients>
<fullScreen>true</fullScreen>
<visible>true</visible>
<softKeyboardBehavior>none</softKeyboardBehavior>
Solved.
just use latest Air sdk.
http://www.flashdeveloper.co/post/10985842021/overlay-adobe-air-32-in-flash-builder-46
Related
The new 9.1 simulator with Xcode 7.1 has the feature to simulate a force touch like the iPhone 6s / 6s+ but the option is greyed / disabled.
iOS Simulator > Hardware > Force Touch Pressure [disabled]
Screenshot for reference
Anybody know how to enable this option?.
Note: Im testing this on a iPhone 6s simulator
Simulator does not support interaction with iOS Devices using 3D Touch prior to Xcode 7.3. The menu item that you are referencing relates only to Apple Watch devices.
select simulator(watch) --> Hardware --> Force Touch Pressure --> Deep Press, and then click and hold on simulator, menu will be popup. you don't need to real device to test context menu.
On the Apple Developer website, it says:
NOTE
With Xcode 7.1 you must develop on a device that supports 3D Touch. Simulator in Xcode 7.1 does not support 3D Touch.
Apparently, the new Simulator 9.1 does not support 3D Touch. You can actually implement such a behavior but (unfortunately) you have to test it on real a device that supports 3D Touch.
I guess we all have to wait for the next issue of Xcode.
See here for similar discussion and way to test force touch only for quick actions (on the app icon).
It is true that by far (Xcode 10.1) iOS simulator still does not support 3D touch if your Mac doesn't have touchpad with this capability.
However, there are a few libraries like this that swizzle system's touch event handling and inject 3D touch feature. Of course, you don't want this code to be included in your production code to avoid being rejected on app's review, but you can certainly use this for development!
The library I mentioned works great for my Swift 4.1 project.
I am having a terrible time updating my Flex Project to use 64bit and iOS 8. I have to update because when I use Adobe Air SDK 14 I get the following error while uploading my release version via the Application Loader.
I've followed all of the instructions listed in the following, but nothing works:
http://easynativeextensions.com/making-your-ios-apps-universal/
https://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder.html
https://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html
When I change the line in my air descriptor mxl file to:
<application xmlns="http://ns.adobe.com/air/application/18.0">
I get the following error:
I've downloaded the Air SDK from this page: http://www.adobe.com/devnet/air/air-sdk-download.html
I tried using both the main link and the Flex specific SDK only link.
Then I installed the Air SDK in /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722
Also, I used the Apache Flex SDK installer to get the latest flex SDK to be used with Air SDK 18.
It seems to have installed fine
As you can see I've tried multiple versions. I also select the air version in my Flex Project compiler path.
I even tried overlaying the SDK in the Flash Builder SDKs folder.
Still, I always get the error when I try to set my app descriptor XML line to 18.0
<application xmlns="http://ns.adobe.com/air/application/18.0">
I can set it to 16.0 and the application will build.
<application xmlns="http://ns.adobe.com/air/application/16.0">
But then when I build, my app has a ton of UI problems. Spinners go crazy and tab bars, buttons, and layout all have problems. My app goes from looking like this:
To this:
I have no idea what to do.
Menu -> Clean Project ....
Next, rebuilding
Apache flex 4.9.1 needs minimum Flash Player 11.1.
I read that Apache flex 4.9.0 is working with Flash Player 10.2 is that right? I can't find it anywhere! Where can I download it from?
Thanks!
No need to build the SDK from scratch, Apache Flex 4.9/4.10/4.11 will work with Flash Player 10.2 and above out of the box, 11.1 is not the minimum version. All you need to do is change the configuration file (framework/flex-config.xml) to use 10.2 rather than the default 11.1 and download the correct player global swc. The Apache Flex README has more details instructions on how to do this.
https://github.com/apache/flex-sdk/blob/develop/README
Alternatively the installer (version 2.7 or above) will allow you the select the Flash Player version.
http://flex.apache.org/installer.html
That being said some features may work poorly (eg mobile components) and it hasn't been fully tested on Flash Player 10.2.
I have an ActionScript only Flash Builder 4 project of which i know that it was successfully exported for AIR 2.0
If I set the the Flex SDK to 'Hero' and the required AIR version to 2.6 in the app-descriptor like here, then the export works fine:
However - if I change the Flex SDK to 4.0 (overlayed with the AIR 2.0.2 SDK) and change the version in the app-descriptor.xml to 2.0 like here:
then it will compile just fine and run in ADL, but it won't export. If i click the "Finish" button, the window only flashes for a moment but nothing happens. i can repeatedly click on finish, just a short flash, no error message, no exported air file.
If I leave the Flex SDK on 'Hero' and the only thing I do is to change 2.6 in the app-descriptor.xml to 2.0, then the same problem occurs!
I tried this with Flash Builder 4 as well as Flash Builder Burrito - in both cases the same problem.
Anyone an idea what goes wrong?
The app descriptor file is very different between 2.0 and 2.5 and above. I'm surprised you're not seeing an error because I did (maybe try doing a clean?). For instance, 2.5 supports profiles, instead of the <version> tag, it uses <versionNumber> and it also supports metadata for android/playbook OS'.
Try deleting the application manifest XML for your air app and allowing flex builder to re-generate it. Sometimes these kinds of glitches happen because of errors with the application manifest.
I am having some issues with the differences between running my Air Desktop application with the ADL from within my IDE and actually running it as an packaged air application that is installed. Everything functions as it should in the IDE when run with ADL, but once it is packaged the drag and drop functionality no longer works correctly.
I was able to get this to work when Adobe Air 1.5 runtime was installed, instead of 2.5. I am aware that there were a lot of changes made with this last update, but I am unsure of how to proceed, as I am unable to debug the packaged air application to see what is actually happening.
One solution that I could see would be to install the Adobe Air 2.5 SDK and use that to debug with.
If anyone has any insight to why drag and drop works in the ADL and the runtime, your feedback would be much appreciated.
Also, I am using Flash Builder 4, with the Flex 3.5 SDK
If something doesn't work when compiled, it's usually because you've used a feature only allowed for natively packaged AIR applications. Try packaging it as a native file using this guide and see if it works:
http://help.adobe.com/en_US/air/build/WS789ea67d3e73a8b22388411123785d839c-8000.html
Essentially all you'll need to do is:
Check this line in your app.xml file and make sure it is uncommented and set to extendedDesktop like below:
<supportedProfiles>extendedDesktop</supportedProfiles>
and then on the command line call:
ADT -package -target native mynewfilepath/myFile.exe myfilepath/myFile.air
[ADT is found within your flex sdk folder.]