The Android engine library

The Android engine builds into an AAR containing Java/Kotlin APIs, a manifest, Android resources and native libraries for selected ABIs. An AAR is not a finished game: its host must provide project data and drive the lifecycle correctly.

Match components

• AAR, native SO libraries and project data must come from compatible builds. Do not mix arbitrary artifacts sharing version 1.0.0.
• The device architecture must be present. Java classes can load before native-library loading fails.
• Minimum/compile SDK and Java must match the current template and dependencies.
• For C#, separately establish the target variant’s .NET components; an ordinary AAR does not prove their presence.

Use Android export for a standalone game. For an existing application use host/fragment embedding. An SDK bridge without a custom host usually needs only a plugin.

Check that the application initializes the engine, locates project data and survives pause/resume with functioning input. ClassNotFoundException concerns Java packaging; UnsatisfiedLinkError concerns native libraries, ABI or their dependencies. No AAR, host integration or device run was built here.