Agree as well. I think it was @William Spence that brought up the strong point that many educational institutions for reasons I personally would disagree with, may have chosen iOS devices, like iPads, which age like the rest of us. For Adobe to preemptively cut support to these users, especially before Apple does, is, well a selfish move imo. We're always talking about 5% market share or 20% market share, but is that all it's really about? There are potentially cases where educational apps are used by kids in rural communities that struggle with funding and can be profoundly affected by decisions like this. With the % math of how many users out of millions they get lost. They may only be 100 or 200 kids but when they're told their iPads won't work and they need to raise funds for new ones - is that really fair, is that how we want our technology, our software, to enable and enrich? Was it a poor choice for someone to choose Apple devices in that scenario, maybe, but that happens. This gets to a larger discussion about Apple and it's own brand identity, which is sort of like a Cadillac, and as we saw with the recent battery issue, there appears to be some planned obsolescence going on (not the only tech player that's doing this I'm sure). They have their reasons. But really if you step back, having the latest, greatest, fastest hardware doesn't really change the content and quality of the app. If the app is doing some powerful A.I. computation / modelling or is all about the latest graphics maybe, but that's not what most really useful apps do. It's certainly not the case with educational apps. So if I was sourcing for educational settings I think I'd look for the Toyota Corolla (support and hardware-wise) instead of the Cadillac. Just my two cents on that. All this deprecation of hardware is also terrible for the environment. I got a bit tangential from the thread there for awhile - this thread was very active and I've been thinking about it a lot. Just wanted to share some thoughts. ... View more

Encountered a new bug with air 29: Embedding otf font broken in air 29 My project won't compile with an embedded font. ... View more

Correct, I got that error without using any location services. ... View more

I see, thanks for clarifying. Hopefully the workaround can be shared too. ... View more

Hi Colin, Fingers crossed that workaround can be shared. What's the issue with iPhone X, before this error happened I'm pretty sure I was able to run it in the sim? Thanks for the reply. -cybo ... View more

The other issue with 29, not sure if this is fixed in beta 30, is that the iOS simulator on OSx is broken: iOS simulator broken with new updates Haven't received an update on that from the air team yet. ... View more

Hi Pravishti, Is there any update on this issue or a workaround? The simulator is a really powerful tool for testing on various iOS devices. -cybo ... View more

I sincerely applaud your ability to admit your wrong and change your stance. Correct me if I'm wrong but most forums have sticky's asking users to do that exact thing - read the complete thread to prevent the thread from becoming bloated and redundant. However, I'll admit that I too am guilty of not always doing that or just skimming it over. Time is in short supply these days. No sarcasm here. Hope you have a great day. ... View more

I have to point out that this point was made pages ago in the thread. Thanks for continuing to engage Flipline, you are patient indeed. ... View more

You didn't read the whole thread then. I did make my points to zwetan, in point form after he insulted William by saying he didn't understand text and needed pictures. And no I have not done what he did by insulting someone I disagree with because I'm so zealous about my point. I believe it's warranted - stand up or sit down and let people get away with it is my opinion. Don't get tribal over a guy that clearly is triggered for no reason. zwetan's attitude is toxic to the thread and he is terribly redundant if you actually read it all. ... View more

I hear you, but the guy talks disrespectfully to other users and needs to be called out. Secondly, the signal I'm sending is don't waste your time reading his posts because he's just repeating himself ignoring the obvious points others are making. To be clear, I'm not saying I presume he fails at most interviews because of his bad English, I would never be prejudice in that way, I'm presuming he would fail due to his deplorable personality. Providing he doesn't continue to demean other users to desperately try to sell his point a view, I won't say anything. ... View more

Honestly, don't even read zwetan_uk's posts, he's redundant and ignores what's being said. It's just going to hurt your brain. The guy is seriously obtuse. zwetan_uk, for a guy with some pretty terrible English it's cute how condescending you are. I bet you fail hard at most interviews. ... View more

Let me try to help William. I'll use short sentences since zwetan is pretty condescending in his poor communication. I think he gets a bit lost. Here zwetan, point form for you with minimal punctuation: - Apple allows 32 bit + 64 bit hybrid apps to be submitted currently to continue to allow 32 bit devices access to new apps and updates, even if it doesn't support 32 bit only going forward, in fact, I don't see a use case of only submitting 32 bit apps - iOS 11, which isn't supported on 32 bit devices, does not support 32 bit apps - devices that don't support iOS 11 are still in use - developers want the ability to still support 32 bit devices as xcode currently still does Let me know if you need pictures zwetan. Also, maybe try decaf. ... View more

Wait, you are saying that Apple's roadmap will be such that OSX will be 64bit exclusively, yet that really has nothing to do with iOS. Apple has not dropped support for 32bit devices running iOS, but by doing this with the air SDK you have preemptively done just that. Correct? ... View more

Agree this is a BAD choice for Adobe air. This is shown by the fact that xcode creates a hybrid 32/64 ipa by default to support 32bit devices as well. It seems that Adobe should try to support 32bit up to the point that those devices are considered deprecated. I don't think iPhone 5 especially would be considered deprecated at this point. It's likely a resource and hours billable thing. I would imagine that for the SDK developers every fix and change they make needs to be done twice for each architecture, making it require twice the hours to build. That's a guess. If it's not the case and much easier it would baffle me why they would do this. I think until that graph shows < 5% users affected, they shouldn't even consider such a move. ... View more

I've been following it, but haven't read every post in detail. I agree as I said in my last post, Adobe should support 32bit until the devices are considered deprecated. But if AIR 29 is working with the workaround, that's a good thing. It could break again as it does working with Apple's constant policy changes and as you said then you'd be forced to use AIR 30. It does seem like Adobe didn't want to put the hours in to support both bit architectures in their SDK. I can sympathize that it's probably hair pulling work trying to constantly satisfy Apple requirements. It's almost as if they make them just to keep it tough for the Adobe staff lol. Hopefully enough pressure will have them reconsider the 32 bit support. I'll add my support to the thread you've linked. ... View more

Right, though we did find a workaround with the latest manifest adds. I see your point. But to make clear, how far back can we currently go with the air SDK and still be approved by the apple store? If it's pretty far back that should offer some comfort. Until 28 won't be accepted by the store, I wouldn't really panic. That being said, it seems that Adobe should try to support 32bit up to the point that those devices are considered deprecated from a developers point of view. I don't think iPhone 5 especially would be considered deprecated at this point. ... View more

Wait, so to confirm. If the future SDK's don't support the 32bit devices, isn't it still possible to update those apps with an older SDK like 28, that does support 32bit? You obviously won't get the latest fixes and enhancements, but wouldn't updating still be possible? ... View more

I see. I assume there is a new tracker bug for this issue then. Is it still the case that all air apps require full network access? I remember this was something to do with the captive runtime but now it's always included in the builds. A little paranoid with privacy issues with all that's going on in the news. Be nice to see an official statement from adobe regarding the SDK and privacy. ... View more

Thanks for clarifying. It does seem odd that adobe closed the tracker for this exact bug, and you're saying it's actually not fixed and you need to use the InfoAdditions hack. Do you see any reason for suspicion for privacy issues for our users that adobe may actually be using location information within the SDK itself? ... View more

This is confusing to me, so you are saying that with v29 some of your apps are approved and some are not with this same error? So this wasn't fixed in v29 sdk then? It seems adobe said it was in the bug tracker here: https://tracker.adobe.com/#/view/AIR-4198623. It looks like v29 is a official release and not a beta right? ... View more

Will try this when I need to submit again. We don't need to be worried about privacy here do we? I mean, adobe isn't grabbing location data from our users behind our back is it? That would be terrible. ... View more

I have this exact same issue. No ANE's, previous build was accepted and my app certainly does not use any location information. Really hope they come out with a fix soon for this I've already missed a deadline due to it. ... View more

Hi Pravishti, Any update on this issue? -cybo ... View more

Thanks Pravishti. Appreciate the hard work of you and your team. -cybo ... View more

Perhaps we can elevate it to the bug tracker? There must be lots of users experiencing this if it's not isolated to us. ... View more