No longer recognizing untracked files #620
Comments
|
I have been trying to work through this as well. I am able to track modifications on existing files, or adding files through MGit and then modifying them. However any new file is being ignored. |
|
Yes, same. If create the file through MGit, it works. And for some reason, I'm now noticing that if there was a file named "ABC" already in the directory, even if I rename the file to something else like "XYZ", MGit won't let me create a new "ABC" file. No error, just fails silently. Unlike When I try to create a file that I know is there, I do get the error that a file with that name already exists. I suppose it could be a weird interaction with Obsidian, but I don't think that should cause any issues. It should just create the file |
|
Also experienced this on April 7, 2022 |
|
Seeing the same thing; creating a new file for a pre-existing tracked file doesn't seem to pick up external changes, either. |
|
Also experiencing this on Android 11 with One UI 3.0. |
|
Thank you everyone for reporting this. |
|
@maks I understand. Thank you for the update though. It's really going to be unfortunate if they don't grant you the permission, as your app is the best git tool I've found for Android. |
|
I'm happy to download an APK and install it outside of Google play. I'm already doing that with termux and a few other apps. Are you open to posting the built APK on GitHub somewhere? (Pretty please!) |
|
I'm happy to download an APK and / or email someone at Google if it will help persuade the Play Store to grant the permission. |
|
I was also wondering about an APK. I would do it that way as well. Google not giving you this permission has really messed with my workflow |
|
Thank you everyone for your support. |
fdroid is an option, i wouldn't mind downloading directly from github either though Edit: I didn't know the app was already on fdroid |
|
MGit is already on F-Droid, but even installed from there, it doesn't have the 'all files' permission it needs. I assume it needs to be added to the manifest, and then I guess a Play Store edition created without it. |
|
I ended up setting up Termux and following an online guide to get command line git setup. It's annoying because Termux has its own permissions issues. But as long as you are okay with setting up your local repo in one of the places Termux does have access to then it's fine. It recognizes new files. You just have to be okay with doing things on the command line on a phone, which is its own special level of masochistic sometimes. |
|
Would it be possible to use the Storage Access Framework for setting the base directory for your repositories? That's supposed to give you access to all of the files and directories under that one... https://developer.android.com/training/data-storage/shared/documents-files#grant-access-directory |
|
No, because JGit can't deal with that. |
|
@jfmcbrayer Unfortunately not. I've looked into using the SAF in the past but there are couple of showstoppers:
|
|
Thanks, that's terribly unfortunate. |
|
You have access to Download (not tested, info from system log, peoples write it isn't usable) and Documents (tested) directories. Just place Github folder in Documents directory. |
|
@daimoniuma that's interesting. I'll try that out |
|
Although I haven't added untracked files that often so I haven't tried, is it a possible work around to use the "New File" command in MGit to create a blank file and then replace the content? Even this works, it is awkward to write non-text content... Is it possible for MGit to add a function like "Add File", and call an Android file manager, like com.google.android.documentsui , to list untracked file and add the select file to git? |
|
@maks Maybe in your appeal you should point out to google that even though MGit is not aimed at modifying files from other application folders, other applications are to modify files in MGit folder. Thus MGit requires to be able to access files "from" other applications inside it own folder. (Ie also you could point them out that the editor is not part of MGit thus MGit requires to the ability to access files created by the editor application which is ... another application). Also, there is the "access to all file types", you could point to them that in a git repository there are files that are not media files (especially with regards to #640 which I had me rename my ssh private key with a JPG extension to be able to import it in Android up to 11). I am all for an FDroid repo workaround. But it is insane of Google to forbid VCS because if they do not give permission to MGit any VCS ought not to get any better luck. |
|
I think we might be out of luck at this point because I believe that Google
no longer allows full file system access with Android 13, but I could be
wrong.
…On Fri, Sep 9, 2022, 8:02 AM Alban Browaeys ***@***.***> wrote:
@maks <https://github.com/maks> Maybe in your appeal you should point out
to google that even though MGit is not aimed at modifying files from other
application folders, other applications are to modify files in MGit folder.
Thus MGit requires to be able to access files "from" other applications
inside it own folder. (Ie also you could point them out that the editor is
not part of MGit thus MGit requires to the ability to access files created
by the editor application which is ... another application).
Other than them not understanding this point, I am out of guess why they
would have refused MGit access to files created by other applications).
Also, there is the "access to all file types", you could point to them
that in a git repository there are files that are not media files
(especially with regards to #640 <#640>
which I had me rename my ssh private key with a JPG extension to be able to
import it in Android up to 11).
I am all for an FDroid repo workaround. But it is insane of Google to
forbid VCS because if they do not give permission to MGit any VCS ought not
to get any better luck.
—
Reply to this email directly, view it on GitHub
<#620 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE52JMJCM7QVDFMXHAOYCBDV5NGOXANCNFSM5SXVDHJA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I also pointed out the issue that MGit Google Play store version only allows "access to media files". There is the issue of not being able to access files that are not media files out of those MGit creates (the latter I suppose because I guess MGit is still allowed to create pdf, zip, etc., not only files with an extension of mp3, jpg, etc). But currently, you cannot import an ssh key file from MGit without renaming it with a JPG extension (then removing it via MGit UI after the import to a mgit subfolder succeed. |
This solution worked for me! For folks not so familiar with Android, the "permissions manager" is in the Android system settings and not in the app settings. Also, at least on my OnePlus running Android 12, when you go "permissions manager" you are NOT provided with a list of apps to choose from, rather you are presented with a list of permissions categories. At that point choose "Storage" and then from there it sorts by level of permission, starting with apps that have full permissions. Scroll down to the apps that have limited permission, find MGit, click on it and then select "All Files." Now MGit will recognize new files on its own. |
|
I've made one last attempt at trying to make the app compliant with Google Play policies in regards to use of the "All Files access" permission and have resubmitted for review to Google Play. |
|
Sadly Google Play has once again rejected the latest version so that's the end of the line for MGit on Google Play. I will shortly publish a new version on Google Play that will remove support for Android 11 onwards and display a message to that effect, referring users to instead install the app from F-Droid. To help users who would need to upgrade vs uninstalling and re-installing from F-Droid (because F-Droid signs APK's with their own certificate and not mine) I will also begin publishing APK's from CI soon, though I would like to do that only once I have a update check mechanism in place (#669) |
|
Besides of F-Droid and APK`s, is it possible to also make MGit available on Samsung's Galaxy Store? I control my phone by Google Family Link, which does not allow install apps by APK, but it allows me to install apps via preinstalled Galaxy Store... |
|
@yuttai I'll try to look into this as I'm not sure what the requirements are to be able to publish on the Galaxy Store. |
|
Mgit 1.7.0 from F-droid, on Android 13.0.0/Lineage 20 - "Clone failed, Operation not permitted" in both /storage/emulated/0/[Download|Documents]. |
|
It is working fine here. Same version 1.7.0 from F-droid on Android 13. Just cloned a new repo on /storage/.../Documents to test a new clone, worked fine. Are you sure it's not you ssh key or some other issue? |
|
sorry my bad, emacs made a *scratch* file that I accidentally committed and
for some reason isn't valid on Android. check out worked fine after I
removed the file.
…On Sun, Jul 9, 2023, 16:00 Henrique Abreu ***@***.***> wrote:
It is working fine here. Same version 1.7.0 from F-droid on Android 13.
Just cloned a new repo on /storage/.../Documents to test a new clone,
worked fine. Are you sure it's not you ssh key or some other issue?
—
Reply to this email directly, view it on GitHub
<#620 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWJWSWQWCUW6FNVPS3NMS3XPLBRRANCNFSM5SXVDHJA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi. It seems like I have the same issue. I wanted to clone my big repo to my phone, and got the same error message. However, I was able to successfully clone other repos, both public and my private. How does one detect the file which makes Mgit to reject the whole downloaded repo? @maks |
It took me some time to figure it out. Since the private repo I had the issues with is a collection of my notes, their names tend to contain a lot of special characters (in my case The list of the invalid characters one can see here. |
As the function name shows That is why these are not MGit or even Android per see forbidden file characters. These characters are forbidden on Microsoft filesystems which are the only ones we can use on external media on Android (so that Windows users can read these external media). |
|
Are there any updates or a work around for the situation regarding untracked files? |
|
@CodeMazeSolver as told in the preceding comment there is no MGit untracked file bug. But this was explained in this thread already. Only a few last comments talk about an unrelated issue that was due to Android using Microsoft FAT format for external storage (SD cards) to let users read the cards under Windows and ... well FAT not supporting quite a lot of characters. Thus MGit is unable to check out the git repository on FAT FS when such a character is in a filename in the git files. |
and others
Describe the bug
MGit is no longer recognizing untracked files on Android. I know that there is a filesystem issue due to new permissions in Android 11+, but isn't there a "see all files" permission? I know that there are a few apps that have it, such as Solid Explorer.
I have even moved my repo and files to the Documents folder as I saw recommended in some of the Google Play Store review replies. That did not solve the issue either. I have multiple new files that I created with a different app, and I am not seeing them show up in MGit as untracked files like I would expect.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After creating new files they should be seen as untracked files in MGit
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: