Bug 37267 - System.NullReferenceException when creating a click event for a WKInterfaceButton
Summary: System.NullReferenceException when creating a click event for a WKInterfaceBu...
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-23 15:52 UTC by Adam Hartley [MSFT]
Modified: 2016-01-14 10:50 UTC (History)
7 users (show)

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


Attachments
Sample project and logs (2.72 MB, application/zip)
2015-12-23 15:52 UTC, Adam Hartley [MSFT]
Details


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 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:
Status:
RESOLVED FIXED

Description Adam Hartley [MSFT] 2015-12-23 15:52:00 UTC
Created attachment 14393 [details]
Sample project and logs

## Overview

A System.NullReferenceException occurs when creating a click event for a WKInterfaceButton in a WatchKit storyboard

## Information

Exception details, version info and log contents here:

https://gist.github.com/BytesGuy/ceaed7ae4da07865739e

## Notes

Was not able to reproduce this issue locally on latest stable.

Customer observed this happening on both latest stable and latest Alpha channels.
Comment 1 Alan McGovern 2016-01-14 10:50:47 UTC
With no way to repro and no line numbers it's not gonna be possible to be sure we've fixed this. However the code in question no longer exists the latest iteration of the code, so the issue is more than likely going to be fixed as part of c7. If this is important to fix in c6 just re-open and we'll look into it.