The #MobileDebugging Writing Contest: Round 3 Results Announced!

Technophiles and bug hunters of all ages - the results of the #MobileDebugging Writing Contest Round 3 are here!

If you're reading about this contest for the first time, you still stand a chance to win $$$. Do you have a knack for unraveling complex coding conundrums? Well then, and HackerNoon present you with the Mobile Debugging Writing Contest!

Entering the contest is super easy - submit a story related to mobile app testing and debugging!

#MobileDebugging: Some ideas to help you get started

1. Do you remember those support tickets from customers writing in to report their application crashing or freezing?
2. Was it right after a new release?
3. Were you notified by a monitoring tool?
4. Did a problem arise from a 3rd party library?
5. Did a problem occur when receiving an unexpected HTTP response? ​

The Mobile Debugging Writing Contest: Round 3 Nominations 🔥

We followed our tradition of selecting the winners by selecting the top ten story submissions that had the highest number of views and votes. And to add some extra spice, HackerNoon's editorial team cast their votes to determine the crème de la crème, the top three winners.

#MobileDebugging Writing Contest: Top 10 nominations:

1. Debugging Rust Cargo Issues in Gitlab by @maksimmuravev
2. The Red Death of Flutter by @sipping
3. Implementing 'UICollectionView Compositional' Layout with Pinterest Section by @vadimchistiako
4. Cocoapod as XCFramework With Dependencies by @maxkalik
5. Running Parallel Code in Flutter With Isolates by @dhruvam
6. How to Upload Source Maps to Sentry with Next.js by @chilledcowfan
7. An Intro to the Playwright Testing Framework by @puppo
8. The Mighty App Developer vs a Pesky Bug by @thedebuggingdetective
9. Improve Your Code Quality With These Useful Kotlin Extensions for Android by @victorbrndls
10. How to Generate Test Code with Playwright by @puppo

#MobileDebugging: Round 3 Winners 🔥🔥🔥

The story that got the highest number of votes is:

Flutter is beautiful. Why such a statement? It is because Flutter takes the hardships out of mobile development... for the most part.

Congratulations,@sipping, on winning first place. You have won $500.

The second place goes to:

A little explanation: When Sentry is reacting to any error or event, it tries to get the source maps from the release archive that it has uploaded. According to the GitHub issue conversation, the framework's code does not get uploaded by default anymore and Sentry doesn’t have access to all files for resolving stack trace.

Way to go@chilledcowfan! You have won $300!

Third place and the most-read story award goes to:

That’s a double-win, @maksimmuravev! You won $200!

Once again, congratulations to all the winners! We will be in touch with y’all shortly. In the meantime, keep calm and continue submitting your stories on #mobiledebugging. To find out more about our ongoing contests, please visit contests.gzht888.com.