Anyone? I can find absolutely nothing about how I could fix this error, the message is incredibly not-descriptive, and I have reason to believe that it might even be something going wrong on the Ouya servers' end - maybe this isn't even something I can fix, in other words.
I'd love to be able to publish this game to the Ouya! It would be great to get an answer from a real Ouya developer who could shed some light on this. (Or anyone from the community who knows what this could be.) Thanks!
My game has been finished and shippable for over a week, and I haven't gotten any reply from trying to conact Ouya support yet...
The error message I'm being shown gives me no information and AFAIK is due to an error on the Ouya servers and their Ruby scripts that validate APKs - even though my APK is valid so far as I know (it runs perfectly on the Ouya).
E3 is over - I'm bumping this in hopes that an Ouya engineer will see it here. And could maybe tell me what on earth this error means and what, if anything, I can do on my end to resolve it and release my game?
It seems like it would be good for Ouya to be able to say "Yes, you can make games in Flash for the Ouya, and in fact here's one that shipped." So far as I know this game is the first one made with Flash (AIR Mobile for Android) that has been finished and shippable - at least I haven't heard of any others...
I forgot to add that I have already tried deconstructing the APK generated by Flash Builder/AIR Mobile, and re-building and encoding the APK properly using the Android command-line tools. When I was done, I submitted and got exactly the same error. I've done everything I know how, and need support from the Ouya back-end team to know what about the APK is invalid (if anything).
I did, Piers fixed the problem that was happening with APKs produced by Adobe AIR; I think they were missing a file that the verification process had assumed was present.
...I'd assume something different (but similar) is happening in the case of your APK. For me it was impossible to know what was up until I got help from Piers and some other Ouya developers, since the error is on the back end.
Comments
...I'd assume something different (but similar) is happening in the case of your APK. For me it was impossible to know what was up until I got help from Piers and some other Ouya developers, since the error is on the back end.