crashlytics custom crash reporting not showing on Firebase Console
up vote
0
down vote
favorite
so I'm using this tutorial https://firebase.google.com/docs/crashlytics/customize-crash-reports to enable crashlytics crash report in my Android App. I noticed that Custom Crashes never appears on my Firebase Console using this code:
Crashlytics.log(Log.DEBUG, "tag", "message");
After setting my UserIdentifier.
But when I tried Forcing a crash like this:
Crashlytics.getInstance().crash(); // Force a crash
it appears on my Dashboard. So why is my Custom Crash missing.
When I switched back to custom logging, It never works. I also tried using LogException, that didn't work as well.
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
Please note that It's Firebase console I'm using.
android 
firebase crashlytics edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
asked Nov 11 at 22:01
leggo
2716
add a comment |
up vote
0
down vote
favorite
so I'm using this tutorial https://firebase.google.com/docs/crashlytics/customize-crash-reports to enable crashlytics crash report in my Android App. I noticed that Custom Crashes never appears on my Firebase Console using this code:
Crashlytics.log(Log.DEBUG, "tag", "message");
After setting my UserIdentifier.
But when I tried Forcing a crash like this:
Crashlytics.getInstance().crash(); // Force a crash
it appears on my Dashboard. So why is my Custom Crash missing.
When I switched back to custom logging, It never works. I also tried using LogException, that didn't work as well.
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
Please note that It's Firebase console I'm using.
android firebase crashlytics edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
asked Nov 11 at 22:01
leggo
2716
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
so I'm using this tutorial https://firebase.google.com/docs/crashlytics/customize-crash-reports to enable crashlytics crash report in my Android App. I noticed that Custom Crashes never appears on my Firebase Console using this code:
Crashlytics.log(Log.DEBUG, "tag", "message");
After setting my UserIdentifier.
But when I tried Forcing a crash like this:
Crashlytics.getInstance().crash(); // Force a crash
it appears on my Dashboard. So why is my Custom Crash missing.
When I switched back to custom logging, It never works. I also tried using LogException, that didn't work as well.
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
Please note that It's Firebase console I'm using.
android firebase crashlytics edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
asked Nov 11 at 22:01
leggo
2716
so I'm using this tutorial https://firebase.google.com/docs/crashlytics/customize-crash-reports to enable crashlytics crash report in my Android App. I noticed that Custom Crashes never appears on my Firebase Console using this code:
Crashlytics.log(Log.DEBUG, "tag", "message");
After setting my UserIdentifier.
But when I tried Forcing a crash like this:
Crashlytics.getInstance().crash(); // Force a crash
it appears on my Dashboard. So why is my Custom Crash missing.
When I switched back to custom logging, It never works. I also tried using LogException, that didn't work as well.
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
Please note that It's Firebase console I'm using.
android firebase crashlytics android firebase crashlytics edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
asked Nov 11 at 22:01
leggo
2716
edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
asked Nov 11 at 22:01
leggo
2716
edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
edited Nov 12 at 3:01
Frank van Puffelen
225k26367395
225k26367395
asked Nov 11 at 22:01
leggo
2716
asked Nov 11 at 22:01
leggo
2716
asked Nov 11 at 22:01
leggo
2716
2716
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Mike from Firebase here.
Crashlytics.log(Log.DEBUG, "tag", "message"); will log information into a crash, but the logs are only sent and processed if a crash or non-fatal exception happens in the same session of the app.
Writing the log is done async, and we focus on capturing crashes or non-fatal exceptions over writing the log to disk. If the log happens just before a crash or non-fatal as in this example:
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
It's possible we didn't have time to write the log before the exception happened. In that case, we'd prioritize capturing the exception believing that getting the exception or crash is more important then a log.
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53253688%2fcrashlytics-custom-crash-reporting-not-showing-on-firebase-console%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Mike from Firebase here.
Crashlytics.log(Log.DEBUG, "tag", "message"); will log information into a crash, but the logs are only sent and processed if a crash or non-fatal exception happens in the same session of the app.
Writing the log is done async, and we focus on capturing crashes or non-fatal exceptions over writing the log to disk. If the log happens just before a crash or non-fatal as in this example:
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
It's possible we didn't have time to write the log before the exception happened. In that case, we'd prioritize capturing the exception believing that getting the exception or crash is more important then a log.
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
add a comment |
up vote
0
down vote
Mike from Firebase here.
Crashlytics.log(Log.DEBUG, "tag", "message"); will log information into a crash, but the logs are only sent and processed if a crash or non-fatal exception happens in the same session of the app.
Writing the log is done async, and we focus on capturing crashes or non-fatal exceptions over writing the log to disk. If the log happens just before a crash or non-fatal as in this example:
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
It's possible we didn't have time to write the log before the exception happened. In that case, we'd prioritize capturing the exception believing that getting the exception or crash is more important then a log.
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
add a comment |
up vote
0
down vote
up vote
0
down vote
Mike from Firebase here.
Crashlytics.log(Log.DEBUG, "tag", "message"); will log information into a crash, but the logs are only sent and processed if a crash or non-fatal exception happens in the same session of the app.
Writing the log is done async, and we focus on capturing crashes or non-fatal exceptions over writing the log to disk. If the log happens just before a crash or non-fatal as in this example:
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
It's possible we didn't have time to write the log before the exception happened. In that case, we'd prioritize capturing the exception believing that getting the exception or crash is more important then a log.
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
Mike from Firebase here.
Crashlytics.log(Log.DEBUG, "tag", "message"); will log information into a crash, but the logs are only sent and processed if a crash or non-fatal exception happens in the same session of the app.
Writing the log is done async, and we focus on capturing crashes or non-fatal exceptions over writing the log to disk. If the log happens just before a crash or non-fatal as in this example:
Crashlytics.log(Log.ASSERT, TAG, Log.getStackTraceString(e));
Crashlytics.logException(e);
It's possible we didn't have time to write the log before the exception happened. In that case, we'd prioritize capturing the exception believing that getting the exception or crash is more important then a log.
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
answered Nov 12 at 20:05
Mike Bonnell
13.6k24562
13.6k24562
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53253688%2fcrashlytics-custom-crash-reporting-not-showing-on-firebase-console%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
