The Flex SDK 4.6.0 is pretty old by now, as it was released back in 2011. After that, it went open source, and you can now download the latest Apache Flex from here: http://flex.apache.org/installer.html Using the automatic installer, it will download the latest Apache Flex and will automatically overlay your choice of version of AIR (for Flex developers). You can even choose to overlay AIR 13 beta if you want. ... View more

Colin Holgate: Its build number is quite confusing though, and says it is 13.0.0.42. No idea why it jumped from AIR 4 to AIR 13. Apparently the jump is meant to get AIR to be aligned with Flash Player's current version number, which is also 13. I don't see the need, but whatever. Also, each new version will change the major version number rather than the minor one. So next AIR version after 13.0 will be 14.0, the following after that 15.0, etc... I don't see the point if the actual changes are of the same type as when AIR was advancing only the minor number (3.7, 3.8, 3.9...), i.e: No big changes, just some progressive enhancements. APW1993 escribió: As stated in my reply to OMA2k I'm getting the error "applicationVerificationFailed" when trying to install the ipa onto my iPhone. I'm getting this with both the Air 4 and Air 13 SDKs suggested. As Colin said, that message usually appears when using the wrong certificates and/or provisioning profiles. The provisioning profile has to match the UDID of the test device you're using. If it doesn't, you will not be able to install the IPA into a test device. ... View more

I don't get such a message. Try to download the latest stable version, which is 4.0.0.1628 http://www.adobe.com/devnet/air/air-sdk-download.html ... View more

Then just go to Help / Manage AIR SDK to use the new SDK (which should be unzipped in a folder). ... View more

What are you using? Flash Pro? Flash Builder? FDT? FlashDevelop? ... View more

Did you finally find a solution? ... View more

Colin Holgate escribió: Although it was only two months between 3.9 and 4.0, releases seem to be about 3 months apart. That would put the next non-beta some time in March I suspect. It used to be a bigger worry, because betas were watermarked, and you were not supposed to release apps that used a beta. These days it’s ok to use the beta for shipping apps, and there’s no watermark. In many ways it doesn’t matter whether it’s a beta or a release version that you use. Yeah, but still, I think Adobe should release a proper non-beta version of the updated AIR SDK before the next big version change (from what I read, next version of AIR will be called 13.0, not 4.1), because surely a lot of people won't know about this unless they read these forums and will still download the SDK from the regular AIR SDK page. Plus not all companies might be comfortable using beta software to publish their apps to the App Store, even if it's just a semantic issue and it's probably only "psychological" (though I guess beta versions are less tested; that's what betas are meant for, after all). ... View more

I've never tested that, but I can confirm the preventBackup argument works (at least I never had an issue with that). I usually use it with the files themselves, not just the directory. Also be sure to use AIR SDK 3.6 or higher (older versions don't have that property). Actually, you can only use the AIR 4.0 beta now (not the release version), or your app will be rejected by Apple as well for different reasons (outdated XCode version). The beta (4.0.0.1619) can be downloaded here: http://labs.adobe.com/downloads/air.html ... View more

Any ETA on the final non-beta version? Thanks! ... View more

Sorry, I didn't notice he meant the other way around. In that case, you still need an ANE, but I don't know about any readily available one. You might be interested in contacting with the author of this post: http://apache-flex-users.2333346.n4.nabble.com/Flex-Mobile-Share-image-from-gallery-td521.html ... View more

You can try with this ANE for Android: https://github.com/illuzor/Android-Sharing-Extension-ANE If you need iOS functionality as well, you have this paid extension: http://www.milkmangames.com/blog/tools/#iosgv Instructions for the latter can be found here: http://www.adobe.com/devnet/air/articles/goviral-ane-android.html http://www.adobe.com/devnet/air/articles/goviral-ane-ios.html ... View more

flexercised wrote: If you go to the release notes, there is a date and build numbers. Thanks for the tip. Still, I think it'd be best to put the build in the download page itself, instead of just "version 4". Or even better, since from now on subsequent versions of AIR will change the major version number each three months (like Mozilla), it'd make sense to change the minor version number when a minor update is issued (you know, what minor version numbers are actually meant for ). So this (now beta) updated version of AIR 4 could maybe be called 4.1 when it's released as final version. It'd be less confusing than still calling it 4.0. Anyway, I hope they don't wait until AIR 5.0 (due in a couple of months in theory) to release this update as final. ... View more

Hi. @MarkJ, if you're using Apache Flex, then you shouldn't use the files linked by Nimitja, but the ones at the bottom of this page ("AIR 4 for Flex Developers"): http://labs.adobe.com/downloads/air.html Best regards. ... View more

Thanks for the update! Will this be published as final non-beta version soon? Also, I'd like to suggest putting the build number in the SDK download page: http://www.adobe.com/devnet/air/air-sdk-download.html There it just says "version 4", but no build number. The build number is important because in the past there have been lots of minor updates with no change to version number, only the build, and the only way to know for sure is to download the ZIP/TBZ2 file over and over each time you're not sure of what version is up. That's a waste of everybody's bandwidth, including Adobe's. So it would be a good idea to specify the full version, including build number. Best regards. ... View more

I would recommend against using useNative = true in Windows, because that means the behaviour and presentation of the page is very unpredictable, since the user can have pretty much any version of IE from 6 to 11 and beyond. That's more than a decade worth of different (and some really old and buggy) versions of Internet Explorer. The embedded WebKit in AIR could use an update (it's a bit old), but it's still a lot better than the wild territory of native IE ;-). I'm glad the AIR team listened to us and in AIR 3.9 they gave us back the option to not use native IE in Windows (in some of the previous versions, such as AIR 3.6, 3.7 and 3.8, only the IE engine was available to StageWebView, which forced me to use AIR 3.5 for Windows versions of my application, since the IE engine provided all sorts of problems). Anyway, I don't understand your post very well. First you say "is working and on mobile but not on desktop AIR apps". From that I get that your page is working on mobile but doesn't work properly on desktop, but then you say "on mobile it seems that the cookie/session is not found". That contradicts the other sentence, since now you're saying it doesn't work properly on mobile. Which one is true? ... View more

You can’t add them in the publishing settings, but you can add them in the XML. You don’t have to use the command line. For icons, yes, but for other things (for example the new faster iOS packaging engine) you have to add an extra argument (-useLegacyAOT no). It could be useful to have the ability to add extra custom arguments. As for ADT itself, even if you fully understand it there are so many parts to it, especially when you have external media in your app, that there is such a lot that could go wrong. I like not having to use ADT directly. I usually use either batch files or ANT scripts so I only have to care to get the command line right once. ... View more

spinlight escribió: OMA2K, yes I'm a developer and can figure out the command line.   That's good . I mentioned it because earlier in this thread there was someone who said that he "really didn't have the skills to use the command line", as if it were something really hard, and insisted in doing it from CS6. I think if someone can code, there shouldn't be any problem to type a few lines in a CLI. Well, in your case you're trying to use CC, but unfortunately, as far as I know, even the very latest version of Flash Pro CC (13.1.0.226) still does not support iOS 7 icons. Not sure why; they should at least have added those icons in the latest December 2013 update. Anyway, I don't think they should remove packaging functionality from Flash CC, but maybe make it more transparent and customizable, so you can change the ADT command line as needed (maybe in an "Advanced settings" tab, or something like that), so if new command line arguments are added, you can still use them from Flash. IIRC, you can add arguments like that in Flash Builder and FDT, which is the best way to code an AIR project. ... View more

Sorry, I can't help you with that, since I always use command line scripts to compile. That read-only stuff was just a kludge anyway. If you're still having problems, you might as well learn how to use the command line method. You're supposed to be a developer, so it should be a piece of cake for you ... View more

I also would like to know this. Does this new policy affect Adobe AIR applications? ... View more

Grallator wrote: @OMA2k, I'm afraid on not on CC - I use CS6. I think it'd be nice if Adobe could issue and update fix for this. Subscription is a nice business model for Adobe, but leaves the faithful still wanting a CS6 approach in the lurch. Well, since even the just released 13.1 update of Flash Pro CC still does NOT support the iOS 7 icons, it's even less likely to have that support applied to CS6, unfortunately. At least, there are several workarounds (editing the descriptor and making it read-only, or compile using the command line). ... View more

Grallator escribió: Not a helpful suggestion I'm afraid but I'm also having issues with CS6 and iOS7 requirements. Please Adobe fix this and give us an update. We supported your software, even through the dark days of the App store not allowing Air apps. Please give back and give us an air SDK we can use in CS6 (and others)! Just use the command line ADT tool, it's not that difficult. If you don't find your way around, I can provide a few batch files that might help. Still, I can't see why the latest 13.1 update of Adobe Flash Pro CC just released a few days ago still does not include the iOS 7 icons. This update would have been a very good opportunity to add them to Flash Pro. ... View more

rodolfo1216 escribió: I used it in Flash CS6 to create my .ipa file.  The Icon area did not contain fields for icons of size 120, 76 and 152px. After submitting it to Apple I received the same error seen above. I guess the problem is CS6 removes those icons when publishing or changing settings. Can you check if those icons are still present in the -app.xml descriptor? If they were removed, then re-adding them an using Colin's suggestion about write protecting the file should do the trick, though each time you need to change something in that file, you'll have to remove the read-only attribute and then add it back. Not very practical. rodolfo1216 escribió: I was wondering what the latest info was on this issue.  I really don't have the skills to use the command line.  Is there a simpler solution?  Really frustrated.   Appreciate any help you can give. I can't believe a developer can say he doesn't have the skill to use the command line. If you can program in AS3, using the command line should be a piece of cake to you. You just have to go into your directory using the "cd" command and then run ADT with Adobe's instructions. Not hard by any means. Flash will always be behind what the latest version of AIR can do, so you should learn how to use the command line compiler for those cases. Even the current version of Flash CC doesn't support iOS 7 icons nor Android high density icons, and it was released half a year AFTER that type of icons were introduced in Android (but before iOS 7). ... View more

What's the real difference between listing all of the languages or only the supported ones? Your app is not listed for users of the unsupported languages? I hope not, because sometimes we get new customers which use languages still unsupported in our app, and then we add localizations for their language after subscribing to our service. Would it hurt visibility not to list all languages? ... View more

Colin Holgate escribió: By screenshots I really meant splash screens. The image you see as the app launches. Ah, ok, I see. Yes, the splash screens need to be inside the IPA. Do you know what's with the 48 / 50 pixel icons? ... View more

Colin Holgate escribió: With 3 - 5 screenshots, 18 icons, plus whatever other external files and folders your app requires, it ends up being quite a complex line. Screenshots? Do you really have to include screenshots in the compiled IPA? If you do, you don't have to upload them into iTunes Connect? I don't think so, they're probably just bloating the IPA with no actual use of the pictures. I've never included screenshots in the ADT command line (I manually upload them into iTunes Connect) and everything seems to work fine. Also, I'm seeing everyone is including the 512x512 and 1024x1024 icons, but Apple says specifically "Do not include this icon in your app bundle if you are not distributing your app via ad-hoc distribution" ("this icon" = the iTunesArtwork icon in both sizes 512 and 1024) https://developer.apple.com/library/ios/documentation/iphone/conceptual/iphoneosprogrammingguide/App-RelatedResources/App-RelatedResources.html So if you're uploading for app store you shouldn't bundle those bigger sizes with the IPA, since you're already manually uploading those icons through iTunes Connect. I guess if you do there's no problem, but why bloat the IPA even more if it's not needed? Plus if you're uploading an iPad app (non-universal), iPhone icons are not needed either, so if I'm not mistaken, these are the icons needed currently for an iPad-only application compatible with both iOS 7 and iOS 6 (and older) and both retina and non-retina screens:   <!-- IOS 7: App icon (iPad) -->     <image76x76>icons/icon_76.png</image76x76>     <image152x152>icons/icon_152.png</image152x152>   <!-- IOS 7: Spotlight search results icon (all devices) -->     <image40x40>icons/icon_40.png</image40x40>     <image80x80>icons/icon_80.png</image80x80>   <!-- IOS 7: Settings icon (all devices) -->     <image29x29>icons/icon_29.png</image29x29>     <image58x58>icons/icon_58.png</image58x58>   <!-- IOS 6: App icon (iPad) -->     <image72x72>icons/icon_72.png</image72x72>     <image144x144>icons/icon_144.png</image144x144>   <!-- IOS 6: Spotlight search results and Settings icon (iPad) -->     <image50x50>icons/icon_50.png</image50x50>     <image100x100>icons/icon_100.png</image100x100> The above XML is based off the aforementioned Apple document. Maybe the Adobe AIR documentation about icons should be changed to reflect the new iOS7 icons: http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac1e63e3d129907d2886-8000.html BTW, I've seen that this AIR document lists a special non-iOS 48x48 icon, with a note saying "AIR adds a border to this image and uses it as a 50x50 icon for spotlight search on lower resolution iPads". So if AIR adds a 2px border to the 48x48 pixel icon, thus converting it to a 50x50 icon, then why does it accept another 50x50 icon as well? It's also listed as being for "Spotlight search for lower resolution iPads" so it serves the same purpose. If both 48 and 50 pixel icons are used in the descriptor, which one of the two icons are used, then? I just tested Spotlight and searched for an old version of my app (which uses the 48 pixel icon, not the 50 one) in an iPad 2. I've seen that the icon for my app actually looks smaller than the rest of apps in the iPad. I suppose that's because it's the 48 pixels icon + 2 pixel border. What's the point of AIR adding a 2 pixel border to a 48 pixel icon instead of only accepting the 50 pixel icon straight away? Why not just use the 50 pixel icon? I suppose I'll skip the 48 pixel icon next time I upload to the App Store, and use the 50 pixel one instead. There's no point in having my app icon look a different size than the rest of apps (even if it's only in the Spotlight search feature). It looks as if the icon were designed wrong, when it really wasn't. Ah, the AIR document also confirms the 512 and 1024 icons are not needed for the App Store: "The 512-pixel PNG file is used only for testing development versions of your application When you submit the final application to the Apple App Store, you submit the 512 image separately, as a JPG file. It is not included in the IPA." ... View more

Well, I know that AIR's ADT can install apps with "adt -installApp -platform ios -package myapp.ipa". That's in fact what I use to install my test apps in iOS devices. But that install process is really using an iTunes library to install apps. Actually, it doesn't even work if iTunes is not installed in the system. So it's iTunes the one that "refuses to install" it. When I have this problem when trying to install with the ADT command line tool, in that case even opening the iTunes app and trying to installing the IPA through its graphical interface doesn't work. ... View more

I suppose you meant they are NOT dispatched on mobile devices. Which is a pity, because they'd make things easier. I've filed a feature request in bugbase. Please vote if you're having the same issue: https://bugbase.adobe.com/index.cfm?event=bug&id=3648849 ... View more