Adobe Community
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
About jadams602
since
‎Jun 09, 2009
‎Oct 02, 2022
jadams602
Engaged
176
Posts
33
Upvotes
13
Solutions
‎Aug 03, 2017
06:45 AM
Just tried the latest AIR 27 beta on my app where I have been doing an external resign because of dynamic frameworks use, but now I just get this from AIR 27: Anyone else able to build an app with ANEs using dynamic frameworks? Maybe someone at Adobe can suggest (knowing the line of code that is throwing a null) what might be the cause) (And no, I'm not going to be able to provide a complete sample project that duplicates this error, as I'm using too much proprietary, unreleased ANE code and dynamic framework elements) Hoping someone can at least work backward from this point of failure. Failed build results in: unexpected failure: null java.lang.NullPointerException at com.adobe.air.ipa.IPAOutputStream.finalizeFrameworkSig(IPAOutputStream.java:1310) at com.adobe.air.ApplicationPackager.createPackage(ApplicationPackager.java:94) at com.adobe.air.ipa.IPAPackager.createPackage(IPAPackager.java:291) at com.adobe.air.ADT.parseArgsAndGo(ADT.java:673) at com.adobe.air.ADT.run(ADT.java:471) at com.adobe.air.ADT.main(ADT.java:521)
... View more
‎Jul 05, 2017
08:33 AM
2 Upvotes
On Android you could possibly do this without a native extension, although technically you should really be saving files into the standard Android photo directory for the OS, which can only be gotten with a native call to (Java code below): File path = Environment.getExternalStoragePublicDirectory( Environment.DIRECTORY_PICTURES); (sure you could guess various default folders you might find on the web, but some versions of the OS have now abstracted this folder so it isn't the same guaranteed location. It is important to use the right folder otherwise other apps or default photo browsing app won't see the images your app is exporting (if that is important to make them public to all other apps on the device)) On iOS I don't see how you could do it without an ANE as Adobe's API is simply CameraRoll.addBitmapData Adobe has a CameraRollBrowseOptions class but no CameraRollSaveOptions class to support customization.
... View more
‎Jul 05, 2017
07:28 AM
Since Adobe still only supports JPEG which is lacking when you might want to really use 32-bit PNG with optional transparency, I recommend using one of the various ANEs out there that support exporting Photos and also adds support for PNG.
... View more
‎Jun 23, 2017
08:02 AM
By the way, when you are packaging up a macOS app for submission to the Mac App Store and you have built your .pkg for submission, you can actually test and deploy this sandboxed version locally on your mac into the /Applications folder using: sudo installer -store -pkg XXXX.pkg -target / where XXXX is the name of your app .pkg. This could possibly help you test your app in a sandboxed environment before giving it to Apple that you wouldn't experience yourself to in direct .app development builds.
... View more
‎Jun 23, 2017
07:54 AM
If you are getting an exception with trying to use an Open or Save Panel: Terminating app due to uncaught exception 'NSObjectNotAvailableException', reason: 'service com.apple.appkit.xpc.openAndSavePanelService failed to init an instance of NSOpenPanelService on behalf of remember that macOS apps on the Mac App Store must work in the sandboxed environment, so make sure you follow all of Apple's rules with file access exceptions with sandboxed apps: Technical Q&A QA1773: Common app sandboxing issues With Open/Save you need to make sure you include in your Entitlements.plist: <key>com.apple.security.files.user-selected.read-write</key> <true/> and that you don't try to programmatically open or save a file outside your app's sandbox folders programmatically but only present an open or save panel where only your user chooses throw the open or save panels the location to open or save a file. Only when the user chooses a file will the app be able to access files outside the sandboxed environment. (Details in Apple's documentation). Using AIR's open and save panels should conform to these Apple requirements when using the latest AIR SDKs.
... View more
‎Jun 21, 2017
07:29 AM
A starting page would likely be the SDK archive page, then figuring out how far back you wanted/needed to go: Find and download archived versions of Adobe AIR SDK
... View more
‎Jun 19, 2017
09:27 AM
new iOS 11 review in App API They are asking about the new StoreKit API additions in iOS 11 which allow Apple's in-app review requests to users. It is more than likely you or someone will need to implement a simple ANE to trigger this. I doubt this would be high on Adobe's radar to add this within AIR itself.
... View more
‎Jun 09, 2017
01:59 PM
Sorry, I really cant tell from what you are showing. this is really just a file path issue... If you can't figure out your relative paths just play it safe and use absolute paths for your .plist and your .app ... ie codesign -f -s "3rd Party Mac Developer Application: Carving Technologies LLC (4397PR2B6Q)" --entitlements "/Users/saifrehmn/.....somewhere..../PumpkinEntitlements.plist" "/Users/saifrehmn/.....somewhere/..../Pumpkin.app"
... View more
‎Jun 09, 2017
01:33 PM
You would manually make your own entitlements plist file and given your codesign line above, I assume you are doing this in the Terminal and your 'pwd' directory is where your Pumpkin.app/ folder is? so if you are using --entitlements "Pumpkin.entitlements" you just need to place that file in the same folder (but you can also do things like --entitlements ../../PumpkinEntitlements.plist and reference a relative location as well. I recommend using the .plist extension, --entitlements PumpkinEntitlements.plist since this is the type of file you are making. Use a text editor and make a PumpkinEntitlements.plist file that contains (as an example, you might not need all these settings but consult Apple's documentation on what entitlement permissions you might need based on the things your app is doing): <?xml version="1.0" encoding="utf-8"?> <plist version="1.0"> <dict> <key>com.apple.security.app-sandbox</key> <true/> <key>com.apple.security.files.user-selected.read-write</key> <true/> <key>com.apple.security.network.client</key> <true/> </dict> </plist> (com.apple.security.network.client if you use the internet) (com.apple.security.files.user-selected.read-write if you use Open/Save panels) etc...
... View more
‎Jun 09, 2017
12:41 PM
1 Upvote
Not sure what codesigning steps you are currently using, but one useful discussion with links is at: Re: Tutorial on publishing Flex/Air app for Mac App Store or just using Developer ID for general distribution In particular related to the sandboxing error above, you would want to make sure the lines <key>com.apple.security.app-sandbox</key> <true/> are part of the Entitlements.plist you will be using
... View more
‎Jun 01, 2017
02:19 PM
Thanks for documenting all your work and providing the project setups on github. Following your techniques, I was also able to integrate a third-party Swift framework into an ANE project and get it to work on iOS, tvOS and macOS. Quite a bit of fidgeting, and as you mention with your tools, requires resigning .ipa before using on iOS and tvOS devices. Given that more and more third party frameworks are switching to Swift instead of Objective-C, it is becoming limiting to assume we are going to be able to build all our ANEs with static libs. I second the idea that Adobe should devote some resources to making Swift framework integration into ANE development the new norm for iOS/tvOS/macOS platforms.
... View more
‎May 16, 2017
07:34 AM
Background: What works fine: I am successfully building an ANE that supports tvOS, and like you can do on iOS, I am successfully building both device and simulator platforms into the ANE: "appleTV-ARM" and "appleTV-x86" (like you can do for iOS building for both platforms "iPhone-ARM" and "iPhone-x86"). I am using IntelliJ IDEA 2017.1.2, and there is no issue actually building an .ipa and deploying to the AppleTV device directly using a custom Apple iOS SDK target: /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/SDKs/AppleTVOS.sdk . Even running in debug mode in IntelliJ works fine with actual device hardware and the ANE works too, including the "appleTV-ARM" platform correctly. What doesn't work: Additionally, I am trying to setup IntelliJ to run the AppleTV Simulator to include the proper "appleTV-x86" platform when it builds the .ipa. Setting up a build configuration choosing iOS Simulator and setting the SDK to: /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVSimulator.platform/Developer/SDKs/AppleTVSimulator.sdk does in fact work to launch the AppleTV simulator. (If you had no ANEs in your AIR app you would be done and fine). However, trying to include an ANE and run on the Simulator generates errors because for some reason, the platform "appleTV-x86" is not getting included in the .ipa but instead the "iPhone-x86" platform (I looked inside the resulting .ipa contents to confirm this). As I said, this doesn't happen when using the 'iOS device' / 'Package AIR Application' builds, but only when trying to use simulator mode. Anyone know of a trick or extra build setting within IntelliJ to get "appleTV-x86" included instead of "iPhone-x86"? I mention this here just in case this is a current limitation that might need addressed in the AIR 26 Beta SDK itself as opposed to a limitation in IntelliJ IDEA. Thanks
... View more
‎May 03, 2017
10:18 AM
2 Upvotes
Some feedback on the new DeviceRotation feature in AIR 26 beta (tested with 26.0.0.93 in particular) Comments: Do you plan on exposing an option to control the delay/rate at which DeviceRotationEvent.UPDATE events are delivered? With a quick simple test, seeing the following average rates of DeviceRotationEvent.UPDATE callbacks using its reported timestamps): Nexus 7 ~ every 125 milliseconds iOS iPhone 6 - every 90 milliseconds But at least on Android natively, you get to control the delay with SensorManager's SENSOR_DELAY_FASTEST, _GAME, _NORMAL, _UI Using Distriqt's existing third-party ANE https://github.com/distriqt/ANE-DeviceMotion and its exposure to a corresponding SensorRate property, I am able to get rates up to ~ 10 - 20 ms on the devices above with SensorRate.SENSOR_DELAY_FASTEST (even on iOS) Considering a vast majority of AIR apps that might want to use this feature are games, it might make sense for you to at least expose an optional GAME mode rate that can match ~ 20ms - 50ms on games. Issues: Testing with a Samsung Galaxy S III SGH-T999 running Android 4.4.4 , DeviceRotation.isSupported returns true but no DeviceRotationEvent.UPDATE events are received (same simple app code used to successfully get events on a Nexus 7 and iOS iPhone 6 above)
... View more
‎Sep 28, 2016
06:33 PM
1 Upvote
Adobe staff really shouldn't keep posting <key>NSAppTransportSecurity</key> <dict> <key>NSAllowsArbitraryLoads</key><true/> </dict> as *the* solution for every NSAppTransportSecurity issue. The proper solution is to only add exceptions to the domains your app is really using, not just completely disable NSAppTransportSecurity like this. This isn't why Apple added this feature just so everyone turns around and just disables it. Completely disabling NSAppTransportSecurity should only be used in development testing or if your app actually needs to allow your users to enter arbitrary URLs like a web browser. At some point Apple will likely crack down on settings like the above when you submit to the store (if they aren't already)
... View more
‎Sep 15, 2016
04:14 PM
You see everything. I was talking about the video link to Apple and the Adobe staff's link to the documentation. No, Starling does not use URLMonitor. Best guess is that it is one of the ANEs you are using. If you can setup the local IPv6 testing and can remove use of each ANE one by one, you might be able to narrow the culprit down.
... View more
‎Sep 15, 2016
06:03 AM
Ami Hanya wrote: how can i check it? and what i need to changh in the app? The video and the link provided above in this thread from Adobe staff show you how to test locally for iPv6 compatibility with your app. What you need to change in your app all depends upon what you are using to access the network. If you are only using URLLoader, Adobe has confirmed it is IPv6 compliant. If you are using URLMonitor some people have reported IPv6 issues, and I haven't seen any official confirmation or denial from Adobe whether this class is IPv6 compliant. I've seen other posts where people have swapped out their use of URLMonitor with an ANE that does equivalent network reachability testing. If you are using any ANEs that use networking code you need to check their source for IPv6 compliance or confirm with the ANE creator whether it is compatible.
... View more
‎Sep 15, 2016
04:07 AM
Right now, my only idea is to buy IPv6 for the server/domain we are using. I'm going trough the process of purchasing one right now. I've used https://ip6.nl/ to test if the domain is ready for IPv6, and lets say mine is not. Please make sure you re-read the earlier comment and watch the linked Apple video. This requirement for your app has nothing to do with whether your server is using IPv6 or not, that isn't going to fix anything. It is about whether your client app works in an IPv6 only network (even when hitting IPv4 servers).
... View more
‎Aug 04, 2016
08:46 AM
1 Upvote
Just to further clarify the difference between your original code and the sample above that works, you are trying to write a file using File.applicationDirectory. That is a read-only directory on iOS (and normally other platforms as well, as mentioned in the docs for File: File - Adobe ActionScript® 3 (AS3 ) API Reference ) You shouldn't ever try to write into File.applicationDirectory you should at least use File.applicationStorageDirectory, and if you need cache content consider using File.cacheDirectory. All those helper static File. Directory properties do all the work for you to chose the right folder no matter what platform. If you are curious where those directories resolve on various platforms there is a nice summary here: Adobe Flash Platform * Working with File objects in AIR
... View more
‎Jul 21, 2016
09:50 AM
1 Upvote
@caco_chapira Your issue isn't at all related to IPv6. Your issue sounds like you are not using NSAppTransportSecurity settings (a different Apple requirement). Your first post said "my app just requests normal https urls" but in your second example, you are not using https:, you are using http:, so unless you added NSAppTransportSecurity settings, your http: requests will fail (nothing to do with the IPv6 discussion above). Check the other NSAppTransportSecurity threads for details on NSAppTransportSecurity.
... View more
‎Jun 30, 2016
06:37 AM
jingji_ wrote: I'm using it with static IP address instead of a domain. Hey thanks! If this is a static IPv4 address, are you planning on using that in production or is this only for development testing? Just mentioning that you could run into another Apple hurdle if you need to keep using static IPv4 addresses as Apple requires apps also support working in an IPv6-only network environment now, so you could get an app rejection if you plan on keeping static IPv4 addresses when Apple verifies it with IPv6-only network. It would be best if you can avoid the IPv4 static addresses even in development so you can also test the app yourself in IPv6-only networks too.
... View more
‎Jun 29, 2016
09:11 AM
Are you using any ANEs (native extensions) in your app to determine whether you are connected to the internet/network? Adobe has already said their use of URLs is IPv6-only-network compliant, but if you have any ANEs in your app that are doing their own 'network connected' code they might be using IPv4 only APIs. If Apple is flagging an issue related to IPv6 network, you can test this locally yourself with your own Mac and see if you can reproduce the problem, links at the end of this thread: IOS submission refused because of IPv6 only
... View more
‎Jun 28, 2016
06:16 AM
So it looks like you decided to just completely disable App Transport Security by using <key>NSAllowsArbitraryLoads</key><true/> If your app is really only going to one site "kyt.jxt189.com" you should really consider adding more specialized App Transport Security exceptions that focus on allowing only jxt189.com and not the whole internet. At some point Apple might not allow you to just disable App Transport Security completely if you aren't building a general purpose web browsing app. Regardless though, if they said something like "they can't login in the server in our IPA", maybe they mean you need to provide them a test username and password to login to the site to properly test the app? I don't think this new issue of theirs has anything to do with App Transport Security at all now, you have completely disabled ATS in your app...
... View more
‎Jun 21, 2016
10:44 AM
2 Upvotes
Starting with AIR SDK 20, the AIR Runtime is now built with the iOS 9 SDK, this opens up the new requirement from Apple about App Transport Security: Flash Player Help | Release Notes | Flash Player® 20 AIR® 20 Certainly sounds like you are running into missing NSAppTransportSecurity settings in your app descriptor if you are trying to use http: URLs and not https: For example, like the following discussion: URLLoader iOS - Error #2032: Stream Error « Starling Forum
... View more
‎Jun 09, 2016
09:38 AM
And you are using hostnames for your access and not IPv4 dot notation addresses ("0.0.0.0")? If it is only URLLoader use I guess it would be confirming with Adobe how they implement things in iOS AIR runtime. If it is a problem with URLLoader you should definitely be able to confirm this yourself with a local NAT64 hosting, maybe you know a Mac user friend to try it out.
... View more
‎Jun 09, 2016
09:35 AM
flashysquirrel wrote: For the local IPv6 network, is there any solution for a PC user ? I don't know about NAT64 internet hosting software for PCs like what OS X supports but that is what you would want to try and research. So, the request i make with URLLoader, without any specific configuration, and without any specific manifest additions should work on an IPv6 network ? Or should the server be configured for IPv6 ? i'm a little confused about what they expect ... A few people have said AIR is already IPv6 compliant (can't say for sure myself) so if you are exclusively using URLLoader for all your network access? Then it would be up to the AIR iOS implementation to ensure IPv6 compatibility. Are you using any ANEs at all? You would need to check them for any network code.
... View more
‎Jun 09, 2016
09:30 AM
What client network libraries are you using in the app to make the requests? Again, it is not whether your servers are IPv6 but whether the client network code you are using works in a IPv6 NAT64 network where your mobile app thinks everything is IPv6 (even your IPv4 server)
... View more
‎Jun 09, 2016
08:20 AM
NSAppTransportSecurity is about https support it is not related to the ipv6 requirements. It will not disable ipv6 requirements from Apple. Watch the first 15 minutes of this WWDC 2015 video: https://developer.apple.com/videos/play/wwdc2015/719/ It shows how you can setup a local IpV6 network for your device testing with your Mac and some common sources of ipv6 problems. The issue also isn't necessarily directly related to your server being ipv6, but that the app will work on an ipv6 only network.
... View more
‎Mar 15, 2016
07:23 AM
Ok, well the idea was that you would end up seeing which files or folders are getting created in those directories, and at some point in your app you would instantiate a File instance using a path pointing at those problem file or folder and set preventBackup = true and that would flag them from iCloud trying to back them up. I also wouldn't assume that the one that got accepted is also truly 'safe', from experience, its been seen many times that any given review of a version isn't always 100% consistent. One version might get accepted, and the next update with just some minor changes might get flagged for something some other reviewer missed the first time. Not sure what else to suggest except to make sure you execute every scene/feature in your app that might be downloading/saving local files and check the container again for files you aren't cresting yourself but that you can flag to prevent backup
... View more
‎Mar 14, 2016
06:55 AM
1 Upvote
Whether you are explicitly writing files to applicationStorageDirectory or documentsDirectory or some process is putting files there as part of temporary file usage, these folders and their contents will be part of an iCloud backup. After running your app locally on a device, use an app that allows you to explore your app's folders, or you can use XCode's built in Devices tool to explore your app's container and confirm what files are ending up in these folders. You don't need to necessarily stop using these folders or putting files there, you just need to mark them with 'preventBackup = true' from the File class: File - Adobe ActionScript® 3 (AS3 ) API Reference This will solve the problem of them being considered for iCloud backup (you can just set this on a parent folder and it will prevent any files or subfolders within that folder from being considered for backup)
... View more
‎Jan 08, 2016
03:27 PM
The latest beta release notes mentions the new use of iOS 9 and iOS SDK Upgrade and with support for App Transport Security (ATS) you include a sample exceptions to the default behaviour of: <iPhone> <InfoAdditions> <![CDATA[ <key>NSAppTransportSecurity</key> <dict> <key>NSAllowsArbitraryLoads</key><true/> </dict> ]]> </InfoAdditions> </iPhone> But you really shouldn't be recommending this global disabling setting. It is more secure for people to only downgrade on a per-domain exception setting as needed for the domains they know they are using, like: <iPhone> <InfoAdditions> <![CDATA[ <key>NSAppTransportSecurity</key> <dict> <key>NSExceptionDomains</key> <dict> <key>yourserver.com</key> <dict> <!--Include to allow subdomains--> <key>NSIncludesSubdomains</key> <true/> <!--Include to allow HTTP requests--> <key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key> <true/> <!--Include to specify minimum TLS version--> <key>NSTemporaryExceptionMinimumTLSVersion</key> <string>TLSv1.1</string> </dict> </dict> </dict> ]]> </InfoAdditions> </iPhone>
... View more
Copyright © 2023 Adobe. All rights reserved.
AdChoices