#Error 1065 rte player pro#
So the AIR SDK has some hardcoded folder names in its DLLs, and Flash Pro CS5.5 changes AIR settings behaviour based on an English string which is shown to the user in the menus, instead of using an ID or any other variable.PUBLIC SERVICE BROADCASTING in Ireland is facing a “genuinely existential moment”, an Oireachtas committee has heard. So you're changing the application behaviour based on the content of a string rather than an ID?! What about localization? I haven't tried localized versions of Flash CS5.5, but I suspect that string can't be translated, or else that settings window won't work. The only problem now is that you can't have 2 iOS options coexist (2.7 and 3.0) so you'll have to move the "AiriPhone.xml" file out of that folder to use the new XML for AIR 3.0 for iOS.
If it's "AIR for iOS", then Flash presents the appropriate options for iOS in the "AIR for iOS Settings" window, but if that string is anything else than "AIR for iOS", then the settings shown are the AIR desktop ones. It seems Adobe Flash CS5.5 looks for this string.
The problem with the old XML was that it had a other than "AIR for iOS" (I had written "AIR 3.0 for iOS" to differentiate from the old version).
I've uploaded a new iOS_AIR3_0.xml file replacing the old one in the same MediaFire URL linked above (you'll see it has newer date than the other files). Well, I hope those XML files are useful to somebody and avoids further frustration.ĮDIT 2: I've realized the XML for iOS didn't work properly.
#Error 1065 rte player update#
I've wasted A LOT of hours in this (more than half a day), with what should have beenĪdobe should make a SDK installer so we do not have to be tinkering with all theseĮrror-prone procedures each time a new update is released!
#Error 1065 rte player upgrade#
I know Adobe AIR is meant for developers, not for final users, but still,Īll these not very well documented upgrade procedures are a pain in the ass. I think AIR SDK installations should be a lot more straightforward than this! It's hardcoded into a DLL, so that can't be changed. That's because of how the publish settings work in Adobe Flash. Yes, you have to change that inside the AIR2.6 folder even if the SDK has been put into AIR3.0. "c:\Program Files (x86)\Adobe\Adobe Flash CS5.5\AIR2.6\samples" folder, Inside that folder, copy the file "airglobal.swc" located at "c:\Program Files (x86)\Adobe\Adobe Flash CS5.5\AIR3.0\frameworks\libs\air".įinally, you will have to keep the file "descriptor-sample.xml" in the Inside the folder "c:\Program Files (x86)\Adobe\Adobe Flash CS5.5\Common\Configuration\ActionScript 3.0" create a new folder named "AIR3.0". My XML files point to that new "AIR3.0" folder. It's best to use a different separate folder. Then, make sure you've unzipped the AIR 3.0 SDK into the folder "c:\Program Files (x86)\Adobe\Adobe Flash CS5.5\AIR3.0"ĭo not overwrite the contents of the "AIR2.6" folder, as suggested by the "Overlay AIR SDK" article (). Put all three files into the folder "c:\Program Files (x86)\Adobe\Adobe Flash CS5.5\Common\Configuration\Players" These are the steps needed to get AIR 3.0 running properly: I've created some modified XML files with the profiles needed for AIR 3.0 and Well, after much tinkering, I think I've finally found a way to finally make it work!. Please let me know if that works for you as well.ĮDIT: It seems the Adobe Forums are down right now, so I'm posting my answer here: I've explained it here in this post in the Adobe Forums: I've also had this issue and spent a lot of hours trying to figure it out, until I've found a solution that works for me.
0 kommentar(er)
