nonsensical geoplot.m warnings?

I use geoplot.m with benign options:

loc = [49.7500   32.5000  -70.0000  -97.0000];
gx      = geoaxes;
geolimits(gx, sort([loc(1),loc(2)]), sort([loc(3),loc(4)]) );

I sometimes receiver errors; sometimes I do not; this seems like an unstable bug of geoplot.m. When I do receive such errors, they have this form:

Warning: A value of class "double" was indexed with no subscripts specified. Currently
the result of this operation is the indexed value itself, but in a future release, it
will be an error. 
> In matlab.internal.asynchttpsave/AsyncHTTPContentFileWriter/handleThreadIsFinishedEvent
In matlab.internal.asynchttpsave.AsyncHTTPContentFileWriter
In asyncio/Channel/onPropertyChanged (line 471)
In asyncio.Channel>@(source,data)obj.onPropertyChanged(data.Name,data.Value) (line 401) 

I should add that my employer will buy me a new version (2021b), but this warning still fills up my screen and leads to reduced performance.

However, using the zoom features on the plot, or manipulating the figure in general also generates such errors. Is there a command I can issue that will "fix" this?

Answer 1

[Walter Roberson]

See https://www.mathworks.com/matlabcentral/answers/457222-warning-about-a-value-indexed-with-no-subscripts-and-error-in-future-release

It is probably eliminated in a later release.

[Joshua Carmichael]

I will find out before January. Thank you for the answer, and the link.