2021-05-12
2307
#firebase
Nabil Kazi
48329
May 12, 2021 ⋅ 8 min read

Logging and remote error reporting in mobile apps

Nabil Kazi Mobile Team Lead | Product Designer

Recent posts:

the replay october 8

The Replay (10/8/25): Data enrichment, CSS is back, TypeScript 5.9

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the October 8th issue.

Matt MacCormack
Oct 8, 2025 ⋅ 30 sec read
Goodbye, messy data: An engineer’s guide to scalable data enrichment

Goodbye, messy data: An engineer’s guide to scalable data enrichment

Walk through building a data enrichment workflow that moves beyond simple lead gen to become a powerful internal tool for enterprises.

Alexandra Spalato
Oct 8, 2025 ⋅ 6 min read

DesignCoder and the future of AI-generated UI

From sketches to code in minutes, DesignCoder shows how AI-generated, hierarchy-aware UIs could change the way developers prototype and ship apps.

Rosario De Chiara
Oct 7, 2025 ⋅ 5 min read

Should you use if() functions in CSS?

It’s 2025, and CSS finally thinks logically. The if() function brings real conditional styling — no hacks, no JS workarounds. Here’s how to use it right.

Ikeh Akinyemi
Oct 7, 2025 ⋅ 16 min read
View all posts

One Reply to "Logging and remote error reporting in mobile apps"

  1. Hi Nabil, thanks for your post.
    I have a question about the Android example: in order to get the log message remotely sent via Firebase, shouldn’t you do like this?
    Timber.e(new RuntimeException(“Test error message”),”Test error message”);
    It seems to me that, if you do not add the message to the Throwable, the text is not sent to Firebase…
    Thank you in advance for your reply.
    Filippo

Leave a Reply