icon

English

icon

Vietnamese

icon

English

  • Facebook
  • Twitter
  • Youtube
  • Instagram
  • Tiktok
FAQ

Câu hỏi thường gặp

Nếu bạn có bất kỳ câu hỏi nào, đừng ngần ngại! Hãy nhấn vào nút "Liên hệ" để gửi thông tin của bạn qua mẫu đơn. Chúng tôi rất mong nhận được ý kiến của bạn!

Liên hệ

Why does the browser open when clicking on the attached file?

  • The Deck server app supports two different types of attachments:

  • Attachments added prior to Deck server 1.3 have been added as deck_file attachments
  • Attachments added with Deck server 1.3 or later are added as file attachments
  • The latter are stored as regular files in your Nextcloud, usually in the /Deck folder of your account.
    Only file attachments can display preview images and be opened directly, while deck_file attachments are only available via the Web UI.
    We have opened a feature request to implement an occ migration command, but the current state of implementation is unclear.

How can I receive notifications when it's due?

When a card reaches its due date, users usually want to receive notifications. The Deck app can send push notifications to you, which are displayed in the browser, via the Nextcloud Desktop sync client and with the Nextcloud Android app. Even if you don't necessarily need the Deck Android app, it provides enhanced integration starting from Nextcloud Android app 3.14.2 and Deck Android 1.10.x: Clicking on a notification will directly open the relevant card in the Deck Android app.

To make all this work, you will need two things:

  1. Ensure that your Nextcloud Android app can receive push notifications (You will need Google Play services for this)
  2. Configure in your user settings that you want to receive push notifications:
    • Click on your profile picture in the top right corner of the browser
    • Choose "settings" and then "activities" in the left sidebar.
    • Enable the checkbox Changes in the Deck app

Why didn't you provide an option for...?

We default to prioritizing simplicity over providing an option for every edge case. Our resources are quite limited, so we have to carefully consider introducing new options.

  1. Quickly implementing a feature, but who will maintain it over the next 5 years?
  2. Each option significantly increases the test matrix and leads to large efforts to test each combination
  3. Each option increases the number of possible configurations, making issue tracking more difficult
  4. Each option increases visual noise for those who won't use the options
  5. Each option introduces additional maintenance effort, making working on actual features increasingly difficult over time
  6. Each option introduces new side effects, potentially leading to undiscovered bugs or breaking existing features
  7. The Android app aims for feature parity with the corresponding server app.

I encountered an error.

There are too many different environments to be able to test each one individually.

First, make sure you have updated and tested with the latest versions available of both this app and the Deck server app.

In case you receive a NextcloudApiNotRespondingException, try disabling battery optimization for both apps. In all other cases, please try clearing the storage of both apps, Nextcloud Android and Nextcloud Deck Android.

You can do this by navigating to:

Android settings
       ↓
     Apps
       ↓
Nextcloud / Deck 
       ↓
    Storage
       ↓
 Clear storage

Often there are issues with the state of the server app. Try creating a new test account on your Nextcloud instance and connect to it. If no errors occur, share the boards of your real account step-by-step with your test account to find the problematic board.

If the issue persists, please open a bug report in our issue tracking system.

Why was my error report closed?

As stated in the bug template, we reserve the right to close issues that are not adequately filled out in the issue template. The information we request is necessary immediately, even if it seems unimportant or irrelevant to you.

We have very limited resources and capabilities, and we genuinely want to help you fix various bugs, but we cannot know your environment, the various software versions, stores you have used. Therefore, providing specific steps to reproduce is crucial.

We also decide to close issues if the original reporter does not respond within a certain timeframe. We typically respond to issues within an 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 reported from last week may no longer be relevant.
  2. We lose context of a report or a question over time. We have many things to care about, and diving deep into an issue and then relying on a response that never comes is a waste of our limited entertainment time.