-
Notifications
You must be signed in to change notification settings - Fork 43
NoSuchMethodError: 'callMethodVarArgs' when calling getStats() #60
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
Comments
+1 on this |
@EvertonMJunior I see that you made this change: StiftTechnologies@8431d6c That change makes sense, because otherwise the variable type is not known. Is that enough to fix the issue? Maybe you could make a PR to this repo to suggest the change? |
@renefloor yes, the change did remove the error presented above, I didn't make a PR yet because everything worked on debug mode, but I ran into other issues I didn't have the time to debug yet on Web release mode, so I'm not 100% sure if the problem was actually solved, if it's solved only in debug for some reason, or if it was solved and there are other issues that hadn't appeared yet due to not being able to proceed because of this issue. I preferred to keep using the 1.4.10 version for now as I don't have the time to pin it down and solve it myself now. But feel free to try it too! |
@EvertonMJunior for me it also fixed it for debug mode, but not for release mode. The error did change though, I got: This makes me look closer to the function. On line 338 it's calling
So I suspect that The original logs also said:
So I guess that |
@EvertonMJunior I got it working by combining your fix with a change on line 338. Edit: opened a PR |
Related issue: flutter-webrtc/flutter-webrtc#1781
In this release
stats.callMethodVarArgs('forEach'.toJS, [ ... ]);
was introduced:439c8ef#diff-5523a536631aaa1af43c73105f4e719d85cac17e5e6d13f2b1f0bd69d533aabdL324-R339
Running this now on web gives the following error:
When reverting lines 326-339 to the old ones everything runs fine. What is the reason this change was made in the first place? Is the old code broken with wasm?
The text was updated successfully, but these errors were encountered: