-
Notifications
You must be signed in to change notification settings - Fork 477
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 when start audioVideo after 3.18.1 update #2771
Comments
I'm getting the same issue on For me the Audio Video controller seems to try to get started a few times and then just fails. |
Hello, I'm checking in from the Chime SDK team. If possible, could you provide debug level logs and could you see if you can reproduce the issue using our demo app? Meanwhile, I will try to reproduce this issue on my end and try to track down the error. |
This seems to be where it throws the error
redWorkerCode ?
|
Now, the RED worker code will all come bundled together in a single blob that only needs to be passed to the worker, which will avoid the use of parsing the stringified RED class code via regex since it is possible that the stringified RED class code may come in adifferent format as expected by the regex. This issue was originally found in #2771.
Now, the RED worker code will all come bundled together in a single blob that only needs to be passed to the worker, which will avoid the use of parsing the stringified RED class code via regex since it is possible that the stringified RED class code may come in a different format as expected by the regex. This issue was originally found in #2771.
Now, the RED worker code will all come bundled together in a single blob that only needs to be passed to the worker, which will avoid the use of parsing the stringified RED class code via regex since it is possible that the stringified RED class code may come in a different format as expected by the regex. This issue was originally found in #2771.
We have tried to upgrade AWS Chime to version 18.1 and we have the same issue. We have checked the version 18.0 and problem does not appear.
|
@ltrung yes, this is the point where I get the error with message: "Cannot read properties of null (reading '1')" The redWorkerCode is
|
@ltrung I did a link with the branch that you ask in my project, but I got the following error |
@maisasb Is it possible for you to send a link to the repo/branch that you are currently using to test this issue? The discrepancy seems to lie in the different build systems used for your project and our project and I'd like to be able to test the build in your project more reliably. |
We are still working on a fix for this issue as it seems that the current fix attempt is still not working. However, for anybody that is currently blocked by this issue, here is a quick fix. The issue is caused by logic in our new Audio Redundancy feature that was released in 3.18.0, but this feature can be disabled anytime before
anytime before |
…rker code stays intact and is able to be loaded The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
…rker code stays intact and is able to be loaded The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
@maisasb @aguasch1 @sevgit We have updated the potential fix in #2772. Can you again try pulling that branch and verify if it fixes your issue? When testing please do not use this line |
…rker code stays intact and is able to be loaded The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
@dinmin-amzn It worked! 🎉 |
@maisasb Thank you for verifying the fix. Were you able to get any debug logs from your latest test? You can get debug level logs by using the |
@maisasb Did you remove the |
@dinmin-amzn the log
|
@dinmin-amzn yes, I removed that line |
@maisasb Are you available for a Chime call? I'd like to see why the redundant audio worker is not starting. |
@dinmin-amzn yes |
@maisasb Please try joining at this link https://chime.aws/2333969980 and let me know if the link is not working. |
Confirmed with @maisasb that the latest fix is working and that the redundant audio worker is able to be setup. We will move forward with this fix. |
@maisasb Could you send some of the debug logs from the project that had the |
|
@maisasb One last thing I forgot to verify, are you able to see the |
@dinmin-amzn Yes
This logs are from the other project that was not working |
@maisasb Thank you again for sending those logs. Glad you were able to fix the dependency issue in the main project! |
…rker code stays intact and is able to be loaded The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
…rker code stays intact and is able to be loaded The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
…rker code stays intact and is able to be loaded The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
…rker code stays intact and is able to be loaded The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
…rker code stays intact and is able to be loaded (#2772) The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
…rker code stays intact and is able to be loaded (#2772) The redundant audio worker code string may vary based on the build system of different projects. Because of this, certain build systems will cause invalid worker code to be generated and the redundant audio worker will not be able to run. Now, the redundant audio worker code is saved at build time so that all clients can run the redundant audio worker with the same exact code, regardless of the client's build system. This issue was originally found in #2771.
Is the fix to rollback? My audio has stopped working with: meetingManager.audioVideo.setAudioProfile(new AudioProfile(null, false)); |
What happened and what did you expect to happen?
After updated to 3.18.1 I started to get an error to initialize new meeting. I didn't change the code and start to get this error:
The audio video controller will reconnect due to status code TaskFailed and error: serial group task AudioVideoStart/b03cc98d-2348-4055-8ff6-a93ed3e82713/d525b3b3-734f-f00d-4613-c96e4a92c3ce was canceled due to subtask AudioVideoStart/b03cc98d-2348-4055-8ff6-a93ed3e82713/d525b3b3-734f-f00d-4613-c96e4a92c3ce/Timeout15000ms error: serial group task AudioVideoStart/b03cc98d-2348-4055-8ff6-a93ed3e82713/d525b3b3-734f-f00d-4613-c96e4a92c3ce/Timeout15000ms/Peer was canceled due to subtask AudioVideoStart/b03cc98d-2348-4055-8ff6-a93ed3e82713/d525b3b3-734f-f00d-4613-c96e4a92c3ce/Timeout15000ms/Peer/SubscribeAndReceiveSubscribeAckTask (once) error: Cannot read properties of null (reading '1')
This error occur after audioVideo.start()
I followed this documentation to create the configuration:
https://github.com/aws/amazon-chime-sdk-js/blob/main/guides/03_API_Overview.md
Have you reviewed our existing documentation?
Reproduction steps
This is the configuration that I use to start the meeting, without the subscribers and observers
In version 3.17.0 works, but in 3.18.0 start to get error.
Amazon Chime SDK for JavaScript version
3.18.1
What browsers are you seeing the problem on?
chrome
Browser version
117.0.5938.132
Meeting and Attendee ID Information.
No response
Browser console logs
The text was updated successfully, but these errors were encountered: