Professional App Update System in Kodular Without Play Store – All Concerns

Discuss
1

I want to discuss building a professional app update system outside the Play Store. My goal is to allow users to download app updates directly from a server or website, with smooth compatibility from Android 5 to 14.

Below is a full list of all concerns and challenges I have faced:

All Concerns & Challenges:

  1. URI and File Access Issues:

ACTION_VIEW or ACTION_OPEN_DOCUMENT_TREE often fails on Android 10+ due to Scoped Storage.

file:// URIs are blocked on Android 7+; only content:// URIs are allowed.

Extensions like TaifunFile or PathToURI frequently give “path to URI conversion not possible” errors, especially on Android 11+.

Some Activity Starter calls result in “Activity not found” errors.

  1. Activity Starter Limitations:

Supports only Action, Data Type, URI.

Cannot add flags or extras, limiting direct APK installation control.

  1. Android Version Fragmentation:

Android 5–9: file URI mostly works.

Android 10: Scoped storage prevents direct file access.

Android 11–14: Strict storage permissions, may require MANAGE_EXTERNAL_STORAGE or SAF.

Solutions often work for one version but fail on others.

  1. APK Installation Restrictions:

Installing APK outside Play Store requires unknown apps permission.

Android 8+ requires per-app installation permission.

Silent install is impossible; user interaction is mandatory.

  1. Download Folder Access Issues:

Cannot reliably open public Downloads folder on all devices.

SAF can open document tree, but user must manually select the folder.

Programmatic redirection often fails.

  1. Path to URI Conversion Errors:

TaifunFile cannot always convert tree URI → path URI, especially Android 11+.

PathToURI extension may return empty URI or crash.

These errors prevent opening or installing the downloaded APK.

  1. Extension Reliability:

TaifunFile, PathToURI, and similar extensions work inconsistently.

Some devices throw security exceptions when attempting file access.

Must handle runtime storage permissions.

Must prompt for install unknown apps permission for APK installation.

Failing to manage these leads to crashes or failed updates.

  1. Scoped Storage Restrictions:

On Android 10+, direct file access is restricted.

Many traditional methods of opening downloads or APKs fail without SAF or content URI.

  1. Device Fragmentation:

Some older devices behave differently than newer ones.

Testing is required for Android 5–14, but no single approach works reliably across all versions.
Any solutions is there to prevent this multiple concerns

2

Hi Anugrah,

Do you need to point to paths other than the ASD?

3

Yes, I want the update system to access public Downloads or other public folders, not just the app-specific directory.

4

Alright, I’ll step aside and let someone else who knows more intervene.

Have you already checked this very useful post by bodymindpower?

Since you told me the app won’t be published on the store, this might be suitable for you.

5

There once was an extension by @bodymindpower, unfortunately it does not have been updated to the latest sdk, so it does not work anymore

But probably @bodymindpower will open source it so probably you @Anugrah or someone else could update it?

Taifun

6

There also is

However there seem to be some issues, too…
But the sources are available. .

Taifun

1 Like