I had something relatively similar to your story happen to me as well, funnily enough 😅. It's not directly related to code, but I would definitely consider it debugging to some degree 😂
I typically work on web apps & websites, but one of my university term projects this year was a native app. My team and I chose to build an Android app.
One of the final steps in the project was to submit the app to the Google play store... As part of that submission, you have to sign the google ads TOS. For some reason, we just couldn't find the confirmation button. After literal hours of trying to figure it out, I turned off my adblocker and reloaded... turns out the confirmation button was inside an iframe from ads.google.com ( a blocked domain ).
I don't think I've ever felt so simultaneously relieved and idiotic at the same time...
A Freelance DevOps doing container stuff and automating unhealthy amounts of software.
Need something automated or containerized? Feel free to hit me up :)
Wow, I never would have thought about that, nicely done!
Imagine the pain if it was a centrally managed dns adblocker like pi-hole. Not even your local adblocker would have known there was a button :D
That would have been horrifying lmao. At least in my case, Firefox is kind enough to give a hint (from the dev tools) that maybe an extension of some sort is the cause of my problem.
There has to be a clause in the ToS that we implicitly accept when we install these Adblockers stating that we'll have a "heart-dropping conundrum at least once while this extension is installed".
I had something relatively similar to your story happen to me as well, funnily enough 😅. It's not directly related to code, but I would definitely consider it debugging to some degree 😂
I typically work on web apps & websites, but one of my university term projects this year was a native app. My team and I chose to build an Android app.
One of the final steps in the project was to submit the app to the Google play store... As part of that submission, you have to sign the google ads TOS. For some reason, we just couldn't find the confirmation button. After literal hours of trying to figure it out, I turned off my adblocker and reloaded... turns out the confirmation button was inside an iframe from ads.google.com ( a blocked domain ).
I don't think I've ever felt so simultaneously relieved and idiotic at the same time...
Wow, I never would have thought about that, nicely done!
Imagine the pain if it was a centrally managed dns adblocker like pi-hole. Not even your local adblocker would have known there was a button :D
oh that would be terrible 😰
I definitely don't think I would have figured it out if that was the case.
That would have been horrifying lmao. At least in my case, Firefox is kind enough to give a hint (from the dev tools) that maybe an extension of some sort is the cause of my problem.
There has to be a clause in the ToS that we implicitly accept when we install these Adblockers stating that we'll have a "heart-dropping conundrum at least once while this extension is installed".
LOL no kidding huh 😅