I hope every one of you conspiracy theory whining babies will be man enough to come back here and post a sincere apology when Adobe pulls this off, which I suspect they will. I will be first in line thanking them for their hard work. We all know that it is a smaller team than it once was, let the people do their work. I know if i was Adobe and was reading these forums, i would eventually start ignoring you too, they have serious work to focus on, they don't have time to play therapist to the world. I bet that there isn't a guy on this forum that could knock out a 64 bit compiler in a week. Everybody take a deep breathe. Adobe gave us a huge forewarning that flash was to be terminated. They will do the same with AIR if the time comes because that is good business. If you are so unbelievably unhappy with AIR that it is giving you nightmares, then switch platforms and go away. Otherwise, you just look like trolls trying to stir a pot, which I suspect many of you are because you have too much disdain for Adobe and AIR to actually be using their products. Let Adobe work, and try to do the same.

H

hferreira80

Inspiring

If I did conspiracy (freedom do speech) you are doing futurism

And what happen if you are wrong ?

I hope you are man enough to post a sincere apology.

P

PippoApps

Inspiring

Sorry folks, I am going to leave this discussion since it has evolved into a therapy session.

Wishing a happy 64bit Android to all

so long

H

hferreira80

Inspiring

They even did a reset on votes in the tracker!! It went from 120+ votes to 10... (so this on starling forum)

O

OMA2k

Inspiring

hferreira80 wrote
They even did a reset on votes in the tracker!! It went from 120+ votes to 10... (so this on starling forum)

What? Why would they do that?!

So not only they don't acknowledge the issue in the tracker AT ALL, but they also reset votes??!!

H

hferreira80

Inspiring

https://forums.adobe.com/people/Fr%C3%A9d%C3%A9ric+C. wrote
What would be the point in resetting the votes, exactly ? Either Adobe care about their image and communication about this issue, or they don't. But if they care, resetting some votes on a bugtracker issue would be pretty ridiculous, and doesn't make any sense. In that case, why not deleting the issue entirely? Let's try to keep some distance, I think you're taking it too personal.

I agree, there is no point in resetting votes, it makes no sense at all. But at this point, I can expect anything from them, since it also makes little sense to not drop a single line in the tracker or in the forums saying "we're working on these issues", and still this is what we got: Zero replies from anyone working at Adobe. Nothing!

Also, the 64-bit requirement wasn't something that was announced this year. It was announced back in 2017!

"64-bit support requirement in 2019
Platform support for 64-bit architectures was introduced in Android 5.0. Today, over 40% of Android devices coming online have 64-bit support, while still maintaining 32-bit compatibility. For apps that use native libraries, 64-bit code typically offers significantly better performance, with additional registers and new instructions.
In anticipation of future Android devices that support 64-bit code only, the Play Console will require that new apps and app updates are able to run on devices without 32-bit support. Apps that include a 32-bit library will need to have a 64-bit alternative – either within the same APK or as one of the multiple APKs published. Apps that do not include native code are unaffected.
This change will come into effect in August 2019. We're providing advance notice today to allow plenty of time for developers who don't yet support 64-bit to plan the transition."

The above paragraph comes from an announcement made by Google at the end of 2017, and as they said, they made it "to allow plenty of time for developers". Yet, the Adobe team has chosen to do nothing in these almost 2 years since then, so we are now at the final stretch before the deadline, with only a little more that 2 months to go.

And not only that, they are still remaining completely silent in the bug tracker and the forums, as if they were afraid of showing any kind of date commitment, as if they feared they might not make it in time. It's either that or they're just such a tiny team they don't have the time to spend even a few minutes to reply issues in the bug tracker. Either way, this is really worrysome.

The only replies we've had so far are time-wasting replies from fanboys who will blindly defend Adobe no matter what they do and just make excuses for them one after the other. Rest assured those posts don't make Adobe look any better, more like the opposite, because they are such senseless excuses such as:

Adobe shouldn't test their AIR SDK with the latest beta of an Operating System which will be imminently released in just a few months, just because that OS is not production quality code. They should only test when the OS hits final release instead, so users will have problems for months after its release (What?!)
Quote: "I don’t see anything here that is odd about Adobe’s communication", "there's nothing particularly unusual about the current level of communication" (Really?!)
Quote: "the SDK is receiving generous updates, projects like Starling and Feathers are receiving funding" (this is plain false, Starling and Feathers stopped received funding back in January, and the SDK is just having maintenance updates, not "generous" updates; calling them that is a stretch)
"Don't worry, they'll publish AIR SDK 33 in March, and AIR SDK 34 in June". Then, when they fail to publish AIR SDK 33 (and they still haven't to this date): It's perfectly normal, they don't have any obligation to stick to their own publish dates, they can release at any time they want, less than 3 months (now a little above 2 months) until the deadline with no news is perfectly reasonable, there's still plenty of time, stop your tantrum, Adobe owes you nothing! (no comment...)

Do those people who say stuff like that really think it makes Adobe look better? Actually, that makes it look like a mediocre company which will not stand behind their product and which can only count on fanboys to defend it.

AIR is a great technology, but this is such a sorry state of things, really.

Seems that I was misunderstood by some scared folks but, I can resume my previous statement with this statement "But at this point, I can expect anything from them" (it's not my words).

H

hferreira80

Inspiring

This is a great debate.

What ASWC says is true (or part of it is true) but what PippoApps says is also true.

AIR is an high productive runtime however part of that it's you, the developer.

Of course if you compare AIR with Assembly, AIR it's 10.000% more productive even if you are a Assembly Guru, however there are out there other options less productive as AIR but still at least 5.000% more productive then Assembly.

Xamarin allow you to code once and deploy even more options than AIR.

Flutter it's also an option if you like the very new cool new thing.

I have a web base application that I did years ago in 100% pure JS (yes, I said correctly), pure JS and I can say that I create a new page in a matter of minutes (a complex page with several options, grids, etc, etc ...).

I can also test without have to compile anything (so I can say than I can be even more productive).

H

hferreira80

Inspiring

You guys are so concentrate to see who have the reason that you forget the real issue.

You may have "trolling" all this time or you may be thought that is normal and the very last minute you will get an update and prove everyone that you where right or maybe freaking out and losing your mind BUT if you don't have a backup plan right now, it's your fault, simple like that.

zasflower2014

Inspiring

AIR fixes bugs in versions is OK, How many people use Android Q? And not compatible with the previous Android version of the program.

This is Google's own problem, not Adobe.

Win10 can run Win7 programs. Ios 12 can run iOS 10 app.

Because of what you want to do, global developers will write programs for it again. Who does Google think he is?
If Google writes all the programs on its own operating system, then when I say nothing.
An operating system, if no one writes a program for you, it is nothing.
System upgrades a version, the program has to be re-written once, you play developers?
If the operating system can't even be stable, what are you doing?

Z

ZachBJ

Known Participant

Correct.
While MS and Apple still have problems too, Google ways of developing things is way terrible than MS and Apple.

For instance, and we all know about is Chrome. This is the new IE of this century. Even in Chrome we can NOT disable video autoplay , not if we are not using extension.

To develop native Android Apps , we needs LOT OF resources during development. No, you can't use only 1Gb of RAM for using Android Studio + Gradle + Android SDK. You will have a lot more of it....for just creating "Hello Android".
4Gb is bare minimum so everything can runs bit smoothy.

Using Adobe AIR+Flex/Feathers, I don't need those beefy 4Gb to just develop simple "Hello Android" or even much complex one.

PC with 2Gb of RAM, Windows 10 still able to runs on and still able to do various tasks

In Android? We'll have struggle to install say Android O on device only 1Gb of RAM.... Even if you have 2Gb of RAM and then play those big mobile games...? You know what happened then.

while all know Windows is a desktop OS while Android is mobile OS.

I don't know how can mobile OS is hungrier than desktop OS in terms of memory?

Google is the master of resource HOG on almost all products they develop: Chrome, Android, YouTube, Gmail.. but the sad truth is we are using it all

I wonder if someday Google has serious competitor , may be things would change. [But who are Google serious competitor??]

I feel sorry for people that keep blaming Adobe on everything. Thats unwise.

L

Leo KanelAuthor

Inspiring

The issue with Android Q is that Adobe keeps using the Context.MODE_WORLD_READABLE on Android. This was deprecated in API 17 (Android 4.2) and deprecation means that at some point they will remove it. Google removed it on Android Q and thus all apps crash.

This is not something Google will fix on later versions of Android Q or higher. This is something that Adobe needs to fix as we are aware that this changed for about 6 years now. You can learn more about this
here.

Scanning any of your apps with an Android vulnerability analysis system tool will report:

"

[Critical] App Sandbox Permission Checking:

Security issues "MODE_WORLD_READABLE" or "MODE_WORLD_WRITEABLE" found "

This is also an easy fix, which makes things even worst. All they have to do is change MODE_WORLD_READABLE to MODE_PRIVATE. We did this years ago in all of our native apps.

Z

ZachBJ

Known Participant

So far I knew Adobe's style: they work silently and give us surprise.
I still remember when Adobe fulfilled requirements for Apple x64 iOS Apps.
CMIIW even at that time Unity didn't make it yet.

M

marcanw

Inspiring

Yep working on Adobe Air requires a lot of nerves but always an happy ending so far.

T

tidusf39939682

Known Participant

Still waiting !!!

L

Leo KanelAuthor

Inspiring

No worries mate, I bet adobe air team is working on it, this is why they don't reply to anything or release anything (as some people say in here..)

Unfortunately due to the stupidity / handling of the issue, my company decided to leave AIR and all new project will be made in Flutter an electron. Only legacy apps will remain in AIR, until they are completely retired.

The decision was made due to the fact that we have about 5 months before Android Q is officially released and 3 months before the 64bit restriction and we still have no reply from adobe that they will fix the issues. Out of respect for our more than 2million users, we are migrating everything. Sad days..

H

hferreira80

Inspiring

No surprises for me.

I'm only one and made that decision my self, a few weeks ago.

I have one app that I will refactor the layout completely (not because of this issue).

To do so, between do with AIR or change runtime, I decided to move out from AIR and I hope to start soon.

With this move, AIR Mobile will be ended for me.

However I will keep AIR on Desktop.

I'm not stressed with time because even after August, 32 bits apps will be available (without updates) and Android Q will be very new on a so fragmented operation system.

I decided to change not only focused on this issue but on the overall.

yoonesm68067284

Participating Frequently

"We are aware and working on it"

this is the hardest statement for Adobe in this days!

P

phillipkerman

Known Participant

OMG if this wasn't so sad I'd say this is one of the funniest threads I've seen in a while. Maybe some folks are "trolling" but there's also something called a fanboy.

All the theories of where it is, when it's coming, is it coming--all speculation. You can base it on the moon or some schedule or rational you want--whichever.

For my business interests I obvs can't accept the risk beyond the 4 month Android drop dead date.

FWIW, I believe I understood every intent from the non English speaker. [EDIT: had to fix my own typo yet English native.]

H

hferreira80

Inspiring

I understood that you understood what I mean, lol !!!

In a way, you were also "trolling"

...

Back to the topic, I believe the best to do is look to other options out there.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded