Mobile SDK Conflict Doctor View on Asset Store (opens in new tab)

Package details

Latest version
1.0
Last updated
First released
Unity version
6000.3.9 or later
Package size
139 KB
Files
74
Views in the past week
5

Price tracking

Last checked
Tracked since
Lowest recorded
$39.50 on

Keywords

Mobile SDK Conflict Doctor

by Kevin Bjorvand (opens in new tab)

No ratings yet

Find the real cause of Android SDK conflicts. Trace AAR, JAR, Maven, manifest, and native files, explain Gradle errors, compare healthy baselines, and export clear reports.

Price $79.00

Buy on Asset Store (opens in new tab)

Affiliate link Β· Purchases support this site

Price history

Last 6 months

USD
Price history for Mobile SDK Conflict Doctor, 6 months Current $79.00; lowest $39.50; highest $79.00 in this period. $0 $50 $100 Aug Sep Oct Nov

Asset preview

1 / 8

Mobile SDK Conflict Doctor screenshot 1

Mobile SDK Conflict Doctor screenshot 1

About this asset

🩺 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

From the publisher's Asset Store listing.

Technical details

βœ… Compatibility

Unity 2022.3.41f1 or newer. Exact release checks were run on 2022.3.41f1, 6000.3.9f1, and 6000.4.4f1. This is an editor-only, Android-first tool. It adds no runtime code. Source-only scans do not need Android Build Support. Android builds still do. iOS and CocoaPods are not included in version 1.

πŸ”Ž Scan coverage

Scans AAR, JAR, androidlib, Maven/POM, EDM4U Dependencies.xml, source manifests, Gradle templates, Gradle properties, ProGuard/R8 files, and native .so libraries. It records owners, source paths, source lines, archive entries, ABI data, AndroidX/Jetifier settings, and literal SDK/toolchain evidence.

⚠️ Findings

Checks for duplicate Java classes, duplicate embedded artifacts, Maven version limits, manifest contributors and clashes, duplicate native libraries, missing required ABIs, AndroidX/Jetifier mismatch, and some old Gradle settings. Findings are split into Detected, Likely, and Informational. Preflight predictions are kept separate from build-confirmed results.

🧩 Build logs

Imports or Gradle logs. Known errors use a versioned signature catalog and link back to project evidence. Unknown messages stay Unrecognized and receive no made-up fix.

πŸ“Š Baselines and reports

A healthy baseline is saved at ProjectSettings/MobileSdkConflictDoctor/Baseline.json. Compare added, removed, and changed normalized items. Export JSON, Markdown, HTML, and support-redacted files with a SHA-256 manifest. Redaction covers common paths and secret shapes, but files should still be checked before sharing.

πŸ›‘οΈ Safe changes

Scans are read-only by default. Generated output can be used as evidence but is never edited. Most fixes are manual. The only automatic version 1 edit is one supported AndroidX/Jetifier property change in a project-local Assets/Plugins/Android/gradleTemplate.properties file when clear resolver evidence exists. Apply requires a full diff preview and approval. It creates exact backups, writes a journal, checks the result, rescans, and supports guarded rollback. Packages and generated Gradle files are never change targets.

πŸ€– Batch mode and CI

Execute with:

-batchmode -nographics -projectPath <project> -executeMethod KevinBjorvand.MobileSdkConflictDoctor.MobileSdkConflictDoctorBatch.Run -mobileSdkDoctorOutput <directory>

Options:

-mobileSdkDoctorThreshold detected|likely|information|none

-mobileSdkDoctorLog <path>

-mobileSdkDoctorBaseline <path>

-mobileSdkDoctorIncludeGenerated

Exit codes: 0 pass, 2 threshold met, 3 incomplete scan, 4 bad input or export, and 5 unhandled error. Reports are still written when code 2 fails CI.

πŸ”Œ Public API

MobileSdkProjectScanner.Scan

MobileSdkBuildLogImporter.ImportInto

MobileSdkBaselineComparer.Compare

MobileSdkReportExporter.Export / ExportToDirectory

MobileSdkModelValidator.Validate

MobileSdkRemediationTransactionService.Preview / Apply / Rollback

MobileSdkConflictDoctorBatch.Execute

Public serializable models use namespace KevinBjorvand.MobileSdkConflictDoctor, schema 1, tool 1.0.0.

πŸ”’ Privacy and scope

No SDK downloads. No network upload. No package changes. It does not run, replace, update, or configure EDM4U, Gradle, Android Studio, or SDK installers. It does not promise that every build will succeed.

πŸ“„Documentation

Compatibility

Render pipelines supported in each Unity version
Unity version Built-in URP HDRP
6000.3.9f1 Compatible Compatible Compatible

As listed on the Asset Store.