@ticorrian.heard I can try to override the current version used in flutter_zoom_videosdk, to version 2.3.5 on my project’s Podfile, but I have some concerns..
Is the 2.3.5 API version compatible with 2.3.0? I can mention that version 2.3.5 offers in-app sharing while 2.3.0 doesn’t have this feature yet. To use this feature, I’ll have to make the “wrapper” thing that flutter_zoom_videosdk does by hand. This is just an example.. Any other API differences that may have will cause me a lot of headache to fix….
Also, as the flutter_zoom_videosdk is not available on github (At least I couldn’t find it) I can’t fork it and do this upgrade by myself..
My point is, why does your team not keeping flutter_zoom_videosdk synchronized with latest Android/iOS SDK changes? I think this will benefit everyone..
Hi @Emerson1@chen2 I’m in talks with engineering and they are requesting logs of this issue reproduced. Would you be able to provide this? I’ve also got word from some of my team members a similar issue was reproduced internally with React Native but still confirming if there is a correlation.
But the flutter sdk 2.3.0 still use iOS sdk 2.3.0. Zoom Video SDK for Flutter is a Flutter wrapper around the Zoom Video SDKs for iOS and Android. So we run flutter in iOS still not use the 2.3.5 , so the issues still there
The same for me. There are no error logs, just a black screen. The only way I was able to “solve” that was starting the call with disabled video and let users enable it after some seconds. This is not - by far - the expected acceptable behavior.
Has the customer tried to reproduce the issue in our sample app? Since we cannot reproduce the issue and there is no log, we cannot provide with further help.
The screenshot is from our sample app, the fullscreen video can render on Android.
We’re currently facing an issue on iOS devices. The development team has shared screenshots demonstrating that the functionality works seamlessly on Android.
Could you please double-check the behaviour specifically on iOS with the dev team? There may be a platform-specific discrepancy that requires further investigation.
@Emerson1 I am discussing this with the flutter team now.
@Maulik Understood. The roadblock here is that engineering needs more information to be able to properly investigate this. At the moment, they only have screenshots and cannot replicate the issue in our environment with the sample app. I’ll clarify with them to make sure they’re testing iOS.
Are you also able to test with iOS on the sample app and reproduce the issue?
Hi, I would like to express my concern regarding this issue, I noticed that the targeted release date for the fix is currently set for November. Could you please advise if there is any possibility of an earlier release? Many of our users are relying on this bug fix in order to ensure a smoother and more effective integration with Zoom.
At the moment, my only workaround is to downgrade from flutter_zoom_videosdk 2.3.0 to flutter_zoom_videosdk 1.14.0, which is what I’m currently using for the MVP release. While this version works, I strongly require access to the latest release to move forward, but unfortunately, I haven’t been able to find another solution yet.
@ticorrian.heard we have updated the Flutter SDK to version 3.35.4 and the Flutter VideoSDK to version to 2.3.0 , also we are testing on IOS 26 - This blank video issue is still happening and now my workaround of starting the call with video disabled is not working anymore.. This is a major issue…
Every time I try to turn the camera on: <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:299 <<<< FigCaptureSourceRemote >>>> Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:569) - (err=-17281)