File Changes not detected (macOS 13.4.1 (22F82); GitFiend ~0.38-0.42)

[richardstoeckl]

Thank you for this great piece of software!

Since i upgraded somewhere around version 0.38, changes to files are no longer detected. When the changes are added "manually" via git cli (git add testFile.txt && git commit -m "test"), the commit is detected and shown, and I can push the commit without problem. Any additional changes to the commited file are not detected however.

Troubleshooting that did not fix the problem:

• Clear cache and reload
• closing the repo and reopening it
• reinstalling gitfiend (version where it stopped working)
• updating gitfiend
• reinstalling gitfiend (older version)

The only way to get the functionality back, is to remove the repo and clone it again. But after the next app update it stops detecting the changes again.

Thank you for any help!

[GitFiend]

Thanks richardstoeckl, Sorry to hear this isn't working. Do you have any symlinks in your changes? If so, there's a fix coming for this soon. Otherwise, it would be great to see the error message in the dev tools (View -> Toggle Developer Tools). There should be an api response in the network tab for "load_wip_patches".

[richardstoeckl]

Thank you for your response!

There should'nt be any symlinks, at least as far as I understand.

The response gives the following error:

{"Err":"\nPARSE FAILURE AT POSITION 86:\n      SUCCESSFULLY PARSED:\n    \" M .DS_Store\u0000 D LabBook/.ztr-directory\u0000 M LabBook/2023-06-18_CRISPR23-code.md\u0000?? Icon\r\"\n\n    FAILED AT:\n    \"\u0000?? LabBook/2023-06-26_TEST.md\u0000\"\n    "}

As far as I understand, there seems to be a problem with the parsing of the files? But I dont know how the unicode character 'NULL' would be in any of these files? I have attached the file "LabBook/2023-06-26_TEST.md" which also seems to throw the error?

2023-06-26_TEST.md

[GitFiend]

Thanks for the error message. It looks like the "Icon" file has a carriage return in the name. I've updated the parser to support this and will have a release out soon with the fix.

[richardstoeckl]

Thank you for the quick fix. Indeed, deleting the "Icon" file restores proper functionality. Tbh, I don't know how this file was generated there, but updating the parser to support this will be best. Thank you for everything!