JEN PERSON: Is there one common question
that you see coming up all the time with people
when they ask about Crashlytics?
SHOBHIT CHUGH: Yeah.
JEN PERSON: Magic!
Look at that.
SPEAKER: Take one mark.
JEN PERSON: How's it going, Firebase developers?
Welcome to another episode of "#AskFirebase,"
the show where we answer your burning Firebase questions.
I'm Jen Person, your host.
And today, my co-host is Shobhit Chugh,
and Shobhit works on Crashlytics.
SHOBHIT CHUGH: Yeah.
JEN PERSON: Welcome to the show.
SHOBHIT CHUGH: Thank you.
JEN PERSON: You ready to answer some questions?
SHOBHIT CHUGH: Yeah, I'm looking forward to it.
JEN PERSON: Let's do it.
Mohammed on Twitter wants to know
if anyone knows how to close all issues at once.
It looks like they have hundreds of them.
What a pain entering and closing them one by one.
SHOBHIT CHUGH: Yeah.
Unfortunately, that's something that's not possible
right now, so you're going to have to close them one by one.
We've definitely-- it's a request that we have
that we might address at some point.
I would also ask why are you closing hundreds of issue?
Is it for historical purposes?
Like for-- is there some specific workflow
you're looking to close?
Just examine your workflow and see if they
can be closed more frequently.
JEN PERSON: That's a really good call out.
Yeah.
It's sort of-- I see this as twofold.
One is if you could close them all at once, that's great,
but also, you might miss something that's important.
SHOBHIT CHUGH: Yeah.
So also keep in mind that there's two kinds of closing.
So you can close or you can mute.
Closing means if the issue occurs again
in a new version of the app, we'll open it.
And so that means you'll be closing them again.
If this issue is that you just want to ignore irrespective,
mute them, so then they will not be open
when a new version of the app comes out
and you see the same issue again.
JEN PERSON: Cool.
I actually learned a lot from this.
This is really helpful.
I'm glad I do this show.
Phoenix, had a question about, let's say,
crash reports and people's data.
I want to identify the user specifically
to address the issue, so I need the user information
in the logs.
Is there-- is it possible to make Firebase send user info
in crash reports?
SHOBHIT CHUGH: In Crashlytics, we provide fields
where you can set user IDs.
We encourage you to use them.
They appear in the crash reports.
You can search crashes by user IDs.
I do want to caution you on one thing.
Make sure you review terms of both the Google Play
Store and the Apple App Store.
There's only some identifiable information
you can send, so keep those things in mind when you're
sending this information.
A lot of our users send anonymized user IDs
so that you're not sending identifiable user information
to Crashlytics.
JEN PERSON: Right.
That's a good call out.
Sort of we have similar questions
that come up about analytics events
and wanting to be able to identify individual users.
And it's a good idea to check out the terms,
because there is that privacy aspect.
SHOBHIT CHUGH: Right.
Yeah.
JEN PERSON: Yeah.
I'm glad you're here.
[LAUGHING]
I'm like, I don't--
OK.
Our next question is, after migrating
from Firebase crash reporting to Crashlytics,
is it necessary to upload ProGuard mapping
files with Gradle?
I didn't see anything in the documents
or in the mapping files.
Does Crashlytics handle this internally?
SHOBHIT CHUGH: So when you link your account,
we just follow the same Gradle plugin
that we use with Fabric Crashlytics.
So your mapping files were getting uploaded before,
and they get uploaded same as right now.
We handle all this transformation internally
so that you, as the user, don't have
to worry about uploading them to a different location.
JEN PERSON: Cool.
Good to know.
SHOBHIT CHUGH: So Carlos wants to know what parts of Firebase,
if any, can be used in desktop or non-mobile games
and applications?
JEN PERSON: The thing is, Firebase is primarily
for mobile applications, so it isn't really for native desktop
applications.
I've definitely seen some people try to make this work,
because you could theoretically do something involving--
like if you have your own server, you could ping that
and you can use the admin SDK on your own server.
So you have that sort of as a go-around, but most--
the features are designed to work on mobile and web
at this time.
But we are always taking feature requests.
I'll link to that below as well.
We really appreciate getting questions like that
so then we know what our developers are looking for.
SHOBHIT CHUGH: Great.
JEN PERSON: Is there anything else
that you think people should know about Crashlytics?
Maybe there's like common things that you see come up or--
SHOBHIT CHUGH: One of the great features
we have is logging non-fatals, which is very often, you know,
you might catch an exception, but you might still
want to keep track of it, so I encourage
you to use non-fatals.
That way, you can keep an eye on where you end up
in unexpected situations, even though it might not
crash the app.
And that's especially relevant for games.
JEN PERSON: Yes.
Yeah.
That makes a lot of sense.
That's huge.
If you ever look at like reviews in the app store or something
like that, of course, if an app is just closing,
that's a big deal.
But sometimes you'll just see people
talking about like unexpected behavior [INAUDIBLE] the app,
and that can be much harder to track.
So it's nice to know that Crashlytics
has your back on that as well.
SHOBHIT CHUGH: Right.
JEN PERSON: So is there one common question
that you see coming up all the time with people when
they ask about Crashlytics?
SHOBHIT CHUGH: Yeah.
So the question normally I get asked is, hey,
what is Firebase Crashlytics?
And it's fully ready to use?
And the answer to that is, yes, we've
built the required features, you know,
that exist in Fabric Crashlytics in Firebase Crashlytics.
So we strongly encourage you to come check out, link your apps,
and start using Firebase Crashlytics.
JEN PERSON: Yeah.
It's good to know it's ready to go.
SHOBHIT CHUGH: Yeah.
JEN PERSON: Thanks so much for coming on the show.
I really appreciate having your help answering these questions
about Crashlytics.
SHOBHIT CHUGH: My pleasure.
I loved answering these questions.
JEN PERSON: And thank all of you for asking questions.
We really wouldn't be able to have the show without you.
So if you have a question about Firebase, be sure
you're hitting it with that hashtag #AskFirebase
so we can take a look at it, and maybe you'll
see it on a future episode.
And if you like content that you see here,
be sure to subscribe to the Firebase channel
to check out all the other cool content that we have.
Thank you so much for watching, and I'll
see you on a future episode.
SHOBHIT CHUGH: Bye.
JEN PERSON: Bye.
SHOBHIT CHUGH: I don't really think my feelings change
that much.
I mean, I don't really care about this plant.
I do care about other plants, but not this one.