Since my workaround is working, I am no longer testing this issue but back when I was It did not seem to be consistent (I could not always consistently replicate the issue). Also, it was only an issue with Android (IOS worked perfectly with my app) so maybe you are seeing a different problem or variant.
Got it. I will continue to get to the bottom of it and post back here.
I’m seeing the setCenter issue as well. Was the case number is 23216 reported on May 2, 2013 ever fixed? It is almost a year old case and seems like it is still open unless my observation is a new problem. Any thoughts?
ksan, I do not think the case was ever resolved. The workaround I mentioned above was the only thing I found that worked for me. The problem with this approach is it creates a new map object every time you display the map which can eventually fill up memory so I had to make sure I removed each map before creating a new one…ugly, but it worked for me.
mobile36, thanks for confirming. I spent a whole day troubleshooting my code thinking I have a bug somewhere in there then thankfully I found your thread. The workaround isn’t a useable one for me as I have a very frequent map -> detail view from marker tap -> back to map cycle. The wait time on each map creation makes the app unusable so I hide and unhide the map. Thank you very much for the idea though. Most appreciated.
Its a pity that bug like this, nearly a year old, is still out there.
Just out of curiosity, do you see the wrong-centering always consistently? In my case the centering occurs correctly horizontally but vertically it is closer to the bottom of the screen than where it should be. I actually only see this issue on IOS. Just verified on Android and it seems to work as expected there. So maybe mine is a different variant of the same bug.
By the way, I just saw that bug # 23216 appears to be closed in the Bug Reporting system.
Since my workaround is working, I am no longer testing this issue but back when I was It did not seem to be consistent (I could not always consistently replicate the issue). Also, it was only an issue with Android (IOS worked perfectly with my app) so maybe you are seeing a different problem or variant.
Got it. I will continue to get to the bottom of it and post back here.