Open stuartmorgan opened 9 months ago
We should try to prioritize fixing this pretty highly, because we'll lose a lot of test coverage by disabling these.
A potential pattern: both tests using getScreenCoordinate are failing (and seemingly returning -1, -1), and getVisibleRegion presumably uses the same underlying info. (I don't have a connection for getZoomLevel though.)
In the app-facing package, testTakeSnapshot was already disabled for non-iOS because of lack of API key, interestingly.
This issue is assigned to @jmagman but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
This issue was assigned to @jmagman but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
We're seeing OOB persistent failures in a number of tests on iOS:
I can't reproduce them locally, so I don't have a good way to investigate right now. To re-open the tree, I'm going to disable these tests in
google_maps_flutter_ios
, as well as for iOS ingoogle_maps_flutter
(all with comments referencing this issue to make them findable).Since it's OOB and I can't repro locally, my current speculation is either:
The latter may be impacted by the fact that we aren't currently running with an API key in CI (although that can't explain it fully, because I don't have an API key set up locally). I do plan at some point to get the API key working in CI, but since it hasn't affected anything I haven't set up the plumbing, so I can't easily test whether the situation would be improved by having a key (e.g., if the problem is tripping a malicious usage detection, maybe a key would avoid that?)