We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[messageId]
Note: Assuming you already have a list of messages in the Messaging Tab
docker logs appwrite
Timestamp: 2024-03-16T14:00:14+00:00 [Error] Method: DELETE [Error] URL: /v1/messaging/messages/:messageId Type: InvalidArgumentException [Error] Message: [messageId] is missing from the params. [Error] File: /usr/src/code/src/Appwrite/Event/Event.php [Error] Line: 396
Issue might be coming from here where the required messageId is deemed missing.
No error by providing the correct messageId.
messageId
Error is thrown due to missing messageId.
Version 1.5.x
MacOS
No response
The text was updated successfully, but these errors were encountered:
Update: The audits.resource label for the linked API Call is set to message/{request.route.messageId} which as per this throws an exception.
audits.resource
message/{request.route.messageId}
Looking at the other labels, it should probably be -
->label('audits.resource', 'message/{request.messageId}')
Sorry, something went wrong.
stnguyen90
Successfully merging a pull request may close this issue.
馃憻 Reproduction steps
Note: Assuming you already have a list of messages in the Messaging Tab
docker logs appwrite
Output -
Issue might be coming from here where the required messageId is deemed missing.
馃憤 Expected behavior
No error by providing the correct
messageId
.馃憥 Actual Behavior
Error is thrown due to missing
messageId
.馃幉 Appwrite version
Version 1.5.x
馃捇 Operating system
MacOS
馃П Your Environment
No response
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: