Flutter build with 3.22 for iOS failing: The method 'scheduleWarmUpFrame' isn't defined for the class 'PlatformDispatcher'. about flutter HOT 16 CLOSED

I think we lack actionable context on this issue. its possible there is some kind of cache invalidation issue or similar.

from flutter.

Thanks for the report @geokala

The method 'scheduleWarmUpFrame' isn't defined for the class 'PlatformDispatcher'.

It seems the method is part of the class and is present per https://github.com/flutter/engine/blob/9bc449ee2e8bfbd97ab1d56c98837e39cda0289a/lib/ui/platform_dispatcher.dart#L833

Build target is iOS 11,

Per documentation, supported ios versions starts from 12 : https://docs.flutter.dev/reference/supported-platforms
Can you try to change it to 12 and run your scenario again to check if you still get same error or not ?

from flutter.

I've forced the minimum version to be 12 and am not seeing the warning about iOS version any more.

However, the scheduleWarmUpFrame error is still occurring. Do you have any recommendations for troubleshooting further?

From looking at the logs, I also see that analytics were sent- I'm not sure if that's something you have access to (or what is actually sent and thus whether it can be helpful).

from flutter.

Thanks for the update. The method scheduleWarmUpFrame was added as part of flutter/engine#50570 which also made it to 3.22.0, so I am not sure why it could be resulting in the error.
I'll keep the issue open for team's input / attention.

/cc @dkwingsmt

from flutter.

Sounds good. I've temporarily pinned our iOS build to 3.19.6 but if there's any more investigation I can do, let me know and I'll fit it in as soon as I can.

from flutter.

This should has nothing to do with scheduleWarmUpFrame, but is caused by an outdated dart:ui library. Can you show me the command you used to switch to 3.22? Anyway, can you try flutter upgrade?

from flutter.

The commands used to ensure the flutter dir was up to date were:
rm -rf /tmp/flutter-ios
git clone https://github.com/flutter/flutter.git -b stable /tmp/flutter-ios
/tmp/flutter-ios/bin/flutter channel stable

I'll try them with a flutter upgrade tacked onto the end in case that helps and let you know.

Edit: Sorry, missed a command as it's commented while the force-to-3.19.6 is in:
/tmp/flutter-ios/bin/flutter upgrade --force

So it looks like we were running upgrade.

from flutter.

after upgrading to 3.22.0 I've deleted build folder and that fixed it for me

from flutter.

I believe that the system this is happening on has a clean build directory every time but I will double check that.

Also, I believe the system in question might be running on x86_64 rather than the newer m1 (arm? I don't recall). Might that have an impact?

I can't access the system right at this moment but as noted, I'll check the build dir tomorrow and look to confirm whether it's x86_64.

from flutter.

If this is consistently broken it might be an issue with the downloaded SDK or a tooling bug.

from flutter.

Just stumbled upon the same issue... following on the thread below it appears my VS Code is running dart instead of flutter.

https://stackoverflow.com/questions/52483773/dartui1-error-not-found-dartui-flutter-dart

Running flutter run main.dart instead of using debugger from VSCode seems to have done the trick. Should be something that's "confusing" the IDE to run the app using the dart command.

from flutter.

OK, I've had another look, adding the following commands before the build command:
rm -rf build
flutter clean
flutter pub cache clean
flutter pub get
flutter -v build ipa --no-codesign --release --flavor Release
That results in xcode faffing around for a while and then a different error: ../../../.pub-cache/hosted/pub.dev/win32-5.5.1/lib/win32.dart:1:1: Error: The specified language version is too high. The highest supported language version is 3.3.
Given that pub.dev tells me that 5.5.1 targets 3.4, and all the other systems we have using this are working fine, something seems screwy here.

vscode isn't involved in this instance, as it's running as part of a build pipeline.

I can confirm that it's running on x86_64 architecture, though I don't know if that's had any impact on this.

Either way, there doesn't seem to be much we can productively do with this at the moment so I'm leaving it pinned to 3.19.6 and will come back to it next time flutter updates and see if the next updates make it happier. Given that there don't seem to be a lot of other sightings of this problem, I'm happy for this ticket to be closed if nobody has any epiphanies.

from flutter.

I am on arm.. oddly after that "trick" started working again from VSCode so there must be some cache of some sorts. I had no need to pin an iOS build.

from flutter.

Oh, I should also note (regarding jonahwilliams' comment that the system this was on downloads flutter to a temp location on each build, so it /could/ be a download/SDK issue, but I'd expect that to result in more variety in the errors, where we've had fairly stable error states on these.

from flutter.

Just for reference I stumbled upon this again after leaving debugging connected over night (and closing laptop) and having spent some time doing code generation. No clue the actual cause of this coming back but a flutter clean etc. sorted it.

Just dropping it here for reference ... don't have much more to pin point the issue.

from flutter.

Also encountered this problem, flutter run main.dart helped with the solution scheduleWarmUpFrame, but MediaQuery.boldTextOverride remained

from flutter.