Mobile SDK Conflict Doctor

🩺 Find the real cause

Android SDK errors can stop a build with a wall of Gradle text. Mobile SDK Conflict Doctor turns that mess into a clear report. It shows what was found, where it came from, and what to check next.

🔎 Scan the whole Android setup

Scan AAR and JAR files, Android library folders, Maven and EDM4U data, manifests, Gradle templates, rules, properties, and native libraries. See the package, asset folder, file, and line behind each item.

⚠️ Catch risky conflicts

Find duplicate Java classes, duplicate libraries, version limits, manifest clashes, missing ABIs, native library copies, and AndroidX or Jetifier problems. Results are split into Detected, Likely, and Informational groups, so a guess is never shown as a fact.

🧩 Make build errors easier

Import a or Gradle log. Known error shapes are linked to project evidence. Unknown errors stay unknown. The tool does not make up a fix.

🛡️ Fix with care

Most fixes are clear steps you review and make yourself. One guarded AndroidX or Jetifier case can show an exact change, ask for approval, save a backup, and support rollback. Generated Gradle output and package files are never changed.

📊 Compare and share

Save a healthy baseline, then see what was added, removed, or changed. Export JSON, Markdown, HTML, and a redacted support set. Run scans and exports from batch mode for CI.

Mobile SDK Conflict Doctor works beside EDM4U. It does not replace it. It never downloads SDKs, changes packages, or uploads your data.

📄Documentation