Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

App tested OK, apple approved, but crashes for all users who download from app store?

Discussion in 'iOS and tvOS' started by JonnyHilly, Mar 14, 2014.

  1. JonnyHilly

    JonnyHilly

    Joined:
    Sep 4, 2009
    Posts:
    749
    So we have existing app in app store, made second update for it. Nothing special changed in our build machine, same Xcode (5.0) etc.. maybe we had a Unity point update update since last update.

    Tested extensively with internal dev team, (with both debug and release, and test flight builds) then external test team 1, followed by a second test team (that double checks the first test team)
    Submitted to apple, and it passed, and went live to app store...
    now for everyone 100% of users that downloads it, it crashes. How can this be ?
    Had to pull it from app store.

    Built with latest unity 4.3, with (almost) latest xcode, 5.0 on Mac

    Here is crash log (note I removed the bundle id and app names manually, they are correct)
    There are 2 errors mentioned and a strange word I wouldn't expect to see 'sandbox'
    Q. why does it say 'sandbox' on line 1??

    any thoughts appreciated, thanks in advance

    Mar 14 10:08:46 QAQ-iPhone5S-01 kernel[0] <Debug>: launchd[245] Container: /private/var/mobile/Applications/9810A9BD-C625-41A2-95A1-034CFF74E561 (sandbox)
    Mar 14 10:08:46 QAQ-iPhone5S-01 networkd[81] <Warning>: Analytics Engine: double ON for app: com.xxxxxx.xxxxxx.xxxxxxx
    Mar 14 10:08:46 QAQ-iPhone5S-01 appNameHere[245] <Warning>: -> registered mono modules 0x1aaa550
    Mar 14 10:08:46 QAQ-iPhone5S-01 backboardd[31] <Error>: HID: The 'Passive' connection 'appNameHere' access to protected services is denied.
    Mar 14 10:08:46 QAQ-iPhone5S-01 appNameHere[245] <Warning>: searching for iCloud document directory and found this: (null)
    Mar 14 10:08:47 QAQ-iPhone5S-01 awdd[247] <Error>: CoreLocation: CLClient is deprecated. Will be obsolete soon.
    Mar 14 10:08:47 QAQ-iPhone5S-01 backboardd[31] <Warning>: CoreAnimation: updates deferred for too long
    Mar 14 10:08:47 QAQ-iPhone5S-01 backboardd[31] <Warning>: CoreAnimation: timed out fence 2df07
    Mar 14 10:08:47 QAQ-iPhone5S-01 SpringBoard[16] <Warning>: CoreAnimation: failed to receive fence reply: 10004003
    Mar 14 10:08:48 QAQ-iPhone5S-01 ReportCrash[248] <Notice>: ReportCrash acting against PID 245
    Mar 14 10:08:49 QAQ-iPhone5S-01 ReportCrash[248] <Notice>: Formulating crash report for process appNameHere[245]
    Mar 14 10:08:49 QAQ-iPhone5S-01 com.apple.launchd[1] (UIKitApplication:com.xxxxxx.xxxxxx.xxxxxxx[0x5c][245]) <Warning>: (UIKitApplication:com.xxxxxx.xxxxxx.xxxxxxx[0x5c]) Job appears to have crashed: Abort trap: 6
    Mar 14 10:08:49 QAQ-iPhone5S-01 backboardd[31] <Warning>: Application 'UIKitApplication:com.xxxxxx.xxxxxx.xxxxxxx[0x5c]' exited abnormally with signal 6: Abort trap: 6
    Mar 14 10:08:49 QAQ-iPhone5S-01 ReportCrash[248] <Notice>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/appNameHere_2014-03-14-100848_QAQ-iPhone5S-01.ips using uid: 0 gid: 0, synthetic_euid: 501 egid: 0
    Mar 14 10:08:49 QAQ-iPhone5S-01 mc_mobile_tunnel[244] <Notice>: (Note ) MC: mc_mobile_tunnel shutting down.
    Mar 14 10:09:35 QAQ-iPhone5S-01 backboardd[31] <Notice>: ALS: SetDisplayFactor: factor=0.0500
     
  2. hippocoder

    hippocoder

    Digital Ape

    Joined:
    Apr 11, 2010
    Posts:
    29,723
    Sounds like poor integration of middleware, untested with devices that might have no internet access or the same services. You need more testing.

    It might have triggered an exception in testing. Are you sure you've tested this app enough? Because Apple isn't QA. They'll run it once and that's it.

    App tested OK with an incredibly poor testing method it seems. Go back and test it properly using Testflight and some proper testers, scan each part. Play it unexpectedly: take a call, interrupt it at unexpected times with the home button and so on.
     
  3. JonnyHilly

    JonnyHilly

    Joined:
    Sep 4, 2009
    Posts:
    749
    Unfortunately that was not the case... I don't think you read the post.
    This was via a major publisher, tested on all devices, all OS's, and two separate test departments (plus our own meagre developer testing) plus presumably apple ran it at least once prior to approving it. No crashes.
    Everything you suggest for testing has already been done many times, (for the first launch and for subsequent updates) This is something recent and new.
    After uploading to app store, its a 100% fail on all devices, crashes on launch. It was not something that was "missed" in testing.
    googling around, other devs have had similar issues.

    Yes, we are using prime31 plugins, but have not done any custom modifications, and they have worked fine previously, and seem to be working for other developers.

    Do you have any positive suggestions based on the crash log ?
     
    Last edited: Mar 14, 2014
  4. greay

    greay

    Joined:
    Mar 23, 2011
    Posts:
    88
    We're seeing something similar, but worse. It exits before it even gets a chance to generate a crash report. We also failed submission because of it:

     
  5. Crazy Robot

    Crazy Robot

    Joined:
    Apr 18, 2009
    Posts:
    921
    Are you accessing iCloud? If so, is your App ID for your app have iCloud enabled? Does your Distribution Provision Profile list iCloud under Enabled Services? Is iCloud setup correctly in xCode?
     
  6. Mantas-Puida

    Mantas-Puida

    Joined:
    Nov 13, 2008
    Posts:
    1,864
    @JonnyHilly, you should try symbolicating generated crash report. Proper stack trace should hint what is actually happening.
     
  7. JonnyHilly

    JonnyHilly

    Joined:
    Sep 4, 2009
    Posts:
    749
    Thanks all for suggestions. Re-submitted same build to apple, it passed again and this time works for everyone!
    Must have been some kind of corruption.