Do you periodically audit your own ad implementation, or just trust it once it's live?

Been working solo on an Android app called WordNerd - GRE Vocabulary Builder and got curious about something. Once ads are wired up and showing correctly, how many of you actually go back and audit the implementation later versus just letting it run?

I decided to do a full pass on mine before launch, tracing every single ad call instead of just confirming ads were displaying. Turned up four bugs that were invisible from the outside. A native ad view was leaking memory because it wasn't being destroyed on recomposition. A preload function was firing from two different screens at once, so I was double requesting fill for the same slot. One activity was missing a premium status check before preloading, so premium users were technically still triggering background ad calls they'd never see. And one native ad card was rendering off screen due to a layout bug but still counting as a served impression.

Everything looked completely normal from the UI side. The only reason I found these was by treating it like a code review rather than a QA pass.

Wondering if this is a known blind spot for solo devs specifically, since there's no second engineer reviewing the ad code path. If anyone has a checklist they run before submitting a build for review, I'd genuinely like to see it.

WordNerd - GRE Vocabulary Builder on Google Play Store