Welcome to the round 1 winner announcement for the Mobile Debugging Writing Contest by Sentry! Reading about this contest for the first time? We’ve got you covered. This time around, we are interested in reading stories about mobile application debugging.
Some ideas to help you get started:
- Do you remember those support tickets from customers writing in to report their application crashing or freezing?
- Was it right after a new release?
- Were you notified by a monitoring tool?
- Did a problem arise from a 3rd party library?
- Did a problem occur when receiving an unexpected HTTP response?
Enter the Mobile Debugging Writing Contest using
The Mobile Debugging Writing Contest: Round 1 Nominations 🔥
We’ve picked our winners by taking the top ten story submissions that generated the most traffic. HackerNoon’s editorial team then voted, picking the top three stories among them and deciding which order to place the winners.
Here are the Top 10 nominees:
- How I Detected Bugs in a Wallet App by @induction
- The Story of How I Almost Became a Developer by @correspondentone
- How to Save Time by Testing Your Application by @aksenov
- Follow These Tips If Your Android Apps Keep Crashing by @induction
- Debugging on Mobile is Too Hard by @mcsee
- How to Find the Stinky Parts of Your Code [Part XXVII] by @mcsee
- 8 Debugging Techniques for Dev & Ops Teams by @savankharod
- Debugging with Render: Two Effective Methods by @alvinslee
- Applying the Test Pyramid to iOS Applications by @mniagolov
- Mobile App Debugging: Localizing Defects and Making Bug Reports by @strateh76
Winners 🔥🔥🔥
The story that got the most views and highest number of votes is:
https://hackernoon.com/how-i-detected-bugs-in-a-wallet-app?embedable=true
Android system generates the complete information in the compressed ZIP format. The file needs to extract first.
In my case, the wallet app Xverse repeatedly crashed while editing the Bitcoin gas fee to perform the transaction, and the Transaction Failed due to “Error: Request failed with status code 400.”
Congratulations on winning the first place and most-read story award @induction!! You have won $600!
The second place is won by:
https://hackernoon.com/the-story-of-how-i-almost-became-a-developer?embedable=true
On a side note debugging while mobile counts as mobile debugging, right? Right? 😉 ..... okay, I'll stop.
Congratulations, @correspondentone! You have won $300.
In the third place, we have:
https://hackernoon.com/applying-the-test-pyramid-to-ios-applications?embedable=true
The test pyramid should not be looked at too dogmatically. Every project is different, and there are scenarios in which UI tests are easy to maintain and can frequently be executed. As with every part of the software development process, it is crucial to maintain the flexibility of adapting the test suite to changing requirements.
@mniagolov has won $100!
Congratulations again to all the winners! We will contact y’all shortly. Till then, keep calm and keep on submitting #mobiledebugging stories! Visit contests.hackernoon.com to learn more about currently running contests.