All apk install functions will soon be removed

[ghisler(Author)]

Where is the problem? People who want to install apks shouldn't have a problem to install Total Commander from apk either (there is still a full featured download version). And those who don't want to install apks will not care.

[charly_35]

Hello,
I'm not an Android dev ... But the originals file manager and browser from Android are able to do apk installation.
Could it be possible that TC will "ask" this file manager or browser to do the apk installation by the use of API ?

[ghisler(Author)]

I have tried it via Chrome, but it re-downloads the file (duplicates it) before installing it. It also cannot install multi-part apk files. Most modern apps are multi-part.

[nbsp]

2ghisler,

I do not think that Google sent you those ambiguous messages (that they will remove TC from the Play Store) because of the apk install feature.

Rather, I think that they saw the description "www.ghisler.com" under the "+ Add plugins (download)..." entry and thought that TC was installing apps from there.

Now that you replaced the description with "Google Play" I think you should try to re-add the apk install feature to the Play Store version of TC and see if Google says anything.

[ghisler(Author)]

The big problem is: I don't know why they sent it. I asked them multiple time (via dispute) but they didn't want to tell me (or didn't know either what triggered the Google bot).

I already got two warnings, so when I will get a 3rd, all my apps will be removed and all my Google accounts closed. I don't want to risk that for this function, sorry.

[Som30ne]

*The installer paradox*
I understand that google prevents TotalCommander that was installed from Play Store to install other apps.
From this I think it will do so for all other file managers.
Only apps that were not installed from the Play Store would be able to install other apps.
But --- no apps could install other apps, as they are downloaded from Play Store, and thus -
would not allow to install the TC version that is able to install other apps.

@ghisler
My suggestion:
Make the installer feature as a plugin that itself does not require install.
A zip package, that can be extracted to some location accessible for write by a non superUser,
instead of requiring installation of another app altogether.

**I do not know if executable code can be put by a non superUser and be executed,
But if TC can run installer without SU I tend to believe it is possible

[ghisler(Author)]

Make the installer feature as a plugin that itself does not require install.
A zip package, that can be extracted to some location accessible for write by a non superUser,
instead of requiring installation of another app altogether.

This is also not allowed and will result in the removal of the app. I could implement it as a separate apk, as long as I don't call it explicitly (e.g. the user would have to make an internal association). But then multi-part apks couldn't be installed either.

[Som30ne]

This is also not allowed and will result in the removal of the app. I could implement it as a separate apk, as long as I don't call it explicitly (e.g. the user would have to make an internal association). But then multi-part apks couldn't be installed either.

Thank you for the quick reply.
I do not understand the meaning of 'this' that is not allowed.
Is it not allowed to run code that was not installed by an APK ?
Is it not allowed to put executable code by a user ?

If the plugin needs to be a separate APK,
and it is an APK that installs other APKs, it will also not be allowed on the Play Store (if I understand correctly)
(Or maybe it will be allowed if it is declared clearly that this is the intension of this specific plugin ?)
And if it is not allowed in the Play store, we are back to the installer paradox loop again -
Only apps not from the play store can install other apps, and since all apps are from the Play store,
you cannot install apps that are not from Play store


Maybe it is allowed to add a 'generic' plugin definition mechanism,
'manually configure' plugin -
not a 'direct access' but some process to 'add plugin' by the user,
and specify the location and executable either by text input, or by browsing the filesystem.

This way it is generic enough to say that it's the user's choice to define and run.

[ghisler(Author)]

It's very broad what they don't allow, see:
https://support.google.com/googleplay/android-developer/answer/9888379#zippy=%2Cexamples-of-common-violations
Example:

Apps or third party code (e.g., SDKs) that download executable code, such as dex files or native code, from a source other than Google Play.

[mikhoul]

When updating this morning I found the sad news trying to install an APK.

I installed the 3.32d version that should restore the install function, even the latest beta here from the forum and even v3.31 but the install function don't appear in the menu ????

Image: https://i.imgur.com/4Jwi4rb.png

Image: https://i.imgur.com/Q1KhjbL.png


Also I've uninstalled completely TC, cleared cache/data before reinstalling TC,

What could I do to have back the installing APK function back ?

I'm under Android 9.

[ghisler(Author)]

Please read the announcement in this forum:
viewtopic.php?t=76644

[mikhoul]

Please read the announcement in this forum:
viewtopic.php?t=76644

Thanks for the quick reply,

Yes I've read the announcement and I've installed the "latest Total Commander APK files (unrestricted version with included apk installer):
direct download (combined installer)" but the problem is that even with the unrestricted version the install item in the menu don't come back ?

This is the menu I have with the unrestricted version:
Image: https://i.imgur.com/Te3dgzP.png


It's like some old data from the restricted version prevent the unrestricted version to show the install item in the menu ????

[Som30ne]

It's very broad what they don't allow, see:
https://support.google.com/googleplay/android-developer/answer/9888379#zippy=%2Cexamples-of-common-violations
Example:

Apps or third party code (e.g., SDKs) that download executable code, such as dex files or native code, from a source other than Google Play.

I understand that download is not allowed.
But in case there is a zip file on the device,
(first step)
TC can extract it somewhere.
(Second Step)
Then - in TC you would have an option, something like :
Add user defined plugin.
This will open a dialog with 2 fields -
Plugin location, and plugin main file.
(Third Step)
User selects the folder in which the plugin resides
User selects the plugin entry point.

TC then will execute the plugin from wherever it was extracted to
(Or copy it to some location from which it can execute it)

TC itself does not have the installer function.

The plugin is not on the Play Store, and is a simple Zip file.

It is a user defined plugin, that was manually configured, and not installed by TC.

The plugin is the element that has the installer in it.

I also saw this:

Apps that install other apps on a device without the user's prior consent.

This hints me that apps that install other apps - are allowed,
but - the app should declare that in advance and require user's consent to allow it to install.

This, to my understanding, allows to have a plugin that is on play store,
and that declares itself to install other apps, and require consent on first run.
But - if it's too risky to have it on play store, I think the unzip+manual definition,
more than satisfies the 'user consent' clause here.
A popup message to get user consent on first run of the plugin on top of all this,
is even more assurance (In my opinion).

[Horst.Epp]

For me all that is a useless discussion.
Christian is forced to have a TC version which confirms to Google rules.
It is not an importand function of a file manager to install APKs, who does this all the time.
One can simply use the Google internal file manager just to install APKs.
All other work can be done using TC.

[555-NASE]

but the problem is that even with the unrestricted version the install item in the menu don't come back ?

Just tab on the file and DO NOT tab + hold it until you open the context menu as shown on your screenshots. Only a single tab opens the installer menu.