You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Re-enable flame.test in customer_testing once flame-engine/flame#4125 lands #194883
Because registry/flame.test checks out flame-engine/flame (which has no pubspec.lock and declares material_ui: any) and runs flutter packages get (update=.), every customer_testing run after material_ui 1.8.0 was published resolved 1.8.0 live from pub.dev and failed in game_widget_lifecycle_test.dart:
Expected: ['onGameResize', 'onLoad', 'onMount', 'update', 'render', 'update', 'render', 'update', 'onRemove', 'onDispose']
Actual: ['onGameResize', 'onLoad', 'onMount', 'update', 'render', 'update', 'update', 'onRemove', 'onDispose']
Which: at location [6] is 'update' instead of 'render'
In that test, tester.tap(find.text('Play')) pumps a second frame 16ms into the /game route transition; SnapshotWidget now reuses the raster snapshot captured on the first transition frame instead of calling GameRenderBox.paint a second time.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Temporarily disable flame.test for material_ui 1.8.0 (#508)
Bump customer_testing to temporarily disable flame.test (flutter#194886)
test: Update game_widget_lifecycle_test for material_ui 1.8.0 (#4125)
Re-enable flame.test with fix for material_ui 1.8.0 (#509)
Bump customer_testing to re-enable flame.test (flutter#194968)
Bump customer_testing to temporarily disable flame.test (flutter#194886)
Bump customer_testing to re-enable flame.test (flutter#194968)
Bump customer_testing to temporarily disable flame.test (flutter#194886)
Bump customer_testing to re-enable flame.test (flutter#194968)
github-actions commentedon Nov 4, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.