Troubleshooting
“Full Disk Access Required”
The helper tried to mount on a folder that macOS protects (Desktop, Documents, Downloads, iCloud Drive and similar) without Full Disk Access. Click the alert’s button, or open System Settings › Privacy & Security › Full Disk Access, add the RAM Folder helper and turn it on, then try again.
With the command line running without
the helper (through sudo), macOS checks the
terminal app instead: give your terminal Full Disk
Access, or use an unprotected folder.
“This location can’t be used” for a folder inside ~/Library/Containers
~/Library/Containers and
~/Library/Group Containers belong to macOS’s app sandbox.
macOS refuses any mount inside them, and Full Disk Access can’t
override that. It is a macOS restriction, not a RAM Folder one:
choose a folder outside these two locations.
RAM Folder says the helper isn’t available, or nothing happens when I mount
The background helper isn’t approved, or macOS has disabled it (this can happen after a macOS update, or when the app was moved):
- Open System Settings › General › Login Items & Extensions and make sure RAM Folder is allowed in the background.
- If it is already allowed, turn it off and on again, then relaunch RAM Folder.
- Keep
RAM Folder.appin/Applications. Moving the app back there and relaunching it registers the helper again.
“Saved with issues”, or the folder couldn’t be updated
The last step of the save, copying the snapshot into your folder, failed. Your data is safe in the snapshot, and RAM Folder trusts the snapshot over the folder until a save succeeds (see Data safety). The usual causes:
- Permissions or locked files: RAM Folder already clears Finder’s Locked flag and retries once. If it still fails, check who owns the folder and its files.
- Full disk: free some space on the disk that holds the folder.
- Full Disk Access: needed if the folder is in a protected location.
Then mount and eject the RAM folder once: a successful save clears the problem.
A save ended with “interrupted”
The RAM folder disappeared while it was being saved, usually because of a forced eject. What was copied before is in the snapshot, the rest was lost with the RAM contents. Nothing is corrupted: the next save simply picks up from what is in RAM then.
Ejecting is stuck on an app
That app doesn’t quit, most often because it is showing its own “save
changes?” dialog. Switch to it and answer the dialog, or click
Force Quit on its row (its unsaved work is lost). You
can also choose Ignore to leave it running; see Mounting
& ejecting. A Terminal window whose current directory is in the
RAM folder also blocks the eject: cd elsewhere.
The RAM folder won’t mount: the folder is too large
The folder now holds more than the RAM folder’s size, usually because files were added to it while the RAM folder was unmounted. Increase the size and mount again. The folder is not modified by the failed attempt.
My remote RAM folder won’t mount offline
Its latest save is in your bucket only, so RAM Folder needs the network to restore it, and refuses to mount it with missing files. Reconnect and mount again. See Remote storage.
My files look different in the RAM folder and in the folder
Check the timing before assuming anything is lost:
- While mounted, the path shows the RAM contents. The folder underneath is hidden, and only as recent as the last unmount.
- While unmounted, the path shows the folder, which is exactly what the next mount starts from, deletions included.
- A few hidden macOS files are never synced: see Synchronization.
- Permissions and Finder tags aren’t carried by the sync: see Synchronization.
If files you expect are in neither place, look in the snapshot and in the recovery folder before doing anything else, and don’t mount the RAM folder again yet: see Data safety.
Where does RAM Folder keep its own files?
Everything is in
~/Library/Application Support/RAM Folder/:
| Path | Contents |
|---|---|
repository.db |
The list of your RAM folders and their settings (not their files) |
sync/<name>-<id>.noindex/ |
Each RAM folder’s snapshot and save status; see Synchronization |
recovered/ |
Snapshots kept aside after a failed save during a delete |
license-store.json |
Your license, encrypted for this Mac |
storage-credentials.json |
Remote storage keys, encrypted for this Mac |
Can I clean up that folder by hand?
Only while RAM Folder is closed, and carefully:
sync/containers of RAM folders you have already deleted can go (RAM Folder normally removes them itself).- Never delete a
sync/container holding arestore-pending.json(or oldermirror-pending.json) file. Its snapshot holds saves your folder never received. recovered/is yours to sort: copy out what you need, then delete the rest.- Don’t edit
repository.db: add and remove RAM folders from the app or the command line.
How do I uninstall RAM Folder?
- For each RAM folder you want to keep as a normal folder, delete it in the app with Keep folder. Its files stay in the folder.
- Quit RAM Folder and move it to the Trash. Remove
/usr/local/bin/ram-folderif you installed the command line. If RAM Folder still appears in System Settings › General › Login Items & Extensions, turn it off there. - Optionally, delete
~/Library/Application Support/RAM Folder/, after checking the cautions above.
Something else is wrong
Use Help › Ask a Question… or Help › Submit
a Feature Request / Bug Report…. For command-line issues,
running the command again with --debug prints detailed logs
that help us find the problem.