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, Sentry 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 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 this template. 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: Debugging Rust Cargo Issues in Gitlab by @maksimmuravev The Red Death of Flutter by @sipping Implementing 'UICollectionView Compositional' Layout with Pinterest Section by @vadimchistiako Cocoapod as XCFramework With Dependencies by @maxkalik Running Parallel Code in Flutter With Isolates by @dhruvam How to Upload Source Maps to Sentry with Next.js by @chilledcowfan An Intro to the Playwright Testing Framework by @puppo The Mighty App Developer vs a Pesky Bug by @thedebuggingdetective Improve Your Code Quality With These Useful Kotlin Extensions for Android by @victorbrndls How to Generate Test Code with Playwright by @puppo #MobileDebugging: Round 3 Winners 🔥🔥🔥 The story that got the highest number of votes is: https://hackernoon.com/the-red-death-of-flutter?embedable=true 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: https://hackernoon.com/how-to-upload-source-maps-to-sentry-with-nextjs?embedable=true 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: https://hackernoon.com/debugging-rust-cargo-issues-in-gitlab?embedable=true 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.hackernoon.com. You can enter the Mobile Debugging Writing Contest using this template. Technophiles and bug hunters of all ages - the results of the #MobileDebugging Writing Contest Round 3 are here! #MobileDebugging 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, Sentry and HackerNoon present you with the Mobile Debugging Writing Contest! Sentry Entering the contest is super easy - submit a story related to mobile app testing and debugging! #MobileDebugging: 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? 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 this template. Enter the Mobile Debugging Writing Contest using this template . this template this template The Mobile Debugging Writing Contest: Round 3 Nominations 🔥 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: #MobileDebugging Writing Contest: Debugging Rust Cargo Issues in Gitlab by @maksimmuravev The Red Death of Flutter by @sipping Implementing 'UICollectionView Compositional' Layout with Pinterest Section by @vadimchistiako Cocoapod as XCFramework With Dependencies by @maxkalik Running Parallel Code in Flutter With Isolates by @dhruvam How to Upload Source Maps to Sentry with Next.js by @chilledcowfan An Intro to the Playwright Testing Framework by @puppo The Mighty App Developer vs a Pesky Bug by @thedebuggingdetective Improve Your Code Quality With These Useful Kotlin Extensions for Android by @victorbrndls How to Generate Test Code with Playwright by @puppo Debugging Rust Cargo Issues in Gitlab by @maksimmuravev Debugging Rust Cargo Issues in Gitlab Debugging Rust Cargo Issues in Gitlab @maksimmuravev @maksimmuravev The Red Death of Flutter by @sipping The Red Death of Flutter The Red Death of Flutter @sipping @sipping Implementing 'UICollectionView Compositional' Layout with Pinterest Section by @vadimchistiako Implementing 'UICollectionView Compositional' Layout with Pinterest Section Implementing 'UICollectionView Compositional' Layout with Pinterest Section @vadimchistiako Cocoapod as XCFramework With Dependencies by @maxkalik Cocoapod as XCFramework With Dependencies Cocoapod as XCFramework With Dependencies @maxkalik @maxkalik Running Parallel Code in Flutter With Isolates by @dhruvam Running Parallel Code in Flutter With Isolates Running Parallel Code in Flutter With Isolates @dhruvam @dhruvam How to Upload Source Maps to Sentry with Next.js by @chilledcowfan How to Upload Source Maps to Sentry with Next.js How to Upload Source Maps to Sentry with Next.js @chilledcowfan @chilledcowfan An Intro to the Playwright Testing Framework by @puppo An Intro to the Playwright Testing Framework An Intro to the Playwright Testing Framework @puppo @puppo The Mighty App Developer vs a Pesky Bug by @thedebuggingdetective The Mighty App Developer vs a Pesky Bug The Mighty App Developer vs a Pesky Bug @thedebuggingdetective @thedebuggingdetective Improve Your Code Quality With These Useful Kotlin Extensions for Android by @victorbrndls Improve Your Code Quality With These Useful Kotlin Extensions for Android Improve Your Code Quality With These Useful Kotlin Extensions for Android @victorbrndls @victorbrndls How to Generate Test Code with Playwrigh t by @puppo How to Generate Test Code with Playwrigh @puppo @puppo #MobileDebugging: Round 3 Winners 🔥🔥🔥 #MobileDebugging: Round 3 Winners 🔥🔥🔥 The story that got the highest number of votes is: https://hackernoon.com/the-red-death-of-flutter?embedable=true https://hackernoon.com/the-red-death-of-flutter?embedable=true Flutter is beautiful. Why such a statement? It is because Flutter takes the hardships out of mobile development... for the most part. 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. @sipping , @sipping The second place goes to: https://hackernoon.com/how-to-upload-source-maps-to-sentry-with-nextjs?embedable=true https://hackernoon.com/how-to-upload-source-maps-to-sentry-with-nextjs?embedable=true 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. 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. release Way to go @chilledcowfan ! You have won $300! @chilledcowfan @chilledcowfan Third place and the most-read story award goes to: https://hackernoon.com/debugging-rust-cargo-issues-in-gitlab?embedable=true https://hackernoon.com/debugging-rust-cargo-issues-in-gitlab?embedable=true That’s a double-win, @maksimmuravev ! You won $200! @maksimmuravev @maksimmuravev 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.hackernoon.com . #mobiledebugging contests.hackernoon.com You can enter the Mobile Debugging Writing Contest using this template. You can enter the Mobile Debugging Writing Contest using this template . this template this template