[go: nahoru, domu]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests timing out waiting for onMapLoaded #237

Open
DSteve595 opened this issue Dec 8, 2022 · 1 comment
Open

Tests timing out waiting for onMapLoaded #237

DSteve595 opened this issue Dec 8, 2022 · 1 comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@DSteve595
Copy link
Contributor

Opening this for notes/discussion on a failure that affects CI and I can sometimes repro locally.

com.google.maps.android.compose.GoogleMapViewTests > testLatLngNotInVisibleRegion[test(AVD) - 10] FAILED 
	java.lang.AssertionError: Map loaded

onMapLoaded is never called. The map is interactive, and tiles don't seem to be loading properly; zooming renders them at ugly resolutions even though internet is available.
I noticed that changing the camera settings seems to reproducibly affect whether or not onMapLoaded is called.
On a Pixel 5 API 33 emulator:

private val startingZoom = 10f
private val startingPosition = LatLng(1.35, 103.87)

fails.

private val startingZoom = 11f
private val startingPosition = LatLng(1.35, 103.87)

succeeds.

After repro'ing this a few times, my emulator became permanently "fixed", and startingZoom = 10f started to succeed. Something is weirdly stateful here.

@DSteve595 DSteve595 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. triage me I really want to be triaged. priority: p2 Moderately-important priority. Fix may not be included in next release. and removed triage me I really want to be triaged. labels Dec 8, 2022
@DSteve595
Copy link
Contributor Author

Aside from this issue, the Maps API key simply isn't being injected properly in tests. That should be a simple fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

1 participant