Bug 51250 - MKMapPoint.FromCoordinate crashes watchOS app on Apple Watch running watchOS 2 or 3
Summary: MKMapPoint.FromCoordinate crashes watchOS app on Apple Watch running watchOS ...
Status: RESOLVED DUPLICATE of bug 50208
Alias: None
Product: iOS
Classification: Xamarin
Component: Mono runtime / AOT compiler ()
Version: XI 10.3 (iOS 10.2)
Hardware: PC Mac OS
: --- normal
Target Milestone: (C9)
Assignee: Zoltan Varga
Depends on:
Reported: 2017-01-05 19:52 UTC by Jon Goldberger [MSFT]
Modified: 2017-01-10 09:51 UTC (History)
5 users (show)

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

Test Project (36.10 KB, application/zip)
2017-01-05 19:52 UTC, Jon Goldberger [MSFT]

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 Jon Goldberger [MSFT] 2017-01-05 19:52:06 UTC
Created attachment 19101 [details]
Test Project

## Description

Calling MKMapPoint.FromCoordinate(coordinate) where coordinate is a CLLocationCoordinate2D causes a watchOS app to crash with an AOT error:

> Attempting to JIT compile method '(wrapper managed-to-native) MapKit.MKMapPoint:FromCoordinate CoreLocation.CLLocationCoordinate2D)' while running with —aot-only

## Steps to reproduce

1. Open the attached test project and deploy the WatchMeCrash.WatchApp to a physical Apple watch running watchOS 2 or 3

Expected result: A Map will display on the Watch

Actual result: Watch app crashes with the above error.

## Environment

=== Xamarin Studio Business ===

Version 6.1.3 (build 19)
Installation UUID: fe5b13dc-a70d-419e-9bef-37d9a9a209bc
Mono 4.6.2 (mono-4.6.0-branch/ac9e222) (64-bit)
GTK+ 2.24.23 (Raleigh theme)

Package version: 406020016

=== NuGet ===


=== Xamarin.Profiler ===

Version: 0.30.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Xamarin.Android ===

Version: (Xamarin Business)
Android SDK: /Users/moconnor/Library/Developer/Xamarin/android-sdk-mac_x86
Supported Android versions:
2.3 (API level 10)
4.0.3 (API level 15)
4.4 (API level 19)
5.0 (API level 21)

SDK Tools Version: 24.0.1
SDK Platform Tools Version: 21
SDK Build Tools Version: 20

Java SDK: /usr
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

Android Designer EPL code available here:

=== Xamarin Android Player ===

Not Installed

=== Apple Developer Tools ===

Xcode 8.2.1 (11766.1)
Build 8C1002

=== Xamarin.Mac ===

Not Installed

=== Xamarin.iOS ===

Version: (Xamarin Business)
Hash: 8b53676
Branch: cycle8-xi
Build date: 2016-12-18 12:23:27-0500

=== Build Information ===

Release ID: 601030019
Git revision: 7fabf9293c2d7b638e28a07f798d21799da1f886
Build date: 2016-12-21 07:08:35-05
Xamarin addins: efbae0e683a0060d2230e91e70c1598abc054845
Build lane: monodevelop-lion-cycle8

=== Operating System ===

Mac OS X 10.12.2
Darwin Matthews-MacBook-Pro.local 16.3.0 Darwin Kernel Version 16.3.0
Thu Nov 17 20:23:58 PST 2016
root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64
Comment 2 Zoltan Varga 2017-01-09 23:50:48 UTC
This should be fixed by mono master d8743c7a966ad7ef316cfa3de1ffe15c92b208ba. Should I backport it somewhere ? It should only affect watchos.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2017-01-10 09:40:39 UTC
@Zoltan, can you backport to the 4.8 branch?
Comment 4 Zoltan Varga 2017-01-10 09:50:19 UTC
Looks like its already there as ad245375146800f0bd1f16e674fc83ac041ed4dc. This bug is probably a dup, can't find the original one.
Comment 5 Rolf Bjarne Kvinge [MSFT] 2017-01-10 09:51:49 UTC

*** This bug has been marked as a duplicate of bug 50208 ***