Hey guys, it's been a while!
I built several Flex/AIR/Starling games back in 2013-2015(ish) and just recently was able to get them all back onto GooglePlay (they had been removed for me not following up on Google's constant policy changes) - I was excited to learn I didn't have to rebuild anything, just sign some digital paper work essentially. Well, until I realized while Google placed my games live again, they wouldn't install on my modern Galaxy S10. Sooooooooooo, this thread begins lol
I have switched almost exclusively to Unity + C# since then and have been struggling to get my environment set back up for Flex/AIR/Starling - it seems like the landscape around these tools has changed a lot since I authored these projects. Apache owning Flex now, and AIR being updated by Harman, getting my old projects to launch was a project in itself! lol
I'm currently running Flash Builder 4.7 - where I have side loaded Flex with overlayed AIR 32 (at least I think) - and then I was attempting to use the latest Starling that I could find (2.6) but due to thousands of deprecations (if that is a word) I decided to use the original Starling that I had created these with. Not sure of the version, but all my errors go away lol
So I guess I have several noobie questions (my name still makes sense I guess LOL) - will having more modern AIR / Flex allow me to keep these older apps alive? Or is having an outdated Starling going to be my downfall? I don't mind going over the old code bases, I would just prefer not to.
Also, would there be anything drastically different between Flash Builder 4.6 and Flash Builder 4.7? I had to re-construct one of my older projects into a new project due to way too many very old caching issues (I thought it was working but turned out it was just running the old swf in my bin-debug and I was unable to get it to update) I'm curious because when I was finished recreating everything in a fresh project using all the same logic just updated AIR/Flex I now get a null object reference on boot up which is related to how I am handling the screen size. This code worked perfectly before and it seems like a race conditonal. So wasn't sure if this was an issue with 4.7 vs 4.6.
Sorry for being so vague, I can get down into the weeds if you guys are interested but I guess overall looking to see if I'm headed in the right direction here.
Thanks guys! Really appreciate it, and man being back in my old pipeline feels super nostalgic! 🙂