Firebase Crashlytics - Issue number
up vote
2
down vote
favorite
Just moved finally from using Fabric to using Firebase to track our app crashes, and the only thing I'm missing are the issue numbers, that I'm used to from Fabric. Is there a way to see issue numbers on Firebase Crashlytics?
Before, on Fabric: (you can see the numbers marked with green)
And on Firebase, can't find them:
firebase crashlytics firebase-crash-reporting asked Nov 9 at 15:52
Hadas Kaminsky
417418
add a comment |
up vote
2
down vote
favorite
Just moved finally from using Fabric to using Firebase to track our app crashes, and the only thing I'm missing are the issue numbers, that I'm used to from Fabric. Is there a way to see issue numbers on Firebase Crashlytics?
Before, on Fabric: (you can see the numbers marked with green)
And on Firebase, can't find them:
firebase crashlytics firebase-crash-reporting asked Nov 9 at 15:52
Hadas Kaminsky
417418
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Just moved finally from using Fabric to using Firebase to track our app crashes, and the only thing I'm missing are the issue numbers, that I'm used to from Fabric. Is there a way to see issue numbers on Firebase Crashlytics?
Before, on Fabric: (you can see the numbers marked with green)
And on Firebase, can't find them:
firebase crashlytics firebase-crash-reporting asked Nov 9 at 15:52
Hadas Kaminsky
417418
Just moved finally from using Fabric to using Firebase to track our app crashes, and the only thing I'm missing are the issue numbers, that I'm used to from Fabric. Is there a way to see issue numbers on Firebase Crashlytics?
Before, on Fabric: (you can see the numbers marked with green)
And on Firebase, can't find them:
firebase crashlytics firebase-crash-reporting firebase crashlytics firebase-crash-reporting asked Nov 9 at 15:52
Hadas Kaminsky
417418
asked Nov 9 at 15:52
Hadas Kaminsky
417418
edited Nov 9 at 19:23
asked Nov 9 at 15:52
Hadas Kaminsky
417418
asked Nov 9 at 15:52
Hadas Kaminsky
417418
asked Nov 9 at 15:52
Hadas Kaminsky
417418
417418
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Mike from Firebase here. Currently, we don't have issue numbers included within Crashlytics.
I'll let the team know you'd like to see them added in.
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
Thanks, that would be very useful! We are using the issue numbers in our crash fixing process as a way to identify the crash and as a naming convention. I'm sure more developers do too.
– Hadas Kaminsky
Nov 12 at 20:57
Thanks for the feedback again, much appreciated.
– Mike Bonnell
Nov 12 at 21:24
add a comment |
up vote
0
down vote
Whilst (as Mike Bonnell said) there are no issue numbers, you can use the issue ID in the URL bar as an identifier if essential, although it is much longer.
For example, for the issue URL https://console.firebase.google.com/project/<project name>/crashlytics/app/android:<package name>/issues/5bcc240cf8b88c29639a0bcd the ID is 5bcc240cf8b88c29639a0a8e.
answered Dec 5 at 18:37
JakeSteam
1,27521933
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',
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%2f53229063%2ffirebase-crashlytics-issue-number%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Mike from Firebase here. Currently, we don't have issue numbers included within Crashlytics.
I'll let the team know you'd like to see them added in.
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
Thanks, that would be very useful! We are using the issue numbers in our crash fixing process as a way to identify the crash and as a naming convention. I'm sure more developers do too.
– Hadas Kaminsky
Nov 12 at 20:57
Thanks for the feedback again, much appreciated.
– Mike Bonnell
Nov 12 at 21:24
add a comment |
up vote
3
down vote
accepted
Mike from Firebase here. Currently, we don't have issue numbers included within Crashlytics.
I'll let the team know you'd like to see them added in.
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
Thanks, that would be very useful! We are using the issue numbers in our crash fixing process as a way to identify the crash and as a naming convention. I'm sure more developers do too.
– Hadas Kaminsky
Nov 12 at 20:57
Thanks for the feedback again, much appreciated.
– Mike Bonnell
Nov 12 at 21:24
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Mike from Firebase here. Currently, we don't have issue numbers included within Crashlytics.
I'll let the team know you'd like to see them added in.
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
Mike from Firebase here. Currently, we don't have issue numbers included within Crashlytics.
I'll let the team know you'd like to see them added in.
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
answered Nov 12 at 18:57
Mike Bonnell
13.5k24562
13.5k24562
Thanks, that would be very useful! We are using the issue numbers in our crash fixing process as a way to identify the crash and as a naming convention. I'm sure more developers do too.
– Hadas Kaminsky
Nov 12 at 20:57
Thanks for the feedback again, much appreciated.
– Mike Bonnell
Nov 12 at 21:24
add a comment |
Thanks, that would be very useful! We are using the issue numbers in our crash fixing process as a way to identify the crash and as a naming convention. I'm sure more developers do too.
– Hadas Kaminsky
Nov 12 at 20:57
Thanks for the feedback again, much appreciated.
– Mike Bonnell
Nov 12 at 21:24
Thanks, that would be very useful! We are using the issue numbers in our crash fixing process as a way to identify the crash and as a naming convention. I'm sure more developers do too.
– Hadas Kaminsky
Nov 12 at 20:57
Thanks, that would be very useful! We are using the issue numbers in our crash fixing process as a way to identify the crash and as a naming convention. I'm sure more developers do too.
– Hadas Kaminsky
Nov 12 at 20:57
Thanks for the feedback again, much appreciated.
– Mike Bonnell
Nov 12 at 21:24
Thanks for the feedback again, much appreciated.
– Mike Bonnell
Nov 12 at 21:24
add a comment |
up vote
0
down vote
Whilst (as Mike Bonnell said) there are no issue numbers, you can use the issue ID in the URL bar as an identifier if essential, although it is much longer.
For example, for the issue URL https://console.firebase.google.com/project/<project name>/crashlytics/app/android:<package name>/issues/5bcc240cf8b88c29639a0bcd the ID is 5bcc240cf8b88c29639a0a8e.
answered Dec 5 at 18:37
JakeSteam
1,27521933
add a comment |
up vote
0
down vote
Whilst (as Mike Bonnell said) there are no issue numbers, you can use the issue ID in the URL bar as an identifier if essential, although it is much longer.
For example, for the issue URL https://console.firebase.google.com/project/<project name>/crashlytics/app/android:<package name>/issues/5bcc240cf8b88c29639a0bcd the ID is 5bcc240cf8b88c29639a0a8e.
answered Dec 5 at 18:37
JakeSteam
1,27521933
add a comment |
up vote
0
down vote
up vote
0
down vote
Whilst (as Mike Bonnell said) there are no issue numbers, you can use the issue ID in the URL bar as an identifier if essential, although it is much longer.
For example, for the issue URL https://console.firebase.google.com/project/<project name>/crashlytics/app/android:<package name>/issues/5bcc240cf8b88c29639a0bcd the ID is 5bcc240cf8b88c29639a0a8e.
answered Dec 5 at 18:37
JakeSteam
1,27521933
Whilst (as Mike Bonnell said) there are no issue numbers, you can use the issue ID in the URL bar as an identifier if essential, although it is much longer.
For example, for the issue URL https://console.firebase.google.com/project/<project name>/crashlytics/app/android:<package name>/issues/5bcc240cf8b88c29639a0bcd the ID is 5bcc240cf8b88c29639a0a8e.
answered Dec 5 at 18:37
JakeSteam
1,27521933
answered Dec 5 at 18:37
JakeSteam
1,27521933
answered Dec 5 at 18:37
JakeSteam
1,27521933
answered Dec 5 at 18:37
JakeSteam
1,27521933
1,27521933
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%2f53229063%2ffirebase-crashlytics-issue-number%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
