tree 6c07329ce24a3259353c7dbf3c04dbd0c5ae862f
parent c3dc31f665f3ccaa96898a6f719591c8642c32de
author stuartmorgan <stuartmorgan@google.com> 1616693243 -0700
committer GitHub <noreply@github.com> 1616693243 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgXMf7CRBK7hj4Ov3rIwAAdHIIAFm/bSXafviGaFd/51YSWL5c
 wM4CLk+crs2+qLnVzKLRdRxNaYHGL5GfiMzF0pJy26qzQB9xeAIid5RpM1kMN25t
 BVrJnzbkwsLJHvn6sTLofm6iT5gWs9nRXh8VYPgwG/4E7N18wopgXDGYPKoCSdsb
 3QHwXqqPvBNMAhhXxXIJR91YI+7A37k8UVwIFM3benOcHvcPY+SyjvysRxGLLY67
 JjlOspbijMBrfvBT9GA6mn3igEBcmjzkUhupwtWhff98R0R1oH4RGVzmjDsIgJ0Z
 OkA5VD8G7bwaJrP7tgTVIlqkjvv2jDKsHzJHMd8DPzl6n7BRGjBhPnAh+YmWKO8=
 =sqDQ
 -----END PGP SIGNATURE-----
 

[google_maps_flutter] Fix handling of non-nullable invokeMethod return types (#3754)

During the null-safety migration I accepted the auto-migrator use of as Future<T> to handle invokeMethod<T> returning a T?. I didn't realize that as does not actually do that kind of casting, and will fail with "type 'Future<T?>' is not a subtype of type 'Future<T>' in type cast".

There were no tests that exercised these methods in any way, so automated tests didn't catch the bug. This adds a minimal test that calls all of the non-void methods to ensure that they don't explode (and a TODO to backfill full unit tests of the entire method channel).

Fixes flutter/flutter#78426
Fixes flutter/flutter#78856