Imagery Issues with ArcGIS Pro 3.6

[PeteJordan]

I have been seeing odd imagery issues since updating to 3.6.  I have several imagery services and one no longer even displays.  Another one is completely fine and the one I use the most keeps cutting off the top part of the map frame and not displaying the imagery.  When I pan around, it will update the map imagery, but still doesn't diplay any imagery for that couple of inches from the top.

  We tried this on a computer that didn't upgrade to 3.6 just now, and that computer displays everything perfectly.

  So the only difference is my computer having been updated to 3.6...

[PeteJordan]

Yes anything helped and that's the kind of thing ESRI support asked me to try as well.  And yes editing yesterday I found the projection I had when I did previous tests, the default maps I made were in WGS and not State Plane, when I realized I couldn't use some editing features I found I was in the wrong projection and switching back the issue came back.  

  Got on here and found that GrantHerbert posted 30mins before me discovering the same thing.  So forwared that to the ESRI team that has been in contact with me over this.

  I just feel in the mean time, it's either deal with it and have multiple projections to switch back and forth depending on what needs to be done or deal with just having that missing portion at the top until it a fix comes out in another update version...

[GrantHerbert]

I have been investigating this for a client, and can reproduce the issue myself on 3.6 but not on 3.5.4. It does not occur when the Pro map is set to the same coordinate system as the WMS imagery (in our case WGS84) but can be replicated by switching the map coordinate system back to a local projected one (e.g. NAD 1983 HARN). Did not seem to matter which transformation was used. 
It did not occur when I set the map to NAD 1983 UTM 10N, but did when I used NAD 1983 HARN UTM 10N, but pretty much all the NAD 1983 coordinate systems otherwise would show the same behavior (HARN or otherwise).

[PeteJordan]

  This is what I just discovered and came on to report as well.  It tured out the Projected NAD 1983 (2011) State Plane I use has the issue, but WGS 1984 doesn't.  I also tried other state ones for the Projected ones and fould all the Colorado ones to have the issue, but other states as a test were fine.

  I have emailed the tech support team on this bug that I had submitted with the latest update on it with the projections...