-
Notifications
You must be signed in to change notification settings - Fork 476
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
[1.5.4]'Uint16List' can't be assigned to the parameter type 'Int32List'. #126
Comments
same issue, and very annoying. using channel stable + flare_flutter: ^1.5.4 (as indicated in https://github.com/2d-inc/Flare-Flutter/#flutter-channel) doesn't work. I tried to change the type but it didn't work, any idea?? |
Also getting this, does anyone know the flare version that works?
|
It's a combination of the latest flutter stable (1.7.8+hotfix.3) and Flare 1.5.4. Both of those versions must be satisfied for the latest version of Flare and Flutter to work together (we strongly recommend you use these version). It looks like you are using the old stable (v1.5.4-hotfix.2) which has a breaking change with Flutter 1.7.8+hotfix.3. Flare. Please upgrade to the latest Flutter stable. |
Yea was just about to comment that updating flutter seemed to work (run "flutter upgrade") and then use the stable flare tag still. But if that isn't an option 1.5.0 also worked (although I wouldn't recommend hard versioning ever). Thanks for the reply @luigi-rosso |
1.5.0 would work with the older Flutter stable 1.5.4-hotfix.2. The cause of all of this is that Flutter changed the signature of a method Flare uses. This was a good change but it broke compatibility. If you use a version of Flutter with the old signature, you'll need to use a version of Flare that's <=1.5.3. If you're using the latest stable >=1.7.8+hotfix.3 then any flare_flutter >=1.5.4 will work. In your case, |
Well, shouldn't the latest version of Flutter ( |
That's awesome, I didn't realize that was configurable. Thanks for the suggestion! |
close it |
The text was updated successfully, but these errors were encountered: