Practice crash reporting vocabulary: crash rates, symbolicated reports, platform-specific crashes, Firebase Crashlytics, and crash triage processes.
0 / 10 completed
1 / 10
'The crash ___ is 0.3% per session.' Which noun fits?
'Crash rate' is the standard metric: the percentage of sessions that end in a crash. Apple recommends keeping this below 1%; under 0.5% is generally considered good.
2 / 10
What is a 'symbolicated crash report'?
Symbolication maps raw memory addresses in a crash stack trace to readable function names, file names, and line numbers using a .dSYM (iOS) or symbol file (Android).
3 / 10
'The crash happens ___ iOS 16.4 specifically.' Which preposition is correct?
'On iOS 16.4' is correct. The preposition 'on' is used with iOS versions and platforms: 'on iOS', 'on Android', 'on macOS'.
4 / 10
What is Firebase Crashlytics used for?
Firebase Crashlytics is Google's mobile crash reporting tool. It collects, symbolizes, and groups crash reports in real time, helping teams triage and prioritize fixes.
5 / 10
In crash triage, what does it mean to 'reproduce the crash'?
'Reproducing' a crash means finding the exact steps or conditions that trigger it in a controlled environment, which is the prerequisite for debugging and fixing it.
6 / 10
During a code review for the new payment processing module, Sarah flags a potential issue. The commit message reads: 'Fix: Handling null values in transaction data. Crash reported by users on iOS – likely related to inconsistent data formatting.' Which term best describes the *cause* of this crash as described here?
This description highlights a problem where the system is receiving data it doesn't expect (a 'null' value). While a null pointer exception *could* be involved, the primary issue identified here is the source of the unexpected data. The key vocabulary point is recognizing that 'unexpected input' directly addresses this scenario – developers often use this term to describe situations where data deviates from what's anticipated.
7 / 10
Mark sends a Slack message to the team: 'Just got a spike in Crashlytics reports for our Android app after deploying v2.5.1. The stack trace shows a `NullPointerException` in the network request handler. We've attached a symbolicated crash report.' What is the *primary* purpose of a 'symbolicated crash report'?
A symbolicated crash report is crucial for efficient debugging. The term 'symbolicated' refers to the process of replacing identifiable information like usernames, passwords, and exact file paths with generic placeholders. This dramatically reduces the size of the report and allows developers to focus on the core technical details without being distracted by irrelevant data – this is a critical step in triage.
8 / 10
During a standup meeting, David reports: 'We're seeing an increase in crash reports related to the user profile update feature. The logs show that the `saveUserProfile()` function is throwing an exception when the server returns a 400 error. We've created a detailed crash report and are investigating.' What does David mean by 'creating a detailed crash report'?
When David says 'creating a detailed crash report,' he's referring to assembling comprehensive information about the crash. This includes stack traces, device logs, user context data, and any other relevant technical details that will help developers understand *why* the exception occurred and how to reproduce it – this is vital for effective triage.
9 / 10
In a PR review comment, you see the following: 'This feature seems stable in development but we're seeing intermittent crashes reported in Crashlytics on production iOS devices. The crash reports consistently include a stack trace pointing to our image loading library.' What is the *most* important next step for the team to take based on this information?
The key takeaway here is that the crashes are consistently linked to a specific component – the image loading library. Investigating its configuration and potential issues within that area is the most targeted and efficient approach to resolving the problem rather than a broad rollback or alerting all users.
10 / 10
You're triaging crash reports for a mobile game. A report shows a 'Segmentation Fault' occurring only on Samsung Galaxy S21 devices running Android 13. What does it mean to 'reproduce the crash' in this context?
'Reproducing' a crash means recreating the exact circumstances under which it initially occurred. In this case, that would involve attempting to run the game on a Samsung Galaxy S21 with Android 13 – effectively mirroring the original environment where the crash was first observed. This allows developers to analyze the problem in detail.
What will I practise in "Crash Reporting Vocabulary"?
This module focuses on Mobile App Publishing — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Mobile App Publishing exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around mobile app publishing — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Mobile App Publishing exercises?
See the Mobile App Publishing hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.