Create/Edit polygon - When google/OSM/USGS/Carto basemap is selected, points cannot be moved, only added or deleted, for both calculated default polygons and user created polygons. Only the Mapbox basemap allows moving of any existing vertices.
Select polygon from map - When google basemap is selected, the map widget is opened, a non transparent raster tileset is used, if the tileset is changed or a tileset is selected from initially being none after opening the map widget, the polygons are then drawn under the tileset and only appear briefly as the tile layer changes when zooming. If the tileset is not changed, the polygons are drawn over the tileset when the widget opens and can be seen at all times. Does not occur with other basemaps.
Polygon stroke width - When mapbox basemap is selected, the stroke width does not appear to be obeyed and is rendered as a hairline. Does not occur with other basemaps.
4. Upload any forms or screenshots you can share publicly below.
Update - The google basemap draw order doesn't affect geopoints, switching layers doesn't draw the new tileset over the top of the points.
Also - I cannot rotate the map for OSM / USGS / Carto, only google & mapbox allow two finger rotation. I was sure I had this happen previously but then couldn't repeat it. I have selected these layers multiple times and definitely cannot rotate the map.
It's not a zoom first then rotate attempt without lifting fingers - both google/mapbox allow rotate-zoom-rotate-zoom-etc without lifting, but if the first action is zoom you have to lift to be able to rotate.
I've repeated this on both a galaxy Tab S8+ and galaxy S23
Thanks for reporting these issues. It’s challenging to support three mapping engines and hopefully at some point we can figure out a reasonable way to reduce that.
In the mean time, we’ll file issues and triage these. Are there any that are particularly blocking? Probably the polygons being drawn under base maps?
This is me being selfish: The only one that affects me is stroke width for mapbox, because I don't use the other basemaps and mapbox isn't affected by the draw order / vertice adjustment / rotation issues.
I reported everything as I tested every basemap after identifying issues and figured that they would affect others.
Ack! In the beta just before, Mapbox drew the polygons under the selected offline layer as well. Changing layers didn't make them visible. Only switching to no layer would show them.
After testing all other map engines, and going back to Mapbox, (Google has the same issue as previously described. OSM/USGS/Carto are ok also) normal behaviour was restored and I couldn't disappear them again.
I realised I had added the tilesets and then couldn't see my polygons, so to repeat the behaviour I followed these steps;
I went to a different location, saw the polygons with no tileset in this area - ok
used the 'add offline layers' function - ok
selected the layer - ok
the polygons disappeared - not ok! (they're still selectable if you know where to tap)
changed the layer to 'none' - ok polygon appears
change the layer back - not ok! polygon disappears
exit map widget and reopen - ok! polygon appears.
Edit: I haven't tried these particular steps in non-beta, and haven't tried adding new tilesets in other engines in beta or non-beta
