Failing to add reaction to a message, v2
Open
Nobody has claimed this yet.
feature: chat 💬
needs info
Needs triage
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
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.
- See also : #7334
Steps to reproduce
- Send message in conv (self, others, in 1to1 or group)
- Try to add reaction
- See error
Expected behaviour
Reaction accepted
Actual behaviour
Error 400.
Talk app
Talk app version: 20.1.6
Custom Signaling server configured: no
Custom TURN server configured: no
Custom STUN server configured: no
Browser
Microphone available: no
Camera available: no
Operating system: MacOS 11.5.2 Big Sur
Browser name: Firefox
Browser version: 137.0.2
Browser log
Error 400 (HTTP 2) with content :
{
meta: { status: "failure", statuscode: 400, message: "" }
status: "failure"
statuscode: 400
message: ""
data: []
}
Server configuration
Operating system: Debian 12
Web server: Apache 2
Database: MySQL
PHP version: 8.3
Nextcloud Version: 30.0.10
List of activated apps:
- app_api: 4.0.6
- bruteforcesettings: 3.0.0
- calendar: 5.2.2
- circles: 30.0.0
- cloud_federation_api: 1.13.0
- comments: 1.20.1
- contactsinteraction: 1.11.0
- dashboard: 7.10.0
- dav: 1.31.1
- federatedfilesharing: 1.20.0
- federation: 1.20.0
- files: 2.2.0
- files_downloadlimit: 3.0.0
- files_external: 1.22.0
- files_pdfviewer: 3.0.0
- files_reminders: 1.3.0
- files_sharing: 1.22.0
- files_trashbin: 1.20.1
- files_versions: 1.23.0
- firstrunwizard: 3.0.0
- geoblocker: 0.5.16
- impersonate: 1.17.1
- logreader: 3.0.0
- lookup_server_connector: 1.18.0
- nextcloud_announcements: 2.0.0
- notifications: 3.0.0
- notify_push: 1.0.0
- oauth2: 1.18.1
- password_policy: 2.0.0
- privacy: 2.0.0
- provisioning_api: 1.20.0
- qownnotesapi: 25.2.0
- recommendations: 3.0.0
- related_resources: 1.5.0
- serverinfo: 2.0.0
- settings: 1.13.0
- sharebymail: 1.20.0
- spreed: 20.1.6
- support: 2.0.0
- survey_client: 2.0.0
- systemtags: 1.20.0
- text: 4.1.0
- theming: 2.6.0
- twofactor_backupcodes: 1.19.0
- updatenotification: 1.20.0
- user_status: 1.10.0
- viewer: 3.0.0
- weather_status: 1.10.0
- webhook_listeners: 1.1.0-dev
- workflowengine: 2.12.0
Nextcloud configuration:
{
"system": {
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"REMOVED"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"overwrite.cli.url": "http:\/\/REMOVED",
"dbtype": "mysql",
"version": "30.0.10.1",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbtableprefix": "oc_",
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"logtimezone": "UTC",
"installed": true,
"theme": "",
"loglevel": 2,
"pollinterval": 300000,
"maintenance": false,
"updater.secret": "***REMOVED SENSITIVE VALUE***",
"allow_user_to_change_mail_address": "",
"defaultapp": "spreed",
"reference_opengraph": false,
"session_lifetime": 691200,
"trusted_proxies": "***REMOVED SENSITIVE VALUE***"
}
}
Server log (data/nextcloud.log)
None visible for this action.
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 by comparing this report with #7334 and tracing the Talk reaction request that returns HTTP 400. The report names no source file or test; done means reproducing the failure and making reaction submission succeed without the 400 response, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100