Bizarre problem with new build 2025 R3.1

[Arnaud_N]

What about not wanting to store documents on servers over Internet (privacy)?

[Tim_Parnell]

Git is not a cloud required software. You can use it with a cloud provider, you don’t have to.

If you want to be your own cloud provider, I made that super easy to do with Lifeboat and it doesn’t require payment to use the feature

[Frank_Bicknell]

No, I have been 2025r3 for a few months, and earlier versions for much longer, and I had no issues.

[AlbertoD]

@Frank_Bicknell

No, I have been 2025r3 for a few months

What I mean is: do the same steps as your original post but instead of 2025r3.1 do it with 2025r3. If you have no problems, do the same steps again with 2025r3.1, just to make sure that is a new problem with 2025r3.1.

[Bill_Sanders]

@Greg_O

Just remember, this is kinda like smoking a cigarette when filling your gas tank. You may be lucky enough to never have a problem, but one day it might just explode in your face without warning.

Been there, done that, got the tee-shirt and learned my lesson.

Even with all the signs posted, you still smoked?

[Greg_O]

When I was a kid, I had a job working for a 7up distributor. The guy that was in charge of the event division took us out back one day while smoking a cigar and showed us how to fill the propane cooking tanks… all while having that cigar hanging out of his mouth. We lived that day, only by the grace of god.

[Bill_Sanders]

@Greg_O

The answer is almost always “That was easier than I thought. I should have done this years ago!”

For the longest time I used Google Drive to get my work code to home. After a few instances of Google Drive deciding to stop syncing automatically, and having a zillion copies of my stuff, I broke down and installed GitHub Desktop. So easy a caveman could do it!

[David_Cox]

Avoid One Drive for your Xojo code

A good friend at church told me this morning that his One Drive has been filling up with spam PDF files that spammers are ‘sharing’ with him based on his email address alone. Apparently it is a known issue and he’s trying to turn it off. My concern was whether the spammers could ‘see’ your files, whether the PDF files can contain virus code and whether the PDF files might contain dodgy or explicit content.

Unknown pdf file was just shared to my OneDrive, how do I delete/remove this?...

[Anthony_G_Cyphers]

I run a local Forgejo instance in a docker container on my NAS for private projects and use GitHub for projects I wish to make public. Super easy to setup and use.

[Frank_Bicknell]

Sorry, somehow my reply did not get saved.

So what I said is that I have been using 2025r3 and earlier with no problems. 2 days later upgraded then problems. None of the other applications have any issues.

[AlbertoD]

@Frank_Bicknell

So what I said is that I have been using 2025r3 and earlier with no problems. 2 days later upgraded then problems. None of the other applications have any issues.

I understand that.
What I want to know is that you can do the same steps that you did with r3.1 with r3, that means, install r3 (if you already removed it), copy items from that another app (old app) to re-use in the new app, and not get errors.
Many times a new problem with a new version is because we are doing some things that we usually don’t do. I don’t know if you usually copy items from an old app into a new app.
Also can you create a sample project that you can zip and share here where you:

I can then edit the new app, but the save button in the new app is not enabled after I make a change.

it is very strange that:

I can saveas and it appears to be saving but when I re-run the new app it does not have the changes I just made.

I have seen (in the past) people that save as, the app is saved elsewhere or in different format (binary vs text) and they open the older program instead of the new saved one. I’m not saying that this is happening here, just trying to make sure that the problem is r3.1 and not something else, like OS putting the file in read-only mode for some strange reason.

[AlbertoD]

@Emile_Schwarz

if you save as Xojo Project

And I have received warnings when I use Save As if I’m saving in a folder that is not empty.

As I said, most likely the Save As has nothing to do with the problem. We don’t need to focus on that. Thank you.

[Arnaud_N]

@Greg_O

I use my NAS every day. NAS is an acronym for Network Attached Storage after all. I use mine for storing all kinds of things, quite reliably I would add. I just don’t have applications other than the OS read or write to it.

I was thinking about it further.
So you never directly open or save files on your NAS from applications?
Say you want to open a text file in TextEdit. You’d copy it to your home folder first, save modifications, and move the file back?

[Rick_Araujo]

@Arnaud_N

So you never directly open or save files on your NAS from applications?
Say you want to open a text file in TextEdit. You’d copy it to your home folder first, save modifications, and move the file back?

It’s a risk many people run when what they are doing is not important, because the risk is small, near zero if it is something like a txt note with 10 lines you can write again if the connection drops and your app crashes without a second chance for a new “save as” locally.

Here is what Gemini says (and it is correct, I reviewed it):

The risks of working directly on NAS files:

In most home and small office scenarios, operating directly on files shared on a NAS (Network Attached Storage) is not inherently “dangerous,” but it does introduce specific risks that don’t exist with local storage.

Whether it is safe for you depends entirely on the type of work you are doing and the reliability of your network, your devices, its software and OS.

---

1. The Core Risks

Operating on a NAS over a network (using protocols like SMB or NFS) means your data is constantly traveling back and forth. This creates three primary vulnerabilities:

A. Data Corruption via Network Drops

When you save a file to a local drive, the transfer is nearly instantaneous. On a NAS, if your Wi-Fi glitches or an ethernet cable is bumped while an application is “writing” a save, the file can end up half-written.

• Result: A corrupted, unreadable file.

B. File Locking Issues (The “C” Word: Collision)

Local drives only have one “boss” (your PC). A NAS is often shared. If two people open the same Excel sheet or Photoshop project simultaneously, and the software doesn’t handle “File Locking” correctly, the last person to hit “Save” will overwrite the other person’s work. If two or more processes operates on the same file (you, a virus scanner, a file sync process…) locking conflicts and desynchronization of contents (even a 4k block of data loss in the middle of a large file) may be possible.

C. Application Instability

Many professional applications (like Adobe Premiere, Lightroom, or CAD software) are designed to expect the low latency of a local disk. If the network lag (latency) is too high, the program may hang, crash, or fail to auto-save, leading to lost progress.

---

2. Comparison: Local vs. NAS Workflow

Feature	Local Disk (SSD/HDD)	NAS (Over Network)
Speed	Extremely Fast (GB/s)	Limited by Network (often ~110MB/s)
Reliability	High (Direct Connection)	Moderate (Network Dependent)
“Collaboration”	None (controlled single access)	High (Multi “User” Access)
Risk of Corruption	Low	Higher

---

3. When is it “Dangerous”?

You should avoid direct NAS operation in these specific cases:

• Database Files: Never run a live database (like a Plex library or an active SQL database) over a standard SMB share; it is a recipe for corruption.
• Heavy Video Editing: Unless you have a 10GbE network, editing 4K footage directly off a NAS will be sluggish and prone to “dropped frames” or crashes.
• Unstable Wi-Fi: If you are on a shaky Wi-Fi connection, avoid saving large, complex files (like 1GB+ .PSD files) directly to the NAS.

---

4. Best Practices for Safety

If you want the convenience of a NAS without the risk, follow these “Pro” habits:

1. The “Working Copy” Method: Copy the file to your desktop, edit it, and move it back to the NAS when finished. This is the safest way to work.
2. Use Wired Ethernet: Never do heavy file operations over Wi-Fi if you can avoid it. Use a Cat6 cable for a stable connection.
3. Enable Snapshots: If your NAS supports Btrfs or ZFS (like most Synology or TrueNAS units), enable “Snapshots.” If a file gets corrupted during a save, you can “roll back” to the version from 15 minutes ago.
4. UPS (Uninterruptible Power Supply): Plug your NAS into a UPS. A power flicker during a write operation is the #1 cause of NAS file system corruption.

[Greg_O]

@Arnaud_N

Say you want to open a text file in TextEdit. You’d copy it to your home folder first, save modifications, and move the file back?

Yup. But as I said, I don’t use it that way. My NAS is mostly used as a transfer station. I upload files to it for later download somewhere else. I can’t remember a time when I’ve wanted to directly modify a file that’s on there.