Skip to content
Discussion options

You must be logged in to vote

It's already out. 1.38.0 landed on pub.dev on 19 July, and your fix is in it. From the changelog:

FIX: HasWorldReference.onRemove() should call super.onRemove() (#3920)

So the workaround can go as soon as you upgrade.

If flutter pub upgrade isn't picking it up, a plain ^1.37.0 isn't the reason. That resolves to >=1.37.0 <2.0.0, so 1.38.0 is already allowed. The usual culprits are the lockfile or a companion package holding you back:

flutter pub deps | grep flame

If you use flame_tiled, flame_forge2d or similar, one of them may still cap flame below 1.38.0, and pub will silently keep you on the highest version that satisfies everyone. flutter pub upgrade flame will name the constraint tha…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Miiohau
Comment options

Answer selected by Miiohau
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants