Tim Sylvester

No, it would seem to be that the library is not present on the device, but I can't tell why. It could be related to #1558, make sure the architecture...

Unfortunately, my device has not updated to 14. It sounds like it might be an issue with the OpenGL context. You might try different renderer options under Settings / Renderer...

@Adraesh A little research seems to indicate that my device will never get Android 14, unfortunately, and I don't have any specific plans to replace it. If setting the simulator...

Interesting. I don't think "surface is not valid" is coming from WhirlyGlobe. From the comments above it sounds like forcing a repaint would not be enough, as interacting with the...

> Could you add tests? Done. I also expanded some existing test cases, as modifications to some areas with low coverage brought the average way down.

Updating the metric expectation has resolved the build issue, as long as we're okay with the metrics being dependent on implementation-defined behavior.

The coverage results seem to include a ton of partial hits that don't make much sense. It seems to consider anywhere that a destructor calls delete (which is safe to...

Looks like this is "just" the inefficiency of not sharing vertex data. Tile `16/19831/24240` in `label-places` generates 168 segments, and each one gets a drawable for icon and halo, which...

No apparent effect on benchmark performance: main: ``` Average frame encoding time: 2.55 ms Average frame rendering time: 6.22 ms Average frame encoding time: 2.52 ms Average frame rendering time:...

ok, I think this one is finally ready