-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: 3rd party app open in termux broken in latest version #4024
Comments
Did you restart app or run
|
mixplorer version? |
No, Termux version. Either the new version or the prerelease beta. Didn't work with material files either. According to my system, Mixplorer did update recently, but the version of material files is a bit older, and I don't recall the last version of it not working before. Edit: I realized the last post was ambiguous and might have been asking what version of Mixplorer this is. It's this version: com.mixplorer.silver targetSdk 33 |
As always, MiXplorer is broken, both latest stable and beta, older versions have improper usage of RUN_COMMAND intent (search in other issues/discussions). It is stuck in an infinite loop for permission check, until app crashes.
MaterialFiles does not support Termux and only jackpal terminal.
RUN_COMMAND intent works fine for latest beta and there is not issue with Termux, report issues to respective devs of other apps. |
I see, the regression was mixplorer or it was a happy accident it worked before at all. I'll go report it there, sorry for the erroneous report. |
Problem description
Attempting to use a third-party app to open Termux fails. Allow external apps is enabled in Termux properties, and appropriate permissions have been granted where relevant.
Steps to reproduce the behavior.
Enable external apps, open a compatible file manager and attempt to open working directory using Termux, video provided
output.mp4
What is the expected behavior?
The two file managers tested are able to open Termux in the working directory.
System information
The text was updated successfully, but these errors were encountered: