tree c557423e9cf403a3be97888b28dbf9be56905079
parent d3bbef885e57cd0a018e968a186e2b805f7dcfa4
author Ari Weiland <aweiland@google.com> 1603941172 -0700
committer GitHub <noreply@github.com> 1603941172 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfmjM0CRBK7hj4Ov3rIwAAdHIIAIY+2CEoYsxa6J8usfLjE7bz
 PWaWOePadLdIlIkr3vvODGda1Bny8L0A83zzPagL5p60T+e6zXrv34RpF5zC0qAm
 61O6QCNAJpW3pr73CUvvf7XJJ5LNE1n64THjT3BJwI/q9sJdFajs8+NmtFZIXx+X
 KvSn4iELQ5KtmH3Ts/DJxJnteCvnmHlPWLk8Dnrjh4YOrGQSjolQ36+181y9CZC6
 qnS4xWW6jzsoChaznlj+232yiw4mApNkCkgykc08F5I9+nbSZs+01YaaHwX+r/fr
 iIfCyOfJe/zoR9lr5MQpvsJjOPJrr8pUX9wIYIQkJMg8CPrsFHdSdy5Ts3D1Agk=
 =C5KT
 -----END PGP SIGNATURE-----
 

[google_maps_flutter] Overhaul lifecycle management in GoogleMapsPlugin (#3213)

GoogleMapController is now uniformly driven by implementing DefaultLifecycleObserver. That observer is registered to a lifecycle passed via the new LifecycleProvider interface, which has 3 implementations:
1. For v2 plugin registration, GoogleMapsPlugin implements the interface and holds the lifecycle in a field, which is itself controlled by ActivityAware methods.
2. For v1 plugin registration, if the activity implements LifecycleOwner, it's lifecycle is used directly.
3. For v1 plugin registration, if the activity does not implement LifecycleOwner, a proxy lifecycle is created via ActivityLifecycleCallbacks.