Skip to content
New issue

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on "Join call" is not shown to user #13077

Closed
nickvergessen opened this issue Aug 21, 2024 · 1 comment · Fixed by #13133
Closed

Error on "Join call" is not shown to user #13077

nickvergessen opened this issue Aug 21, 2024 · 1 comment · Fixed by #13133

Comments

@nickvergessen
Copy link
Member

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.

Steps to reproduce

  1. As a user try to join a call
  2. Receive a 400 response, see patch below for hardcoded 400
diff --git a/lib/Controller/CallController.php b/lib/Controller/CallController.php
index 373337913..c8a6fe00f 100644
--- a/lib/Controller/CallController.php
+++ b/lib/Controller/CallController.php
@@ -136,6 +136,7 @@ class CallController extends AEnvironmentAwareController {
        #[RequireParticipant]
        #[RequireReadWriteConversation]
        public function joinCall(?int $flags = null, ?int $forcePermissions = null, bool $silent = false, bool $recordingConsent = false): DataResponse {
+               return new DataResponse(['error' => 'consent'], Http::STATUS_BAD_REQUEST);
                try {
                        $this->validateRecordingConsent($recordingConsent);
                } catch (\InvalidArgumentException) {

Expected behaviour

You see an/the error message

Actual behaviour

Browser warning about leaving the page:
grafik

@Souptik2001
Copy link
Contributor

Hey @nickvergessen I am not sure about the exact design that was required (like whether the error message should be just a toast using showError() or not), but does this look good? -

Screen.Recording.2024-08-24.at.6.15.30.PM.mov

If yes then I have raised a PR for this above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ☑️ Done
Development

Successfully merging a pull request may close this issue.

3 participants