[ci] Manual roll Flutter to c246ecd (84 revisions) + fixes

[ditman]

Updates the flutter master version and adds fixes for broken stuff.

• [flutter_markdown] Updates a test image used as a golden file.
• [google_maps_flutter_android] Flaky test/fixed OOB.

Issues

• Completes Manual roll Flutter from c85fa6abf4ff to 4cad9fde6791 (83 revisions) #6861

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or this PR is exempt from CHANGELOG changes.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[ditman]

(Brought from #6861)

OK, the android crash seems to be different/more explicit this time:

     FATAL EXCEPTION: GL-Map
Process: io.flutter.plugins.googlemapsexample, PID: 19653
java.lang.IllegalStateException: Trying to call onSurfaceCreated with no current context
	at m.fvx.l(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:10)
	at m.ezu.run(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:816)

This has taken me to the following public buganizer:

• https://b.corp.google.com/issues/339141097

Maybe we can mitigate by doing this:

• https://developers.google.com/maps/documentation/android-sdk/renderer#opt-out ?

(/cc @reidbaker)

[reidbaker]

(Brought from #6861)

OK, the android crash seems to be different/more explicit this time:

     FATAL EXCEPTION: GL-Map
Process: io.flutter.plugins.googlemapsexample, PID: 19653
java.lang.IllegalStateException: Trying to call onSurfaceCreated with no current context
	at m.fvx.l(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:10)
	at m.ezu.run(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:816)

This has taken me to the following public buganizer:

• https://b.corp.google.com/issues/339141097

Maybe we can mitigate by doing this:

• https://developers.google.com/maps/documentation/android-sdk/renderer#opt-out ?

(/cc @reidbaker)

You resolved this. Did you find a solution?

[ditman]

You resolved this. Did you find a solution?

This resolved itself by bumping one more revision of Flutter, but the incoming changes don't seem related, so it's maybe an OOB fix from Google Maps or FTL (?) (or we got lucky in the flakiness lottery)

[auto-submit]

auto label is removed for flutter/packages/6863, due to - The status or check suite Linux_android android_platform_tests_shard_6 master has failed. Please fix the issues identified (or deflake) before re-applying this label.

[ditman]

Will restart the roller now that this has landed!

[ditman]

The new roll is now showing the "Trying to call onSurfaceCreated with no current context" error... Ugh!