Thank you for the report. 

Is the map loading at all? 
We are aware of a problem in the latest update that causes tiles not to render. We are already working on a fix.

For me, the MapView object is loading Map correctly.But the problem is black screen flickers before the map gets loaded.

The issue seems to be resolved with new version 6.7.76.

6.7.76? I see https://developer.android.com/google/play-services/index.html 6.5 as last version.

I, too, would like to know how to get this magical 6.7.76 version of the play-services libraries.

I am not sure. Google might be distributing updated version to selected customers for testing purposes.

Renjith, to clarify: is 6.7.76 the play-services version you're referring to in your build.gradle file?  Or the version of the Play Services app installed on your phone? 

Play services version installed on my phone

	Untitled.png 302 KB   View   Download

So for 6.7.76 installed on my phone this error also reproduces.

I had problem with version 6.7.74. And that issue is resolved by this updated version.

Thanks for the updates, everyone. This issue should now be fixed in 6.7.76.
(It was in fact unrelated to the other problem in 6.7.74.)

Again same problem in in services 7.3.29 MapView look like bad, how I understood MapView use SurfaceView for render (and in this case we can't add two fragments with map).

1. Please say what will google play services use in future for render MapView?

2. Is present possibility to come back to previous MapView's rendering mechanism (TextureView)? 

Thanks.

Yes again same issue occurred. any update when it'll fix?  

Not fixed in 7.3.29, any reliable workarounds exists?

The issue is appearing again in 7.3.29

Issue also appears on 7.5.74. Any workarounds available? Thanks.

My solution: use only one map for all application, because if you use few maps you depend on google play service and now i don't worry about play service) 

I propose you do the same.

The issue still exists in 8.4.0. Sigh...

The issue still exists in 2.9.1 
I am trying to replace the child fragment inside the parent fragment.
Where in which I am seeing a Black screen flash for a second and loads the child fragment.

Thanks for the further reports that this issue still exists. We are unable to reproduce this issue, so in order to look into this again we'll need a sample that illustrates this issue. The ideal place for hosting a repro sample is GitHub. Please see http://sscce.org/ for details about what the aim of the reproduction sample is.

If someone who can reproduce the issue is able to provide a sample we'll take a look.