Insync automatically appending .txt to extensionless files

[RikuXan]

My Insync (1.3.0.36036) on Windows 10 keeps adding .txt to all files without an extension that I create. This only happens while Insync is running and only for files in folders that are managed by Insync. The Insync feed shows “You renamed to .txt”. Is there a solution to this besides closing Insync, creating the file and reopening it?

Kinds regards,
Philipp

[dipesh]

@RikuXan Sorry for such a delayed response. Please send to us the Insync logs at support@insynchq.com so that we could look into this:

How to find the log files

Tray icon is visible Click on the [image] in your tray menu. Click on the ellipsis to show the support center directory [ellipses] Go to support and click on locate logs - We’ll need the logs.db and out.txt files for investigation [4 locate] Tray icon is not visible The following directories contain logs.db and out.txt: Windows %appdata%\Insync You can copy and paste this path directly into Explorer’s address bar, and it will automatically open the folder containing the logs. M…

[sbmehta]

Hi. I’m having a similar problem with Insync 1.3.22 on Windows 10, although it is does not seem to be specific to the .txt extension.

If i create a file into an Insync managed directory, then rename by removing the three-letter extension (e.g., test.abc => test), a few seconds later that extension is re-appended and a message appears in the Insync feed saying “You renamed to .abc”

There seems to be some memory about the extension when initially created. If i rename test.abc to test.txt then to test … it reverts to test.abc, not test.txt.

If the file had no ext at creation, this does not occur. If i pause Insync, rename the file, then resume sync, it does not occur.

Thanks for your help.

                            samar

[Gabriel_Fair]

Is this still a problem? I’m considering buying but won’t if this is an issue. Can someone close this ticket if it isn’t?

[RikuXan]

Problem still occurs on 1.3.22.36179
I finally got around to sending the logs in, forgot to do so when I initially reported this, maybe it’ll be fixed now (though I don’t know if this is actually so hard to reproduce that my logs would be essential to the solution of this)