After clicking the back button of the CallAppBar in the call content builder, it will navigate to the previous context as expected. How can we return to the same ongoing call from there?
We attempted to navigate back to the calling window by passing the call object. However, in every attempt, we received an error from the callParticipantsBuilder. To determine if the issue lies with our implementation or elsewhere, we conducted a test by simply returning a Container() widget in your callParticipantsBuilder, and the error did not occur. Therefore, we suspect there might be an issue with your StreamCallParticipants component. However, this issue does not occur when the call involves only two participants. It arises when there are more than two participants involved in the call. For your reference, I have attached a screenshot of the error and the stack trace from the log when the error occurred.
Stack Trace
Another exception was thrown: 'package:flutter/src/rendering/sliver_multi_box_adaptor.dart': Failed assertion: line 257 pos 16: 'child == null || indexOf(child) > index': is not true.
I/flutter ( 4233): Another exception was thrown: A RenderViewport expected a child of type RenderSliver but received a child of type RenderErrorBox.
I/flutter ( 4233): Another exception was thrown: 'package:flutter/src/widgets/viewport.dart': Failed assertion: line 233 pos 12: '!_doingMountOrUpdate': is not true.
I/flutter ( 4233): Another exception was thrown: Duplicate GlobalKey detected in widget tree.
Customer reported:
After clicking the back button of the CallAppBar in the call content builder, it will navigate to the previous context as expected. How can we return to the same ongoing call from there?
We attempted to navigate back to the calling window by passing the call object. However, in every attempt, we received an error from the
callParticipantsBuilder. To determine if the issue lies with our implementation or elsewhere, we conducted a test by simply returning a Container() widget in yourcallParticipantsBuilder, and the error did not occur. Therefore, we suspect there might be an issue with yourStreamCallParticipantscomponent. However, this issue does not occur when the call involves only two participants. It arises when there are more than two participants involved in the call. For your reference, I have attached a screenshot of the error and the stack trace from the log when the error occurred.Stack Trace