Bug 44592 - Getting build error on building MessageReceiver Project under XM NSPortExample sample in Xcode8.
Summary: Getting build error on building MessageReceiver Project under XM NSPortExampl...
Status: VERIFIED FIXED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Samples ()
Version: Master
Hardware: PC Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Ivan Herrera
URL:
Depends on:
Blocks:
 
Reported: 2016-09-21 19:00 UTC by Rajneesh Kumar
Modified: 2016-10-20 11:26 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: No
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:
Status:
VERIFIED FIXED

Comment 1 Chris Hamons 2016-09-21 19:03:39 UTC
I think the obj-c part of the sample is busted.
Comment 2 Oleg Demchenko 2016-09-21 19:07:23 UTC
@Ivan please take a look.
Comment 3 Oleg Demchenko 2016-10-19 15:31:08 UTC
Fix is merged to master.
Comment 4 Rajneesh Kumar 2016-10-20 11:26:39 UTC
I have checked this issue with Xcode 8 and observed that this issue has been fixed, Now I am successfully able to build and run MessageReceiver Project successfully.

Screencast: http://www.screencast.com/t/1t1oaX3qoNc

This issue has been fixed, hence I am closing this issue.

Thanks..!