crash from aar-library neither showing in Developer console nor HockeyApp after publishing

Jonathan Schneider's Avatar

Jonathan Schneider

12 Apr, 2017 07:16 PM

I asked the question on StackOverflow and got redirected here, so this ticket is only a copy of this:
http://stackoverflow.com/questions/43345077/crash-from-aar-library-neither-showing-in-developer-console-nor-hockeyapp-after/43357582#43357582

in our App we're using a native library packaged as an .aar and HockeyApp for error reporting. The .aar-code draws information on a SurfaceFragment, the rest of the Application uses standard Android libraries.

After publishing the app to Google Play, users have experienced crashes of the .aar-library, after which the SurfaceFragment stays blank, the surrounding app doesn't crash. During development, these reports were sent to HockeyApp. Now that the app is published, the dialog for crash reports isn't HockeyApp's any more, but a standard google one. However, the reports neither show up in the developer console nor in HockeyApp.

How/where can I get the error reports for the native library?

  1. Support Staff 1 Posted by Benjamin Scholt... on 13 Apr, 2017 09:13 PM

    Benjamin Scholtysik's Avatar

    Hey Jonathan,

    Thanks for getting in touch here. This sounds like HockeyApp's register-calls are called in the release build.
    Which version of the HA SDK are you using and can you share the setup code?

    Apologies for the delayed response on this.
    Best,
    Benny

  2. 2 Posted by Jonathan Schnei... on 18 Apr, 2017 09:29 AM

    Jonathan Schneider's Avatar

    Hi Benjamin,

    we're calling HockeyApp in our start Activity in the following way, relevant code as follows:

        @Override
        public void onResume() {
            super.onResume();
            // ... your own onResume implementation
            checkForCrashes();
        }

        @Override
        public void onPause() {
            super.onPause();
            unregisterManagers();
        }

        @Override
        public void onDestroy() {
            super.onDestroy();
            unregisterManagers();
        }

        private void checkForCrashes() {
            CrashManager.register(this);
        }

        private void checkForUpdates() {
            // Remove this for store builds!
            //UpdateManager.register(this);
        }

        private void unregisterManagers() {
            UpdateManager.unregister();
        }

  3. Benjamin Scholtysik closed this discussion on 18 Apr, 2017 05:15 PM.

  4. Benjamin Scholtysik re-opened this discussion on 18 Apr, 2017 09:20 PM

  5. Support Staff 3 Posted by Benjamin Scholt... on 18 Apr, 2017 09:20 PM

    Benjamin Scholtysik's Avatar

    Hey Jonathan,

    thank you for getting in touch. This is a really weird issue, indeed, and we haven't heard anything like this so far.

    From what I know, it really doesn't matter if the crash occurs inside a .aar or within the app, as the .aar file "is gone" after the app has been build and I don't know of any setting that could possibly result in what you are experiencing.

    I'm hoping to be able to reproduce the issue somehow and then be able to help you. For that, I need more info.

    Which version of the HockeySDK are you using?
    Would you mind sharing a full stacktrace of the crash you are experiencing in debug?
    Does the crash happen only when the apk is submitted to google play or does it happen with the release-build of the APK?

    Best,
    Benny

  6. 4 Posted by Jonathan Schnei... on 21 Apr, 2017 11:04 AM

    Jonathan Schneider's Avatar

    Hi Benny,

    we managed to pin down the error, and it happened because we did not check the V1 (Jar Signature) setting for the signed APK.

    That at least stopped the error from happening when manually installing a release-build. We still have to check what happens when we load the app through the play store.

    Best wishes,
    Jonathan

  7. Support Staff 5 Posted by Benjamin Scholt... on 21 Apr, 2017 05:04 PM

    Benjamin Scholtysik's Avatar

    Hey Jonathan,

    Thanks for the update on the issue. This is interesting.

    I appreciate if you could get in touch once you know if this also fixes the issue with the Play Store. I'd like to add this to our knowledge base.

    Have a great weekend!
    Benny

  8. Benjamin Scholtysik closed this discussion on 25 Apr, 2017 06:28 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac