diff options
| author | Stefan Niedermann <info@niedermann.it> | 2020-07-09 14:24:56 +0300 |
|---|---|---|
| committer | Stefan Niedermann <info@niedermann.it> | 2020-07-09 14:25:38 +0300 |
| commit | 43928e81751cf18b9f6e7057cc824b1f9479b268 (patch) | |
| tree | c3c76ff238b658a4ef744c13d27c46ff075a1cec /FAQ.md | |
| parent | 18b2e45ba43a87fd2346bce224ddd9e48f51489c (diff) | |
Enhance FAQ
Diffstat (limited to 'FAQ.md')
| -rw-r--r-- | FAQ.md | 14 |
1 files changed, 12 insertions, 2 deletions
@@ -4,6 +4,8 @@ Sorry. There are so many different environments, that it is impossible for us to test each and every constellation. +First of all make sure you have updated to and tried with the latest available versions of both, this app and the [Deck server app](https://apps.nextcloud.com/apps/deck). + In case you receive a `NextcloudApiNotRespondingException`, try to disable the battery optimization for both apps. In all other cases please try to clear the storage of **both** apps, Nextcloud Android **and** Nextcloud Deck Android. @@ -17,7 +19,8 @@ Android settings ↳ Clear storage ``` -Often there is an issue with the state of the server app. Try to create a new test account at your Nextcloud instance and connect to it. If there are no errors, share the boards of your actual account one by one with your test account to find the "faulty" one. +Often there is an issue with the state of the server app. Try to create a new test account at your Nextcloud instance and connect to it. +If there are no errors, share the boards of your actual account one by one with your test account to find the defect one. If the issue persists, [open a bug report in our issue tracker](https://github.com/stefan-niedermann/nextcloud-deck/issues/new?assignees=&labels=bug&template=bug_report.md&title=). @@ -38,4 +41,11 @@ Example for a good description: > 2. Add text to the description\ > 3. Click on the ✕ in the top left\ > 4. Answer "Save" when asking to discard or save the changes\ -> 5. See app crash
\ No newline at end of file +> 5. See app crash + +We also preserve to close issues where the original reporter does not answer within a certain time frame. We usually answer issues within a hour and expect you to respond to our questions within a week. + +This is necessary for two reasons: + +1. We have a rapid development cycle - bugs which have been reported weeks ago might no longer relevant +2. We are loosing the context of a report or a question over the time. We have many things to care about and digging into an issue deep and then relying on an response which is not coming is a waste of our limited free time
\ No newline at end of file |