Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 22929 [details]
Local developer's build log
Encountering this both with Visual Studio for Mac and Azure Mobile Center Build for iOS when using Mono 5.0.1, but NOT when using Mono 4.8.1. Our system running VS/Mac uses Xamarin.iOS 10.10.0.36 but I'm not sure what particular version is used on Mobile Center.
Created attachment 22930 [details]
Mobile Center build log
Our local dev's VS Mac version information:
=== Visual Studio Community 2017 for Mac ===
Version 7.0.1 (build 24)
Installation UUID: d7b994ce-3578-4d37-a740-207e0b7a3a16
Mono 184.108.40.206 (2017-02/5077205) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 500010001
=== NuGet ===
=== .NET Core ===
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.0.1/lib/mono/msbuild/15.0/bin/Sdks
=== Xamarin.Profiler ===
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Xamarin.Android ===
Version: 220.127.116.11 (Visual Studio Community)
Android SDK: /Users/elsieyang/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
6.0 (API level 23)
SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.5
SDK Build Tools Version: 25.0.3
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)
Android Designer EPL code available here:
=== Apple Developer Tools ===
Xcode 8.3.2 (12175)
=== Xamarin.iOS ===
Version: 10.10.0.36 (Visual Studio Community)
Build date: 2017-05-22 16:30:53-0400
=== Xamarin.Mac ===
Version: 18.104.22.168 (Visual Studio Community)
=== Xamarin Inspector ===
Build date: Fri, 21 Apr 2017 17:57:12 GMT
=== Build Information ===
Release ID: 700010024
Git revision: 7ab1ca2ced6f584e56b7a0d4d321d00775cd95c9
Build date: 2017-05-19 05:44:51-04
Xamarin addins: 08d17158f3365beee5e60f67999e607cce4b3f93
Build lane: monodevelop-lion-d15-2
=== Operating System ===
Mac OS X 10.12.4
Darwin 16.5.0 Darwin Kernel Version 16.5.0
Fri Mar 3 16:52:33 PST 2017
Any chance you can provide a quick test case that isolates the issue or a way to reproduce it?
I could also make this entire bug private so it can only be accessed by Xamarin employees if you want to share more private code.
Sorry for taking a week to get back to this (temporarily had to do another project) but I can't isolate anything in particular that would cause this. set_Posted is just your average, run of the mill auto-property setter, though.
I am also having this issue. Will try to collect some details when I have a chance.
This looks like it's a bug in Xamarin.Forms: bug #56974, which is fixed in a prerelease version of Xamarin.Forms.
Can you try updating and see if that fixes the problem?
I'll give it a try but that's not a solution we can run with. Is there an ETA on 2.3.5?
Yeah, looks like 22.214.171.124-pre5 has the fix in. Too bad we can't use that for our app production/distribution builds, we need an official 2.3.5 release.
OK, marking as duplicate of bug #56974 then.
I'm reassigning to the Forms team so that they can give an answer about an ETA for 2.3.5.
*** This bug has been marked as a duplicate of bug 56974 ***
126.96.36.199-pre5 is undergoing our QA now. So long as we don't hit any major regressions there or from community pre-prerelease testers, expect we will make it stable this week.