Unactionable notification
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Steps to reproduce
- Occasionally I get a notification on my phone (running iOS) that a new version of the calendar is available.

Expected behaviour
The app or notification itself communicates what to do about this update. It is unclear what the purpose of the notification is and what I should do about it:
- This notification does not impact my use of Nextcloud and does not require me to do anything. In that case I think the notification should not be sent at all.
- This notification makes it possible for me to use new features or fixes bugs. In that case I’d like an easy way to see what changed, for example if opening the app would provide me with an option to open a link to the release notes or so.
- The text indicates mere availability but perhaps I need to do something to install this version that became available (the text didn’t says that it was automatically installed)
Actual behaviour
A notification is received without a clear purpose.
Screenshots
See screenshot above :)
Environment data
iOS version: iOS 15.5
Nextcloud iOS app version: 4.4.0.18
Server operating system: Linux
Web server: nginx
Database:
PHP version:
Nextcloud version: 24.0.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. Start by reproducing the iOS update notification described for Nextcloud iOS 4.4.0.18 and clarify whether it should be suppressed, link to release notes, or explain installation; done means the notification behavior is clear and actionable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100