Bug 25423 - Xamarin.Forms.Maps Pins flicker in Android
Summary: Xamarin.Forms.Maps Pins flicker in Android
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-12-16 08:05 UTC by Anubhav Ranjan
Modified: 2015-01-09 13:43 UTC (History)
8 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Anubhav Ranjan 2014-12-16 08:05:03 UTC
One of our customer is facing issue with Xamarin.Forms.Maps in Android.
Even though the bug https://bugzilla.xamarin.com/show_bug.cgi?id=25055 fixes the issue of Maps getting reset, 
the pins still keeps on flickering.

The issue is reproducible in the sample given here
Comment 3 Christopher Svanefalk 2014-12-21 09:09:24 UTC
I have the same problem. Maps are basically useless because of it.

Xamarin Studio
Version 5.5.4 (build 15)
Installation UUID: fb249e80-2b94-4e1a-bb82-1f0a76379e63
	Mono 3.10.0 ((detached/92c4884)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000031

Apple Developer Tools
Xcode 6.1.1 (6611)
Build 6A2008a


Version: (Business Edition)
Hash: 7244769
Build date: 2014-12-11 14:54:30-0500

Version: (Business Edition)
Android SDK: /Users/csvanefalk/Library/Developer/android-sdk-osx
	Supported Android versions:
		1.6    (API level 4)
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.0    (API level 11)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

Build Information
Release ID: 505040015
Git revision: f93940a35458a18052f1a25e106e62ca970d9c40
Build date: 2014-11-19 15:32:41-05
Xamarin addins: dc23cbd91a3a0e1d326328e1229e86c942a49ec8

Operating System
Mac OS X 10.10.1
Darwin Christophers-MacBook-Pro.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 4 Christopher Svanefalk 2014-12-25 20:02:30 UTC
This is still reproducible as of Forms 1.3 stable.
Comment 5 Jason Smith [MSFT] 2014-12-26 02:21:51 UTC
Fixed in next pre-release
Comment 6 Vladislav Kosev 2015-01-03 03:16:20 UTC
As of this is still not fixed. The problem is clearly with the implementation of Xamarin.Forms.Maps.Android.MapRenderer.OnCollectionChanged(object sender, NotifyCollectionChangedEventArgs notifyCollectionChangedEventArgs) which forces recreation of all markers on every change so when you create 50 markers this 50 removals of all markers and 50 additions of all added markers so far.
Comment 7 Brendan Zagaeski (Xamarin Team, assistant) 2015-01-08 15:41:12 UTC
Just to be diligent about record-keeping, I'll note that was released on December 24, before the fix was applied. If any users see the problem after the next prerelease, be sure to let us know. Thanks!
Comment 8 Vladislav Kosev 2015-01-08 15:44:37 UTC
I apologize, I somehow thought you posted it on December 22nd, not 26th. Makes perfect sense now.
Comment 9 Brendan Zagaeski (Xamarin Team, assistant) 2015-01-09 13:43:38 UTC
@Vladislav, no worries. Better safe than sorry :)