Get help
- Bugs, questions and ideas: open an issue on GitHub.
- Security: if you find a vulnerability, please don't post the details in a public issue: report it privately on GitHub instead.
Before writing, the FAQ and the README may already have your answer.
What to include in a bug report
- The version of Plume (or the commit you built) and of iOS, iPadOS or macOS.
- The version of your Nextcloud server, if you know it.
- The steps that lead to the problem, and what you expected to happen.
- Never your password, app password or server address in a public issue: use cloud.example.com instead.
Quick answers
Sign-in doesn't finish
With the Login Flow, Plume waits until you have signed in and approved access in the browser page it opened. If your browser shows an error, check that the server address is the one you use on the web (for example cloud.example.com, or cloud.example.com/nextcloud if your server lives in a folder). You can also sign in with an app password, created in Nextcloud under Settings → Security.
Where is Plume in Finder or the Files app?
On Mac, Plume appears in Finder's sidebar, under Locations. On iPhone and iPad, open the Files app, tap Browse, and Plume is listed under Locations; if it isn't, tap ⋯ → Edit and turn it on.
A change made on the web doesn't show up yet
Changes made elsewhere reach Plume, Finder and the Files app while Plume is open; there is no background refresh yet. Open Plume and the folder updates.
An upload got a different name
Plume never overwrites a file on upload: when a name is taken, the new file is saved as “name 2.ext”.