1 person found this helpful
Have you heard of the expression, "Tampering with this product will void the warranty"? :-)
There's no guarantee that the process you went through to remove the air. prefix didn't break the part of the app that automatically triggers the AIR runtime request. You're basically doing things that aren't supported, so I doubt you'd find an answer to that question from Adobe.
Personally, I would look at using the captive runtime feature of AIR 3.1+ and then you won't have to worry about the user needing to download the runtime separately. If it's really that important for you to remove the air. prefix, captive runtime should fix this problem.
thanks for the reply!
adobe actually does tell you that you can optionally remove the prefix (and they even give instructions) on how to do it in their "Building Adobe Air Applications" pdf.
you would think they might mention the slight hiccup that it can cause (if this is causing the issue).
i enjoy your tutorials by the way. keep em coming please!
Hey Brad, did you ever get the chance to remove the prefix as well as include the captive runtime feature? Let me know. I was able to remove the prefix from the application without any bugs and package my app with captive runtime but not at the same time.
hi. i never did try that but i didn't think it would be a problem. i would create the apk with captive runtime. then rename it. sounds like this is what you did already though. just in case this helps, here is my method for renaming an apk package name:
let us know if you ever end up getting something to work.