Failed to upload attachment on Android app
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Describe the bug
Got the following error while trying to upload a 4 page pdf as an attacent to a card on android via the apps own upload function
Client details:
- OS: Android, GrapheneOS
- Version latest
- Device: Google Pixel 8a
Logs
Nextcloud log (data/nextcloud.log)
App Version: 1.24.7
App Version Code: 1024007
Server App Version: 1.16.3
App Flavor: fdroid
Files App Version Code: 330000190 (PROD)
OS Version: 6.1.166-android14-11-gc2a63a5bb1f3(2026040801)
OS API Level: 36
Device: akita
Manufacturer: Google
Model (and Product): Pixel 8a (akita)
it.niedermann.nextcloud.deck.exceptions.UploadAttachmentFailedException: Unknown URI scheme
at it.niedermann.nextcloud.deck.ui.card.attachments.CardAttachmentsFragment$5.onError(CardAttachmentsFragment.java:387)
at it.niedermann.nextcloud.deck.remote.api.ResponseCallback$1.onError(ResponseCallback.java:76)
at it.niedermann.nextcloud.deck.remote.helpers.DataPropagationHelper$1.lambda$onError$1(DataPropagationHelper.java:70)
at it.niedermann.nextcloud.deck.remote.helpers.DataPropagationHelper$1$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
at it.niedermann.nextcloud.deck.util.ExecutorServiceProvider$RetryableRunnable.run(ExecutorServiceProvider.java:66)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:520)
at java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
at java.lang.Thread.run(Thread.java:1563)
Caused by: com.nextcloud.android.sso.exceptions.NextcloudHttpRequestFailedException: HTTP request failed with HTTP status-code: 500
at it.niedermann.nextcloud.deck.remote.api.RequestHelper$ResponseConsumer.onResponse(RequestHelper.java:86)
at com.nextcloud.android.sso.helper.Retrofit2Helper$1.lambda$enqueue$0(Retrofit2Helper.java:71)
at com.nextcloud.android.sso.helper.Retrofit2Helper$1.$r8$lambda$lvTGXWzn448UkBzanOoTybLr_2w(Unknown Source:0)
at com.nextcloud.android.sso.helper.Retrofit2Helper$1$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
... 1 more
Caused by: java.lang.RuntimeException: HTTP StatusCode wasn't 2xx:
Got [HTTP 500] for Call [GET http://example.com/index.php/apps/deck/api/v1.0/boards/12/stacks/65/cards/370/attachments] with Message:
[java.lang.IllegalStateException: {"status":500,"message":"Internal server error: Please contact the server administrator if this error reappears multiple times, please include the request ID "i9oJKh6h9mgkJecW9IQc" below in your report.","requestId":"i9oJKh6h9mgkJecW9IQc"}
]
at it.niedermann.nextcloud.deck.remote.api.RequestHelper$ResponseConsumer.buildCause(RequestHelper.java:103)
... 5 more
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
Start with CardAttachmentsFragment.java around the reported error line, then trace the attachment request through RequestHelper.java and the GET /boards/12/stacks/65/cards/370/attachments endpoint. Reproduce the upload on Android and inspect the server response and request path. Done means identifying and fixing the cause of the HTTP 500 or documenting the confirmed server-side dependency with a passing regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100