Bug 15515 - Typo in DidFinishReceivingResource method.
Summary: Typo in DidFinishReceivingResource method.
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 7.0.2.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-10-19 14:01 UTC by Bob Reck
Modified: 2014-04-01 10:29 UTC (History)
3 users (show)

Is this bug a regression?: ---
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:

Description Bob Reck 2013-10-19 14:01:17 UTC

When you add the DidFinishReceivingResource method to a custom MCSessionDelegate, the pre-populated template contains a typo.

public override void DidFinishReceivingResource (MCSession session, string resourceName, MCPeerID formPeer, NSUrl localUrl, out NSError error)

Specifically, the "MCPeerID formPeer" should be "fromPeer" not "formPeer."

Just wanted to let you know.
Comment 1 Sebastien Pouliot 2013-10-21 11:31:43 UTC
Fixed in master 991903bd4ee30e9ba99a70f3e302e387b132f48e
Comment 2 Udham Singh 2014-04-01 10:29:24 UTC
I have checked this issue on following builds:

Mac OS X 10.9.2
Xamarin Studio : 4.2.4 (build 266)
Xamarin.iOS : (Enterprise Edition)

Screencast: http://screencast.com/t/BDdi7vy12

This issue is working fine. Hence, I am closing this issue.