Contact person: Google Play Asset Delivery Troubleshooting

Phone:Show

Email:Show

Location: Marseille, France

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I have a large-scene unity mobile game ready for release but the Google Play Asset Delivery System is holding us back. Asset packs build correctly, yet once the app is uploaded the runtime calls to the Play Asset Delivery APIs misbehave—status codes jump from “pending” to “failed”, downloads stall, and occasionally the install size exceeds the Play console limit even though the packs are flagged as fast-follow. None of the usual fixes (bundletool re-builds, manifest edits, device cache clears) have solved it.

What I need is focused, hands-on help troubleshooting the Asset Delivery APIs themselves. You’ll dig into my current integration, trace the failed responses, and identify the exact cause—whether that’s an incorrect request sequence, missing verification step, or something deeper in the build pipeline. Any guidance on finishing steps for Google Play publishing that fall outside the standard “submit / optimize / update” flow is welcome as well, since my case doesn’t fit neatly into those categories.

I can provide:
• Current Android unity project and Gradle files
• Play Console access to the closed-test track
• Logcat traces and on-device screenshots of the error states

Acceptance criteria:
• Asset packs download reliably on at least two test devices via the Play test track
• No oversize warnings in Play Console and no install-time crashes
• Clear, step-by-step notes so I can reproduce the fix on future updates

Unity PAD, bundletool, Android Studio, and Kotlin or Java debugging experience are essential. If you’ve already rescued a project from similar PAD headaches, your insight will be invaluable." (client-provided description)