›

Bogus crash report upon rejection

MagnesusMagnesus Posts: 304Member
edited July 2013 in General Development
My game was rejected for a crash not related to my game judging by the crash report (and the fact that I tested the game thoroughly on an OUYA before submitting). :|
Fragments of the crash report (completely not related to my game):
java.io.FileNotFoundException: /data/system/entropy.dat: open failed

java.net.ConnectException: failed to connect to www.filepicker.io/174.129.254.207 (port 443): connect failed -- WTF? I don't even know what filepicker.io is

E/OUYAStoreCacheTickler( 592): Caused by: libcore.io.ErrnoException: connect failed: ENETUNREACH (Network is unreachable) -- I've tested my game also when network is off - because it looks like the test OUYA didn't have network connection - and it works and doesn't crash!

I'm mad because it will postpone a really important and huge update to my game. If the testing is so not thorough then maybe it would be better if there was no testing at all (Google Play works like that)? Or if there really is some issue a full information about the device state should also be included and relevant crash report (Samsung Apps works like that, they give great reports and even screenshots!). The one attached has no useful information at all.
Post edited by Magnesus on

Comments

  • dra6onfiredra6onfire Posts: 91Member
    I would suggest that the crash report you are looking at is probably a misdirect. When I was suffering crashes during testing, several times this type of stack trace was the most recent stack trace in the logcat but further up the logcat was the actual failure from my app. The stack trace the you are seeing above seemed to be a side effect of a separate thread crashing after my app actually crashed. See if they will send you the full logcat from the test.
  • MagnesusMagnesus Posts: 304Member
    edited July 2013
    Well, my app doesn't crash at startup under any sane circumstances. And their logcat report was very, very long, still not having anything to do with my app. I suspect their test device (it might be an automatic test) was compromised by some earlier test (for example some earlier tested app left a memory leaking thread running).
    Post edited by Magnesus on

  • PiersPiers Posts: 680Member
    @Magnesus PM me with your game title and I'll have a look.  It's possible it wasn't your app, let me take a look.
  • MagnesusMagnesus Posts: 304Member
    PMd. Thanks.

  • PiersPiers Posts: 680Member
    @Magnesus sorry to say yes your rejected version crashes on launch.  I flashed my OUYA to 1.0.365 (current release) and wiped all user data, side loaded your game; crash on launch.  Side loaded another game; no problems. 

    Hope the new submission is all sorted, but yes this was a valid rejection.
  • MagnesusMagnesus Posts: 304Member
    Very strange. It doesn't crash on my OUYA. Can they provide more details? Actual logcat instead of that mess that was attached to the report?

  • MagnesusMagnesus Posts: 304Member
    edited July 2013
    I've tried everything to crash it (also 1.0.365, also wiping user data, even smashing buttons at start and checking without controller, without WiFi connection, removing my test payments...) and I just can't. Did you use the latest APK that is in the system? (I've uploaded one later - but before creating the thread here - thinking maybe the one before got corrupted)

    PS. The game just got rejected, by this time for some other reasons (that didn't cause rejection last time). It doesn't crash now apparently (although I haven't changed anything). Get your testing team sorted out, guys. It's very unprofessional. :/
    Post edited by Magnesus on

  • PiersPiers Posts: 680Member
    edited July 2013
    @Magnesus Just got this, but sounds like crash is gone on your new version (I checked the rejected) so that's good!  What reason(s) for rejection now?
    Post edited by Piers on
  • MagnesusMagnesus Posts: 304Member
    Some minor overscan area isssues. That weren't a problem before.

  • MagnesusMagnesus Posts: 304Member
    edited July 2013
    To be honest I give up for now. Another rejection. This time because I don't lock things that are already purchased (it's a donation so I assume it can be bought several times - since the server allows it!) and the server can't do that itself. Lock it on the server side if it's not allowed, for the gods sake. :/ Maybe I'll update in a few weeks, after vacation. I don't have time right now to deal with such slow process.
    Post edited by Magnesus on

  • MagnesusMagnesus Posts: 304Member
    OK. Yet another new version was approved today. Much faster review process than normally. Thanks everyone.

  • PiersPiers Posts: 680Member
    :)
Sign In or Register to comment.