paint-brush
The #MobileDebugging Writing Contest: Round 3 Results Announced!by@hackernooncontests
385 reads
385 reads

The #MobileDebugging Writing Contest: Round 3 Results Announced!

by HackerNoon Writing Contests Announcements
HackerNoon Writing Contests Announcements HackerNoon profile picture

HackerNoon Writing Contests Announcements

@hackernooncontests

Official account for all the writing contests powered by HackerNoon.

March 22nd, 2023
Read on Terminal Reader
Read this story in a terminal
Print this story
Read this story w/o Javascript
Read this story w/o Javascript

Too Long; Didn't Read

@sipping wins the first position with the story, The Red Death of Flutter. In second place is How to Upload Source Maps to Sentry with Next.js by @chilledcowfan, while third place went to Debugging Rust Cargo Issues in Gitlab by @maksimmuravev.

People Mentioned

Mention Thumbnail

@maksimmuravev)__[@maksimmuravev](https://hackernoon.com/u/maksimmuravev

Mention Thumbnail

sipping

@sipping

featured image - The #MobileDebugging Writing Contest: Round 3 Results Announced!
1x
Read by Dr. One voice-avatar

Listen to this story

HackerNoon Writing Contests Announcements HackerNoon profile picture
HackerNoon Writing Contests Announcements

HackerNoon Writing Contests Announcements

@hackernooncontests

Official account for all the writing contests powered by HackerNoon.

Learn More
LEARN MORE ABOUT @HACKERNOONCONTESTS'S
EXPERTISE AND PLACE ON THE INTERNET.
0-item

STORY’S CREDIBILITY

Associated Companies

Associated Companies

The writer has or has previously had a business relationship with companies mentioned in this article.

Which companies mentioned has the author had a business relationship with before?

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!

lemon squeezy

lemon squeezy

#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? ​

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:


  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:


article preview
HACKERNOON

The Red Death of Flutter | HackerNoon

Explanation of how Google's Flutter UI startup app was debugged and made to work again and connect with it's central Firebase Database through hours of work.


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:


article preview
HACKERNOON

How to Upload Source Maps to Sentry with Next.js | HackerNoon

Troubleshooting with source maps uploading to Sentry with Next.js


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:


article preview
HACKERNOON

Debugging Rust Cargo Issues in Gitlab | HackerNoon

Straightforward moral of the story: always first check environment variables in CI settings. They can overwrite your configs and cause unexpected issues.


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.


L O A D I N G
. . . comments & more!

About Author

HackerNoon Writing Contests Announcements HackerNoon profile picture
HackerNoon Writing Contests Announcements@hackernooncontests
Official account for all the writing contests powered by HackerNoon.

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite
Writingcontests
Coffee-web
Unni

Mentioned in this story

profiles
X REMOVE AD