Wrong AdMob App ID Caused Limited Ad Serving on Live Android Game

·3 views

A developer discovered that AdMob was serving limited ads on their live Android game, Logo Quiz: Guess Brand, because the ad units were registered under a different AdMob app entry than the one linked to the Play Store listing. AdMob requires a one-to-one link between a Play Store listing and an AdMob app, and since the verified app had no ad units while the app with ad units was unverified, neither could serve ads properly. The fix involved creating ad units under the Play-linked app and updating four IDs across the project, including in both app.json and AndroidManifest.xml, where the app ID is stored in two separate places. The developer noted that changing only app.json still results in the old ID being baked into the APK, and recommends inspecting the compiled artifact directly to confirm which ID was actually shipped. The key lesson offered is to create and link the AdMob app to the Play Store listing before adding any ad unit IDs to the codebase.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Find the Real Cause Behind Unity's 'Gradle Build Failed' Error

Unity developers building Android APKs often get stuck on the 'CommandInvokationFailure: Gradle build failed' console message, which appears hundreds of lines after the actual root cause in the log file. The true error — such as duplicate classes on the classpath — is logged around line 923, while the misleading Gradle failure message appears near line 1158. Developers can bypass the noise by running a grep command against Unity's Editor log to jump directly to the 'What went wrong' section. Common triggers include duplicate JARs in the project, such as copying unity-classes.jar under a second name, or conflicts introduced via the External Dependency Manager. Clearing resolved libraries through Assets → External Dependency Manager → Android Resolver can resolve duplicate-class errors, particularly in Unity 2022.2 and later.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Dev Writer Tests Every Terminal Claim on His Machine Before Publishing

A developer and technical writer behind the weekly newsletter Shellcraft has shared his core editorial rule: every terminal-related claim is verified on his own machine before publication. He estimates that roughly one in five drafted claims turns out to be incorrect upon testing, not due to typos but plausible-sounding errors rooted in outdated or misremembered information. To enforce this standard, he creates a private verification guide for each issue, outlining steps to reproduce commands and their expected outputs. He recently caught a critical error while testing a tool's panel workflow, discovering that a central step in a drafted issue did not work as described, prompting a full rewrite. Introducing himself to the DEV Community, he framed this practice as a promise to the developer audience he plans to write for there at least once a month.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Solo Dev Builds Ad-Free HTML5 Gaming Platform With 17,000 Games and 500K Players

A solo developer built Spielcade, a free browser-based gaming platform designed to eliminate the ads, malware warnings, and forced downloads common on casual gaming sites. The platform hosts over 17,000 HTML5 games across more than 25 genres and has attracted over 500,000 active players with a 4.9 out of 5 rating. It was built using Next.js, React, Node.js, and PostgreSQL, with Cloudflare CDN used to ensure fast global load times. Key technical challenges included scaling database queries for complex tag filtering, optimizing thousands of game thumbnails via lazy loading, and managing technical SEO across more than 17,000 individual game pages. The developer used server-side rendering and automated dynamic sitemaps to help search engines index the growing library effectively.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Guide: Deploy Gemma 4 2B on Cloud Run with NVIDIA L4 GPU Using Python MCP Tools

A step-by-step deployment guide has been published for running Google's Gemma 4 2B model on Google Cloud Run using an NVIDIA L4 GPU and vLLM as the inference server. The project includes a single-file Python MCP server that handles model weight staging, service deployment, health checks, benchmarking, and teardown. Cloud Run's serverless architecture eliminates the need to provision VMs or install GPU drivers manually, with the service scaling to zero when idle. The guide also covers a required migration to MCP Python SDK 2.x after a version-unbound pip install broke the server's import on fresh setups. Prerequisites include Python 3.10 or newer, Claude Code, the Google Cloud SDK with active credentials, and a GCS bucket for storing model weights.

0 comments Read more at DEV Community