Harman Air SDK 33.1 won't package .apk

[steveRedMinnow]

I have downloaded and installed Harman's Air SDK v33.1. I am using Flash Builder 4.7 on a Mac and have created an .ipa file and have successfully submitted it to the Apple App store, but when I try to create an .apk file (32bit), all appears to work well at first, from Flash Builder's Progress view: it is building the workspace, then invokes the compiler. I then get the message that it is packaging but nothing happens. I do not see the packaging progress bar, I do not get an error message, it just sits there indefinitely.

If I revert back to version 32, the packaging progress bar displays and updates until complete and it does create the .apk. However, that version is not accepted in the Google Play Store anymore. So it appears that it has to be something in the 33.1 update. Has anyone else experienced this? What was your work-around?

Here is my environment: Mac Mojave Adobe Flash Builder 4.7 Feathers 4.11 (with initially Air 32 downloaded through Feathers SDK Manager) Harman Air 33.1 overlayed in above Feathers/Air directory using ditto command in Terminal

[kidgamez]

I am having this issue too

[ajwfrost]

Hi - can I check what version of the AIR SDK you're using here? 33.1.1.nn? There are some issues with code-signing of the binaries in the latest one (33.1.1.190) which might be behind this, are you able to check it with 33.1.1.98 (can be downloaded from the 'release notes' part of the website)?

thanks

[steveRedMinnow]

I have tried it with all 3 that are available for download now from Harman:

AIR 33.1.1.190 AIR 33.1.1.98 AIR 33.0.2.338

All allow me to create an .ipa but none create an .apk.

Neither of the following allow me to debug the app either: AIR 33.1.1.190 AIR 33.1.1.9

I get an error message saying there is an error with a screen size. (I can post error message in a following post if necessary but am not near my computer now)

I have also started to overlay the Air SDK using rsync instead of ditto but that hasn’t helped either.

On Jul 26, 2020, at 8:41 AM, Andrew Frost notifications@github.com wrote:

 Hi - can I check what version of the AIR SDK you're using here? 33.1.1.nn? There are some issues with code-signing of the binaries in the latest one (33.1.1.190) which might be behind this, are you able to check it with 33.1.1.98 (can be downloaded from the 'release notes' part of the website)?

thanks

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[teotigraphix]

33.1.1.98 borks as well for me, I set up ANT builds for now but it would be nice to just hit a button still, either way I can't create an apk/s on WIndows 10.

The interesting thing is, when changing the internal JRE, trying to compile a normal project results in some unstable state in FB, it seems like it's messing with internal FB - compiler source/library links of a project. (just a guess). I had to switch back to the default JRE to even get FB to compile again (after many restarts).

Just adding some noise but not like it matters, the FB is a dead horse. :)

[steveRedMinnow]

I have tried creating an Android version of our app again using the latest version of Harman SDK: 33.1.1.217 and I still get the same results. Flash Builder appears to start the process and then just hangs.

[PhilCase]

To make a 64 bit app you need to have the 64 bit version of Java 1.8.0_231 installed (and some environment variables set).

In "Flex Build Packaging", click on "Customize Launch".

add a command line argument of "-arch" after the 'target' parameter to allow you to specify the architecture.

-arch armv8 gives 64 bit support for Android.
-arch armv7 gives 32 bit support for Android.

I changed the JVM that FB4.6 was using previously to the 32 bit version of Java 1.8.0_231. I don't know if you can do that in 4.7. (I also could not build a 64 app in FB 4.6 - I've been looking at IntelliJ Idea and other IDEs for that, but may just be forced to use the command line for the packaging stage).

Harmon's 33.1.1.190 - appears to be giving me problems with the appearance of my components (in iOS in particular). I didn't know that there was a later library available, thanks for that. :)

[teotigraphix]

but may just be forced to use the command line for the packaging stag

I am using 4.7 just for coding and I ended up just writing ant build files that do everything, for the hours and hours this problem can waste, it takes about 2 hours at most to setup build/package/deploy files once and for all. :)

[steveRedMinnow]

@PhilCase, thanks for the info, but I have already set that up. I have been able to create 32-bit and 64-bit apps previously. It is just that the new SDK's silently fail in the process of creating both 32/64 bit apps for Android only. iOS compiles fine.

@teotigraphix - yes that is probably what I am going to need to do, since I have heard nothing from Harman, (even though I have a paid subscription for SDK updates). I am in a waiting pattern from my client for some other issues, so I have had some time to get some info on the problem. However, that window will close soon, so I will need to turn my attention to creating an Ant build. Thanks!

[PhilCase]

@teotigraphix. Thanks for the advice. I will try that :)