Bug 25579 - "Activity" is spelled incorrectly as "Activitiy" in MonoTouch.UIKit.UIApplicationDelegate.DidFailToContinueUserActivitiy() Method
Summary: "Activity" is spelled incorrectly as "Activitiy" in MonoTouch.UIKit.UIApplica...
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 8.4.0
Hardware: Macintosh Mac OS
: Low enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-12-22 14:12 UTC by Kent Green [MSFT]
Modified: 2014-12-22 15:31 UTC (History)
2 users (show)

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


Attachments
Logs from my repo of the issue (47.65 KB, application/zip)
2014-12-22 14:12 UTC, Kent Green [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 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:
RESOLVED NOT_ON_ROADMAP

Description Kent Green [MSFT] 2014-12-22 14:12:37 UTC
Created attachment 9168 [details]
Logs from my repo of the issue

---Overview---
From this desk case:
https://xamarin.desk.com/agent/case/113570

Customer reported that "Activity" is spelled incorrectly as "Activitiy" in the MonoTouch.UIKit.UIApplicationDelegate.DidFailToContinueUserActivitiy() Method. I used the Xamarin Studio Assembly Browser to confirm this. Here's my screenshot of the typoed method: http://screencast.com/t/ncOXObAj0gKK.

Similarly, the typo is present in the API documentation:
http://iosapi.xamarin.com/index.aspx?link=M%3AMonoTouch.UIKit.UIApplicationDelegate.DidFailToContinueUserActivitiy%28MonoTouch.UIKit.UIApplication%2CSystem.String%2CMonoTouch.Foundation.NSError%29

---Build Information---
=== Xamarin Studio ===

Version 5.5.4 (build 15)
Installation UUID: 8ef63a7c-1b18-40de-a334-7f78777fcb55
Runtime:
	Mono 3.10.0 ((detached/92c4884)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000031

=== Xamarin.Android ===

Version: 4.20.0.28 (Business Edition)
Android SDK: /Users/kentgreen/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

=== Apple Developer Tools ===

Xcode 6.1.1 (6611)
Build 6A2008a

=== Xamarin.Mac ===

Version: 1.10.0.18 (Business Edition)

=== Xamarin.iOS ===

Version: 8.4.0.47 (Business Edition)
Hash: 7244769
Branch: 
Build date: 2014-12-11 14:54:30-0500

=== Build Information ===

Release ID: 505040015
Git revision: f93940a35458a18052f1a25e106e62ca970d9c40
Build date: 2014-11-19 15:32:41-05
Xamarin addins: dc23cbd91a3a0e1d326328e1229e86c942a49ec8

=== Operating System ===

Mac OS X 10.10.1
Darwin Kents-MacBook-Pro-2.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64

---Additional Info---
Attaching Xamarin Studio Logs.
Comment 1 Sebastien Pouliot 2014-12-22 15:31:22 UTC
Thanks for the report.

Sadly we cannot fix this at this time (and it's too late for the unified API) as it's a breaking change - i.e. any compiled assemblies, like components, that use this symbol would break if it was renamed.

note: The initial documentation is generated from source, so it has the same type in it's name.

I annotated our source code [1] with this information and, if/when possible, this will be fixed.

[1] master 89242f6e8eec4ec5a8b5f9ce86086009c7520383