-
Notifications
You must be signed in to change notification settings - Fork 709
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
flutter build web --wasm failed due to RangeError #596
Comments
I will check it and release this week. Thanks for raising this! |
yeah this change works and build passes! please note that in the example project I had to remove all dependencies that use |
I don't see any issue with the code that is failing to compile. Is this a bug in the WASM compiler? |
yes, it is the same issue as here rive-app/rive-flutter#391, because rive also depends on |
@demchenkoalex could you commit your changes that remove these dependencies so that I can take a look at the crash reported in the OP and debug? |
Let's track this issue on the Dart SDK issue tracker (see dart-lang/sdk#55817) |
hey @osa1 sorry for the late reply. pushed a branch called wasm-error. in the example folder you can run |
Thanks @demchenkoalex. This was fixed by dart-lang/sdk#55817. |
General
What bug do you experience? 🐞
I am using flutter_chat_ui in my app, and when I tried to run the
flutter build web --wasm
which was introduced recentlyto build my web app in web assembly, I saw the following errors:
What behavior is expected? 💡
flutter build web --wasm should be run successfully
Environment info
Please specify the flutter, flutter-chat-ui versions.
flutter: 3.22
flutter-chat-ui: 1.6.12
Platform
Device (e.g. Android emulator, iOS simulator, Samsung Galaxy S21): Chrome 124.0.6367.208
OS version (e.g. iOS 14.5, Android 11): Mac os 14.4.1
Additional context
I think the issue is src/widgets/typing_indicator.dart:244 use author[1] that does not compatible with the wasm requirement.
I modified the code to
that fixed the issue and
flutter build web --wasm
is successful after the change. If you are OK with this method (replace author[1] to author.last), I can create a pull request for it.The text was updated successfully, but these errors were encountered: