Should I upgrade to IMA DAI Android Deprecated SDK Branch Risk now?

Decide whether to remain on a deprecated Google IMA Dynamic Ad Insertion SDK branch for Android despite support and ad-serving risk, or upgrade sooner and absorb the migration work.

Upgrade now to the latest supported IMA DAI Android branch if monetization continuity matters; stay on 3.35.1 only when minSdk 21 is the short-term blocker.

Blockers

Who this is for

Candidates

Upgrade now to the latest supported IMA DAI Android branch

As of 2026-03-20, Google's Android IMA DAI deprecation policy says a version is supported for 12 months after its successor releases, while deprecated versions are not guaranteed to serve ads and do not receive support-team answers. The latest release shown is 3.39.0 from 2026-01-22 with no deprecation date yet, and 3.38.0 deprecates on 2027-01-22. The main migration steps are that 3.37.0 requires app desugaring and raises minimum tooling to compileSdk 35 and Android Gradle Plugin 8.6.0, 3.38.0 raises minSdkVersion to 23, and 3.39.0 removes several deprecated APIs.

When to choose

Use this when monetization continuity matters more than short-term build churn, especially for teams that cannot accept any branch where ad serving is explicitly not guaranteed. It is the right default if you can absorb tooling updates now and want the longest remaining support window.

Tradeoffs

Best support posture and lowest ad-serving risk, but it can force Android platform work such as enabling desugaring, raising compileSdk and AGP, moving to minSdk 23, and replacing removed deprecated APIs.

Cautions

Check your app for use of APIs removed in 3.37.0 and 3.39.0 before upgrading. If you use the Video Stitcher workflow, the Android guide says your app must send ID3 events through onUserTextReceived() for IMA DAI to function.

Sources

Stay temporarily on deprecated 3.35.1 only as a short bridge

As of 2026-03-20, 3.35.1 is already deprecated, with a deprecation date of 2025-11-07. Google's deprecation page says deprecated versions are not guaranteed to serve ads, may have ad serving sunset if app-crashing bugs appear, and do not receive support-team answers on the developer forum. The practical reason to hold here is to avoid the minSdk 23 jump in 3.38.0 while still using the fixed 3.35.1 branch instead of 3.35.0.

When to choose

Use this only if your immediate blocker is the minSdk 23 increase introduced later, but you can already avoid the older 3.34.x-specific crash risk and do not need to stay below the 3.35.x line. Choose 3.35.1 when minSdk 21 support is the main short-term requirement and your near-term upgrade path is to clear later tooling and API-removal work.

Tradeoffs

Lower immediate engineering disruption than upgrading now, but with explicitly weaker support and ad-serving guarantees because the branch is deprecated.

Cautions

3.35.0 had an OMID issue and Google says to use 3.35.1 instead, so do not target 3.35.0 as a holding branch.

Sources

Stay temporarily on deprecated 3.34.0 only if 3.35.1 is also blocked

As of 2026-03-20, 3.34.0 is already deprecated, with a deprecation date of 2025-09-24. Google's deprecation page says deprecated versions are not guaranteed to serve ads, may have ad serving sunset if app-crashing bugs appear, and do not receive support-team answers on the developer forum. The practical reason to hold here is to avoid both the later minSdk 23 increase and the migration changes introduced after 3.34.0, but this is the weakest support posture of the listed options.

When to choose

Use this only if 3.35.1 is still not viable in the short term because you must remain below the 3.35.x line as well as avoid later blockers such as compileSdk 35 or AGP 8.6.0 readiness, removed deprecated APIs, or the minSdk 23 increase. Choose 3.34.0 only when those combined constraints leave no realistic short-term move beyond 3.34.x.

Tradeoffs

Lowest immediate engineering disruption, but highest platform risk because Google explicitly warns that ad serving is not guaranteed on deprecated versions and support responses are unavailable.

Cautions

3.34.0 has a documented known issue for apps without Java 8+ API desugaring on Android API 25 and lower that may cause crashes.

Sources

Facts updated: 2026-03-20
Published: 2026-04-03

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "Should I upgrade to IMA DAI Android Deprecated SDK Branch Risk now?"
Missing something? Request coverage