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.
I'm running iOS 7.04. on iPhone 5.Here is the scenario. In my mapview, I have user tracking enabled and the blue dot representing user has a callout which on tapping takes the user to the next screen. If the user is stationary and then the callout is touched, it transitions to the next screen flawless. This transition is repeatable and without any issues. Now when the user starts to move and as a result user location changes in the mapView and then the callout is touched, it crashes with this exception:
Objective-C exception thrown. Name: NSInvalidArgumentException Reason: -[VKCacheNode BridgeSelector]: unrecognized selector sent to instance 0x17ae40b0
Google revealed that this VkCacheNode is from some iOS 6 private framework https://github.com/mattlawer/iOS6-Private-Frameworks/blob/43ca814f3954ac8e409fcbb694cb660c2d50f346/VectorKit/VKCacheNode.h
does anyone knows about this?
Created attachment 5630 [details]
Would it be possible to create a small, self-contained, test case to reproduce the crash and attach it to this bug report ?
I have not been able to repro the crash. One of the thing that I noted which prolly I was doing wrong was to use :using() when adding the rightcalloutAccessoryView for a MapView Annotation.
After eliminating that I have not been able to repro the issue. Atleast for the time being.
I will do some more research and if there is a consistent repro path, I will upload the demo app you requested.
Thanks for taking time to look in to the issue.
It is very much appreciated.
A `using` would dispose the managed instance at the end of it's scope. That would mean the native code could not callback into the managed instance after that block.
IOW your managed instances needs to be alive as long as they can be used (and the native/managed life cycle can be different in some cases, e.g. callbacks).
If you can reproduce the issue (with a test case) then please re-open this bug report and we'll have a look into it asap. Thanks