Using MacOS version 1.5.35 and after upgrading to Golden Gate the auto mount for an rclone drive never happens anymore. I have a plus license active and it used to work before upgrading.
What could be causing this issue?
Hi fubag, sorry this went unanswered for so long.
Please update to RcloneView 1.6.8, which fixes this:
https://downloads.bdrive.com/rclone_view/builds/RcloneView-1.6.8.dmg
What most likely broke isn’t auto-mount but RcloneView itself: on macOS 27, version 1.5.35 quits the moment it starts. Every recent build up to 1.6.6 has this problem, and we confirmed it in the 1.5.35 download. If RcloneView opens automatically when you log in, nothing tells you it has quit, so all you notice is that the drive never mounts. (This thread is about the same problem.)
Because the app can’t start, its built-in updater can’t offer you 1.6.8, so please download it from the link above. Open the DMG, drag RcloneView to Applications, and choose Replace. Your mounts, jobs, settings and Plus license carry over. 1.6.8 also fixes a separate startup issue in 1.5.35 that could make auto-mount skip for Plus users when the license check was slow.
On first launch, macOS may ask whether RcloneView can find devices on your local network and access your Documents folder (where it writes its log file). It’s fine to allow both. Please don’t go back to 1.6.6 or earlier afterwards: those versions don’t start on macOS 27, and they erase RcloneView’s database once 1.6.8 has updated it.
We’ve confirmed that 1.6.8 starts on macOS 27, and the user in the thread above has confirmed it works for them on macOS 27.0.1. If it opens but the drive still doesn’t mount, please send us:
- the lines containing “Auto mount” and “mount:” from
rcloneview_app.login your Documents folder (the exact location is shown in Settings, just below “Save application log to file”) - the Mount type shown when you edit that mount in Mount Manager
Please let us know how 1.6.8 goes.
1 Like