This is expected behavior for APKs that are not installed through a mobile app store.

The usual sequence is:

• download the latest APK from GitHub Releases
• allow unknown-source installation when Android prompts
• open the app and let the runtime unpack on first launch

If you need more confidence first, the source repository and release notes are both linked from the site.

The safer migration flow is still export first, then import into SillyDroid.

That lets config, characters, chats, and extensions move together instead of forcing manual directory recovery.

The same ZIP flow also works as a cleaner backup path when switching devices.

SillyDroid tries to bundle the main runtime path directly into the APK, but optional extensions are still separate moving parts.

The practical interpretation is:

• get the base install and unpack flow working first
• install extensions only when you actually need them
• if the network is restricted, prioritize the core app flow before add-ons