xamarin
/
xamarin-macios
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
xamarin-macios/docs/website/mtouch-errors.md

3091 строка
114 KiB
Markdown
Исходник Обычный вид История

[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
---
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
title: "Xamarin.iOS errors"
ms.topic: troubleshooting
ms.prod: xamarin
ms.assetid: 9F76162B-D622-45DA-996B-2FBF8017E208
ms.technology: xamarin-ios
author: bradumbaugh
ms.author: brumbaug
ms.date: 03/06/2018
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
---
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
# Xamarin.iOS errors
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT0xxx: mtouch error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
E.g. parameters, environment, missing tools.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
<!--
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
MT0xxx mtouch itself, e.g. parameters, environment (e.g. missing tools)
https://github.com/xamarin/xamarin-macios/blob/master/tools/mtouch/error.cs
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0000" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com
An unexpected error condition occurred. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with as much information as possible, including:
[docs][mtouch] Add more details for handling MT0000 and fix typo for MT0091 (wrong number shown) (#633)
2016-08-19 16:25:31 +03:00
* Full build logs, with maximum verbosity (e.g. `-v -v -v -v` in the **Additional mtouch arguments**);
* A minimal test case that reproduce the error; and
* All version informations
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
The easiest way to get exact version information is to use the **Visual Studio for Mac** menu, **About Visual Studio for Mac** item, **Show Details** button and copy/paste the version informations (you can use the **Copy Information** button).
<a name="MT0001" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0001: '-devname' was provided without any device-specific action
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This is a warning that is emitted if -devname is passed to mtouch when no device-specific action (-logdev/-installdev/-killdev/-launchdev/-listapps) was requested.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0002" />
### MT0002: Could not parse the environment variable *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This error happens if you try to set an invalid environment key=value variable pair. The correct format is: `mtouch --setenv=VARIABLE=VALUE`
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0003" />
### MT0003: Application name '*.exe' conflicts with an SDK or product assembly (.dll) name.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The executable assembly's name and the application's name can't match the name of any dll in the app. Please modify the name of your executable.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0004" />
### MT0004: New refcounting logic requires SGen to be enabled too.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
If you enable the refcounting extension you must also enable the SGen garbage collector in the project's iOS Build options (Advanced tab).
Starting with Xamarin.iOS 7.2.1 this requirement has been lifted, the new refcounting logic can be enabled with both Boehm and SGen Garbage Collectors.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0005" />
### MT0005: The output directory * does not exist.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Please create the directory.
[mtouch] Automatically create the output directory if it doesn't exist. (#1414)
2016-12-24 18:57:08 +03:00
This error is not generated anymore, mtouch will automatically create the directory if it doesn't exist.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0006" />
### MT0006: There is no devel platform at *, use --platform=PLAT to specify the SDK.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Xamarin.iOS cannot find the SDK directory at the location mentioned in the error message. Please verify that the path is correct.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0007" />
### MT0007: The root assembly * does not exist.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Xamarin.iOS cannot find the assembly at the location mentioned in the error message. Please verify that the path is correct.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0008" />
### MT0008: You should provide one root assembly only, found # assemblies: *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
More than one root assembly was passed to mtouch, while there can be only one root assembly.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0009" />
### MT0009: Error while loading assemblies: *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[mtouch][mmp] Report invalid debug symbols files. Fixes #3200 (#3203) * [mtouch][mmp] Report invalid debug symbols files. Fixes #3200 Try to read the assembly with symbols and, if that fails, warn and fallback to loading them without symbols. This fixes cases were it's not easy to update or delete (e.g. nuget) bad symbols files - so this cannot be an error without causing a lot of pain. However it needs to be reported, otherwise it wont be fixed (by the publisher) and it can limit the debugability of the application and the usefulness of the stacktraces. Finally merge most of the resolver's code between mtouch and mmp so we don't have to fix such issue twice anymore. note: this needs to be slightly updated once we get a version of cecil that can give us a more precise error message. Also bring Rolf's tests from https://github.com/xamarin/xamarin-macios/pull/3079 reference: https://github.com/xamarin/xamarin-macios/issues/3200
2018-01-13 01:39:38 +03:00
An error occurred while loading the assemblies from the root assembly references. More information may be provided in the build output.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0010" />
### MT0010: Could not parse the command line arguments: *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred while parsing the command line arguments. Please verify that they are all correct.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0011" />
### MT0011: * was built against a more recent runtime (*) than MonoTouch supports.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This warning is typically reported because the project has a reference to a class library that was not built using the Xamarin.iOS BCL.
The same way an app using the .NET 4.0 SDK may not work on a system only supporting .NET 2.0, a library built using .NET 4.0 may not work on Xamarin.iOS, it may use API not present on Xamarin.iOS.
The general solution is to build the library as a Xamarin.iOS Class Library. This can be accomplished by creating a new Xamarin.iOS Class Library project and add all the source files to it. If you do not have the source code for the library, you should contact the vendor and request that they provide a Xamarin.iOS-compatible version of their library.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0012" />
### MT0012: Incomplete data is provided to complete *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This error is not reported anymore in the current version of Xamarin.iOS.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0013" />
### MT0013: Profiling support requires sgen to be enabled too.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
SGen (--sgen) must be enabled if profiling (--profiling) is enabled.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0014" />
### MT0014: The iOS * SDK does not support building applications targeting *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This can happen in the following circumstances:
* ARMv6 is enabled and Xcode 4.5 or later is installed.
* ARMv7s is enabled and Xcode 4.4 or earlier is installed.
Please verify that the installed version of Xcode supports the selected architectures.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0015" />
### MT0015: Invalid ABI: *. Supported ABIs are: i386, x86_64, armv7, armv7+llvm, armv7+llvm+thumb2, armv7s, armv7s+llvm, armv7s+llvm+thumb2, arm64 and arm64+llvm.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An invalid ABI was passed to mtouch. Please specify a valid ABI.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0016" />
### MT0016: The option * has been deprecated.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The mentioned mtouch option has been deprecated and will be ignored.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0017" />
### MT0017: You should provide a root assembly.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
It is required to specify a root assembly (typically the main executable) when building an app.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0018" />
### MT0018: Unknown command line argument: *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Mtouch does not recognize the command line argument mentioned in the error message.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0019" />
### MT0019: Only one --[log|install|kill|launch]dev or --[launch|debug]sim option can be used.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
There are several options for mtouch that can't be used simultaneously:
- --logdev
- --installdev
- --killdev
- --launchdev
- --launchdebug
- --launchsim
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0020" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0020: The valid options for '\*' are '\*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0021" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0021: Cannot compile using gcc/g++ (--use-gcc) when using the static registrar (this is the default when compiling for device). Either remove the --use-gcc flag or use the dynamic registrar (--registrar:dynamic).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0022" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0022: The options '--unsupported--enable-generics-in-registrar' and '--registrar' are not compatible.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Remove both the options `--unsupported--enable-generics-in-registrar` and `--registrar`. Starting with Xamarin.iOS 7.2.1 the default registrar supports generics.
[mtouch] Remove deprecated Classic commmand-line arguments. (#1319) * [mtouch] Remove deprecated Classic commmand-line arguments. * [mtouch docs] Document MT0022's death.
2016-12-08 20:59:04 +03:00
This error is no longer shown (the command-line argument `--unsupported--enable-generics-in-registrar` has been removed from mtouch).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0023" />
### MT0023: Application name '*.exe' conflicts with another user assembly.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The executable assembly's name and the application's name can't match the name of any dll in the app. Please modify the name of your executable.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0024" />
### MT0024: Could not find required file '*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0025" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0025: No SDK version was provided. Please add `--sdk=X.Y` to specify which iOS SDK should be used to build your application.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0026" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0026: Could not parse the command line argument '*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0027" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0027: The options '\*' and '\*' are not compatible.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0028" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0028: Cannot enable PIE (-pie) when targeting iOS 4.1 or earlier. Please disable PIE (-pie:false) or set the deployment target to at least iOS 4.2
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0029" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0029: REPL (--enable-repl) is only supported in the simulator (--sim).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
REPL is only supported if you're building for the simulator. This means that if you pass `--enable-repl` to mtouch, you must also pass `--sim`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0030" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0030: The executable name (\*) and the app name (\*) are different, this may prevent crash logs from getting symbolicated properly.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
When Xcode symbolicates (translates memory addresses to function names and file/line numbers) the process may fail if the executable and app have different names (without the extension).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
To fix this either change 'Application Name' in the project's Build/iOS Application options, or change 'Assembly Name' in the project's Build/Output options.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0031" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0031: The command line arguments '--enable-background-fetch' and '--launch-for-background-fetch' require '--launchsim' too.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0032" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0032: The option '--debugtrack' is ignored unless '--debug' is also specified.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0033" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0033: A Xamarin.iOS project must reference either monotouch.dll or Xamarin.iOS.dll
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0034" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0034: Cannot include both 'monotouch.dll' and 'Xamarin.iOS.dll' in the same Xamarin.iOS project - '\*' is referenced explicitly, while '\*' is referenced by '*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!-- MT0035 unused -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0036" />
### MT0036: Cannot launch a * simulator for a * app. Please enable the correct architecture(s) in your project's iOS Build options (Advanced page).
<a name="MT0037" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0037: monotouch.dll is not 64-bit compatible. Either reference Xamarin.iOS.dll, or do not build for a 64-bit architecture (ARM64 and/or x86_64).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0038" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0038: The old registrars (--registrar:oldstatic|olddynamic) are not supported when referencing Xamarin.iOS.dll.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0039" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0039: Applications targeting ARMv6 cannot reference Xamarin.iOS.dll.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0040" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0040: Could not find the assembly '\*', referenced by '\*'.
<a name="MT0041" />
### MT0041: Cannot reference both 'monotouch.dll' and 'Xamarin.iOS.dll'.
<a name="MT0042" />
### MT0042: No reference to either monotouch.dll or Xamarin.iOS.dll was found. A reference to monotouch.dll will be added.
<a name="MT0043" />
### MT0043: The Boehm garbage collector is currently not supported when referencing 'Xamarin.iOS.dll'. The SGen garbage collector has been selected instead.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Only the SGen garbage collector is supported with Unified projects. Ensure there are no additional mtouch flags specifying Boehm as the garbage collector.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0044" />
### MT0044: --listsim is only supported with Xcode 6.0 or later.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Install a newer Xcode version.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0045" />
### MT0045: --extension is only supported when using the iOS 8.0 (or later) SDK.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!-- MT0046 is not reported anymore -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0047" />
### MT0047: The minimum deployment target for Unified applications is 5.1.1, the current deployment target is '*'. Please select a newer deployment target in your project's iOS Application options.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!-- MT0048 is not reported anymore -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0049" />
### MT0049: *.framework is supported only if deployment target is 8.0 or later. * features might not work correctly.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The specified framework is not supported in the iOS version the deployment target refers to. Either update the deployment target to a newer iOS version, or remove usage of the specified framework from the app.
<!-- MT0050 is not reported anymore -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0051" />
### MT0051: Xamarin.iOS * requires Xcode 5.0 or later. The current Xcode version (found in *) is *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Install a newer Xcode.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0052" />
### MT0052: No command specified.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
No action was specified for mtouch.
<!-- 0053 is used by mmp -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0054" />
### MT0054: Unable to canonicalize the path '*': *
This is an internal error. If you see this error, please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0055" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0055: The Xcode path '*' does not exist.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The Xcode path passed using `--sdkroot` does not exist. Please specify a valid path.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0056" />
### MT0056: Cannot find Xcode in the default location (/Applications/Xcode.app). Please install Xcode, or pass a custom path using --sdkroot <path>.
<a name="MT0057" />
### MT0057: Cannot determine the path to Xcode.app from the sdk root '*'. Please specify the full path to the Xcode.app bundle.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The path passed using `--sdkroot` does not specify a valid Xcode app. Please specify a path to an Xcode app.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0058" />
### MT0058: The Xcode.app '\*' is invalid (the file '\*' does not exist).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The path passed using `--sdkroot` does not specify a valid Xcode app. Please specify a path to an Xcode app.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0059" />
### MT0059: Could not find the currently selected Xcode on the system: *
<a name="MT0060" />
### MT0060: Could not find the currently selected Xcode on the system. 'xcode-select --print-path' returned '*', but that directory does not exist.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0061" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0061: No Xcode.app specified (using --sdkroot), using the system Xcode as reported by 'xcode-select --print-path': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This is a informational warning, explaining which Xcode will be used, since none was specified.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0062" />
### MT0062: No Xcode.app specified (using --sdkroot or 'xcode-select --print-path'), using the default Xcode instead: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This is a informational warning, explaining which Xcode will be used, since none was specified.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0063" />
### MT0063: Cannot find the executable in the extension * (no CFBundleExecutable entry in its Info.plist)
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Every Info.plist must have an executable (using the CFBundleExecutable entry), however an entry should be generated automatically during the build.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0064" />
### MT0064: Xamarin.iOS only supports embedded frameworks with Unified projects.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Xamarin.iOS only supports embedded frameworks when using the Unified API; please update your project to use the Unified API.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0065" />
### MT0065: Xamarin.iOS only supports embedded frameworks when deployment target is at least 8.0 (current deployment target: * embedded frameworks: *)
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Xamarin.iOS only supports embedded frameworks when the deployment target is at least 8.0 (because earlier versions of iOS does not support embedded frameworks).
Please update the deployment target in the project's Info.plist to 8.0 or higher.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0066" />
### MT0066: Invalid build registrar assembly: *
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
<a name="MT0067" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0067: Invalid registrar: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0068" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0068: Invalid value for target framework: *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An invalid target framework was passed using the --target-framework argument. Please specify a valid target framework.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0069" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<!--### MT0069: currently unused -->
<a name="MT0070" />
### MT0070: Invalid target framework: *. Valid target frameworks are: *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An invalid target framework was passed using the --target-framework argument. Please specify a valid target framework.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0071" />
### MT0071: Unknown platform: *. This usually indicates a bug in Xamarin.iOS; please file a bug report at http://bugzilla.xamarin.com with a test case.
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0072" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0072: Extensions are not supported for the platform '*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0073" />
### MT0073: Xamarin.iOS * does not support a deployment target of * (the minimum is *). Please select a newer deployment target in your project's Info.plist.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The minimum deployment target is the one specified in the error message; please select a newer deployment target in the project's Info.plist.
If updating the deployment target is not possible, then please use an older version of Xamarin.iOS.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0074" />
### MT0074: Xamarin.iOS * does not support a minimum deployment target of * (the maximum is *). Please select an older deployment target in your project's Info.plist or upgrade to a newer version of Xamarin.iOS.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Xamarin.iOS does not support setting the minimum deployment target to a higher version than the version this particular version of Xamarin.iOS was built for.
Please select an older minimum deployment target in the project's Info.plist, or upgrade to a newer version of Xamarin.iOS.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0075" />
### MT0075: Invalid architecture '*' for * projects. Valid architectures are: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An invalid architecture was specified. Please verify that architecture is valid.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0076" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0076: No architecture specified (using the --abi argument). An architecture is required for * projects.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0077" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0077: WatchOS projects must be extensions.
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
<a name="MT0078" />
### MT0078: Incremental builds are enabled with a deployment target < 8.0 (currently *). This is not supported (the resulting application will not launch on iOS 9), so the deployment target will be set to 8.0.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[mtouch] Require deployment target to be 8+ for incremental builds. (#805) This is something that changed with 70f1346b: our libxamarin.dylib now requires iOS 8+, which means the app itself must require iOS 8+ when using libxamarin.dylib. This fixes an msbuild failure (Xamarin.iOS.Tasks.IBToolLinking("iPhone").BuildTest): Process exited with code 1, command: /Applications/Xcode73.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -framework Foundation -framework UIKit /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/SDKs/MonoTouch.iphoneos.sdk/usr/lib/libmonosgen-2.0.dylib /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/SDKs/MonoTouch.iphoneos.sdk/usr/lib/libxamarin-debug.dylib -lz -isysroot /Applications/Xcode73.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.3.sdk -Qunused-arguments -miphoneos-version-min=7.0 -arch armv7 -shared -read_only_relocs suppress -install_name @executable_path/libXamarin.iOS.dll.dylib -fapplication-extension -o /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/msbuild/tests/MyIBToolLinkTest/obj/iPhone/Debug/mtouch-cache/Xamarin.iOS.dll.armv7.dylib -x assembler /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/msbuild/tests/MyIBToolLinkTest/obj/iPhone/Debug/mtouch-cache/Xamarin.iOS.dll.armv7.s -DDEBUG ld: warning: embedded dylibs/frameworks only run on iOS 8 or later ld: embedded dylibs/frameworks are only supported on iOS 8.0 and later (@executable_path/libxamarin-debug.dylib) for architecture armv7 clang: error: linker command failed with exit code 1 (use -v to see invocation)
2016-09-08 16:01:48 +03:00
This is a warning informing that the deployment target has been set to 8.0 for this build so that incremental builds work properly.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[mtouch] Require deployment target to be 8+ for incremental builds. (#805) This is something that changed with 70f1346b: our libxamarin.dylib now requires iOS 8+, which means the app itself must require iOS 8+ when using libxamarin.dylib. This fixes an msbuild failure (Xamarin.iOS.Tasks.IBToolLinking("iPhone").BuildTest): Process exited with code 1, command: /Applications/Xcode73.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -framework Foundation -framework UIKit /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/SDKs/MonoTouch.iphoneos.sdk/usr/lib/libmonosgen-2.0.dylib /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/SDKs/MonoTouch.iphoneos.sdk/usr/lib/libxamarin-debug.dylib -lz -isysroot /Applications/Xcode73.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.3.sdk -Qunused-arguments -miphoneos-version-min=7.0 -arch armv7 -shared -read_only_relocs suppress -install_name @executable_path/libXamarin.iOS.dll.dylib -fapplication-extension -o /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/msbuild/tests/MyIBToolLinkTest/obj/iPhone/Debug/mtouch-cache/Xamarin.iOS.dll.armv7.dylib -x assembler /Users/builder/data/lanes/1381/5f73edaa/source/xamarin-macios/msbuild/tests/MyIBToolLinkTest/obj/iPhone/Debug/mtouch-cache/Xamarin.iOS.dll.armv7.s -DDEBUG ld: warning: embedded dylibs/frameworks only run on iOS 8 or later ld: embedded dylibs/frameworks are only supported on iOS 8.0 and later (@executable_path/libxamarin-debug.dylib) for architecture armv7 clang: error: linker command failed with exit code 1 (use -v to see invocation)
2016-09-08 16:01:48 +03:00
Incremental builds are only supported when the deployment target is at least 8.0 (because the resulting application will not launch on iOS 9 otherwise).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0079" />
### MT0079: The recommended Xcode version for Xamarin.iOS * is Xcode * or later. The current Xcode version (found in *) is *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This is a warning informing that the current version of Xcode is not the recommended version of Xcode for this version of Xamarin.iOS.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Please upgrade Xcode to ensure optimal behavior.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0080" />
### MT0080: Disabling NewRefCount, --new-refcount:false, is deprecated.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This is a warning informing that the request to disable the new refcount (--new-refcount:false) has been ignored.
The new refcount feature is now mandatory for all projects, and it's thus not possible to disable anymore.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0081" />
### MT0081: The command line argument --download-crash-report also requires --download-crash-report-to.
<a name="MT0082" />
### MT0082: REPL (--enable-repl) is only supported when linking is not used (--nolink).
<a name="MT0083" />
### MT0083: Asm-only bitcode is not supported on watchOS. Use either --bitcode:marker or --bitcode:full.
<a name="MT0084" />
### MT0084: Bitcode is not supported in the simulator. Do not pass --bitcode when building for the simulator.
<a name="MT0085" />
### MT0085: No reference to '*' was found. It will be added automatically.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0086" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0086: A target framework (--target-framework) must be specified when building for TVOS or WatchOS.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0087" />
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0087: Incremental builds (--fastdev) is not supported with the Boehm GC. Incremental builds will be disabled.
<a name="MT0088" />
### MT0088: The GC must be in cooperative mode for watchOS apps. Please remove the --coop:false argument to mtouch.
<a name="MT0089" />
### MT0089: The option '\*' cannot take the value '\*' when cooperative mode is enabled for the GC.
<a name="MT0091" />
### MT0091: This version of Xamarin.iOS requires the * SDK (shipped with Xcode *). Either upgrade Xcode to get the required header files or set the managed linker behaviour to Link Framework SDKs Only (to try to avoid the new APIs).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[mtouch] Provide a more accurate description of the MT0091 error (#1938) The old one makes it sounds the linker is doing magic ;-)
2017-03-30 15:36:20 +03:00
Xamarin.iOS requires the header files, from the SDK version specified in the error message, to build your application. The recommended way to fix this error is to upgrade Xcode to get the required SDK, this will include all the required header files. If you have multiple versions of Xcode installed, or want to use an Xcode in a non-default location, make sure to set the correct Xcode location in your IDE's preferences.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[mtouch] Provide a more accurate description of the MT0091 error (#1938) The old one makes it sounds the linker is doing magic ;-)
2017-03-30 15:36:20 +03:00
A potential, alternative solution is to enable the managed linker. This will remove unused API including, in most cases, the new API where the header files are missing (or incomplete). However this will not work if your project uses API that was introduced in a newer SDK than the one your Xcode provides.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[mtouch] Provide a more accurate description of the MT0091 error (#1938) The old one makes it sounds the linker is doing magic ;-)
2017-03-30 15:36:20 +03:00
A last-straw solution would be to use an older version of Xamarin.iOS, one that supports the SDK your project requires.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!-- MT0092 used by mlaunch -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0093" />
### MT0093: Could not find 'mlaunch'.
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!-- MT0094 is not reported anymore -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0095" />
Remove XI/Classic support (#926) * [tests] Remove Classic SDK tests. * Remove XI/Classic support. This also means we can remove support for the legacy registrars. * [monotouch-test] Remove legacy registrar tests. * [tests/mtouch] Remove Classic tests (and legacy registrar logic). * [tests/scripted] Fix tests to reference Xamarin.iOS.dll.
2016-09-30 22:02:17 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0095: Aot files could not be copied to the destination directory {dest}: {error}
<a name="MT0096" />
### MT0096: No reference to Xamarin.iOS.dll was found.
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
[docs] Improve MT0099 error help text a little bit.
2017-01-25 10:26:13 +03:00
<!-- MT0097: used by mmp -->
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!-- MT0098: used by mmp -->
[docs] Improve MT0099 error help text a little bit.
2017-01-25 10:26:13 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0099" />
### MT0099: Internal error *. Please file a bug report with a test case (http://bugzilla.xamarin.com).
[docs] Improve MT0099 error help text a little bit.
2017-01-25 10:26:13 +03:00
This error message is reported when an internal consistency check in Xamarin.iOS fails.
[mtouch] Refactor command-line parsing to be reusable. Also add a few tests to verify how we treat the root assembly (or lack thereof).
2017-01-03 21:45:16 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
<a name="MT0100" />
[mtouch] Refactor command-line parsing to be reusable. Also add a few tests to verify how we treat the root assembly (or lack thereof).
2017-01-03 21:45:16 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0100: Invalid assembly build target: '*'. Please file a bug report with a test case (http://bugzilla.xamarin.com).
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
This error message is reported when an internal consistency check in Xamarin.iOS fails.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0101" />
### MT0101: The assembly '*' is specified multiple times in --assembly-build-target arguments.
[mtouch] Add an --assembly-build-target option.
2017-01-24 19:55:28 +03:00
The assembly mentioned in the error message is specified multiple times in --assembly-build-target arguments. Please make sure each assembly is only mentioned once.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0102" />
### MT0102: The assemblies '\*' and '\*' have the same target name ('\*'), but different targets ('\*' and '*').
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
The assemblies mentioned in the error message have conflicting build targets.
For example:
--assembly-build-target:Assembly1.dll=framework=MyBinary --assembly-build-target:Assembly2.dll=dynamiclibrary=MyBinary
This example is trying to create both a dynamic library and a framework with the same make (`MyBinary`).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0103" />
### MT0103: The static object '\*' contains more than one assembly ('\*'), but each static object must correspond with exactly one assembly.
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
The assemblies mentioned in the error message are all compiled to a single static object. This is not allowed, every assembly must be compiled to a different static object.
For example:
--assembly-build-target:Assembly1.dll=staticobject=MyBinary --assembly-build-target:Assembly2.dll=staticobject=MyBinary
This example tries to build a static object (`MyBinary`) comprised of two assemblies (`Assembly1.dll` and `Assembly2.dll`), which is not allowed.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0105" />
### MT0105: No assembly build target was specified for '*'.
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
When specifying the assembly build target using `--assembly-build-target`, every assembly in the app must have a build target assigned.
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
This error is reported when the assembly mentioned in the error message does not have an assembly build target assigned.
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
See the documentation about `--assembly-build-target` for further information.
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0106" />
### MT0106: The assembly build target name '\*' is invalid: the character '\*' is not allowed.
[mtouch] Add an --assembly-build-target option.
2017-01-24 19:55:28 +03:00
The assembly build target name must be a valid filename.
For example these values will trigger this error:
--assembly-build-target:Assembly1.dll=staticobject=my/path.o
because `my/path.o` is not a valid filename due to the directory separator character.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0107" />
### MT0107: The assemblies '\*' have different custom LLVM optimizations (\*), which is not allowed when they are all compiled to a single binary.
<a name="MT0108" />
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0108: The assembly build target '*' did not match any assemblies.
[mtouch] Validate the assembly build targets.
2017-01-24 20:11:20 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0109" />
### MT0109: The assembly '{0}' was loaded from a different path than the provided path (provided path: {1}, actual path: {2}).
[mtouch] Warn if mtouch loads an assembly from a different location than requested. Warn if mtouch loads an assembly from a different location than requested (which might be because there are multiple assemblies with the same name). Also rework the MT0023 check a bit by explicitly loading the root assembly first, and then detecting if any loaded assemblies matches the root assembly. This results in code that's a bit more obvious, and it also works correctly with extensions (previously the entire MT0023 check was skipped for extensions).
2017-01-25 12:47:51 +03:00
This is a warning indicating that an assembly referenced by the application was loaded from a different location than requested.
This might mean that the app is referencing multiple assemblies with the same name, but from different locations, which might lead to unexpected results (only the first assembly will be used).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0110" />
### MT0110: Incremental builds have been disabled because this version of Xamarin.iOS does not support incremental builds in projects that include third-party binding libraries and that compiles to bitcode.
[mtouch] Automatically disable incremental builds if building to bitcode and any third-party bindings were found. Works around bug #51710. (#1592) Most projects building to bitcode (any kind of bitcode, this includes the marker-only version as well), will fail to link when linking with third-party libraries and incremental builds are enabled. So automatically disable incremental builds when we detect this scenario. This is only a workaround until we can make this scenario build correctly. https://bugzilla.xamarin.com/show_bug.cgi?id=51710
2017-01-31 16:55:54 +03:00
Incremental builds have been disabled because this version of Xamarin.iOS does not support incremental builds in projects that include third-party binding libraries and that compiles to bitcode (tvOS and watchOS projects).
No action is required on your part, this message is purely informational.
For further information see bug #[51710](https://bugzilla.xamarin.com/show_bug.cgi?id=51710).
[mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. (#2162) * [mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. * Refactor required symbol collection to store more information about each symbol (field, function, Objective-C class), and in general make the code more straight forward. * Implement support for generating source code that references these symbols, and do this whenever we can't ask the native linker to keep these symbols (when using bitcode). Additionally make it possible to do this manually, so that the source code can be generated for non-bitcode platforms too (which is useful if the number of symbols is enormous, in which case we might surpass the maximum command-line length). * Also make it possible to completely ignore native symbols, or ignore them on a per-symbol basis. This provides a fallback for users if we get something right and we try to preserve something that shouldn't be preserved (for instance if it doesn't exist), and the user ends up with unfixable linker errors. * Don't collect Objective-C classes unless they're in an assembly with LinkWith attributes. We don't need to preserve Objective-C classes in any other circumstances. * Implement everything for both Xamarin.iOS and Xamarin.Mac, and share the code between them. * Remove previous workaround for bug #51710, since it's no longer needed. * Add tests. https://bugzilla.xamarin.com/show_bug.cgi?id=54417 https://bugzilla.xamarin.com/show_bug.cgi?id=51710 * [mtouch] Make sure to only keep symbols from the current app when code sharing. This fixes a build problem with the interdependent-binding-projects test when testing in Today Extension mode.
2017-06-02 19:29:19 +03:00
This warning is not reported anymore.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0111" />
### MT0111: Bitcode has been enabled because this version of Xamarin.iOS does not support building watchOS projects using LLVM without enabling bitcode.
[mtouch] Automatically enable bitcode if LLVM is enabled. Fixes #52241. (#1620) Currently we can't build watchOS projects if LLVM is enabled, but bitcode is not (see bug #51634). Additionally the IDEs do not have UI to select if bitcode is enabled or not, so automatically enable it if LLVM is enabled (since most likely people will be building for the App Store if LLVM is enabled). https://bugzilla.xamarin.com/show_bug.cgi?id=51634 https://bugzilla.xamarin.com/show_bug.cgi?id=52241
2017-02-03 09:16:17 +03:00
Bitcode has been enabled automatically because this version of Xamarin.iOS does not support building watchOS projects using LLVM without enabling bitcode.
No action is required on your part, this message is purely informational.
For further information see bug #[51634](https://bugzilla.xamarin.com/show_bug.cgi?id=51634).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0112" />
### MT0112: Native code sharing has been disabled because *
[mtouch] Use fewer error numbers for code sharing failures.
2017-02-28 15:25:21 +03:00
There are multiple reasons code sharing can be disabled:
* because the container app's deployment target is earlier than iOS 8.0 (it's *)).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
Native code sharing requires iOS 8.0 because native code sharing is implemented using user frameworks, which was introduced with iOS 8.0.
[mtouch] Use fewer error numbers for code sharing failures.
2017-02-28 15:25:21 +03:00
* because the container app includes I18N assemblies (*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
Native code sharing is currently not supported if the container app includes I18N assemblies.
[mtouch] Use fewer error numbers for code sharing failures.
2017-02-28 15:25:21 +03:00
* because the container app has custom xml definitions for the managed linker (*).
Native code sharing requires is not supported for projects that use custom xml definitions for the managed linker.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0113" />
[mtouch] Use fewer error numbers for code sharing failures.
2017-02-28 15:25:21 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0113: Native code sharing has been disabled for the extension '*' because *.
[mtouch] Use fewer error numbers for code sharing failures.
2017-02-28 15:25:21 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the bitcode options differ between the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that the bitcode options match between the projects that share code.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the --assembly-build-target options are different between the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that the --assembly-build-target options are identical between the projects that share code.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
This condition can occur if incremental builds are not either enabled or disabled in all the projects.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the I18N assemblies are different between the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing is currently not supported for extensions that include I18N assemblies.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the arguments to the AOT compiler are different between the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that the arguments to the AOT compiler do not differ between projects that share code.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the other arguments to the AOT compiler are different between the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that the arguments to the AOT compiler do not differ between projects that share code.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
This condition occurs if the 'Perform all 32-bit float operations as 64-bit float' differs between projects.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because LLVM is not enabled or disabled in both the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that LLVM is either enabled or disabled for all projects that share code.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the managed linker settings are different between the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that the managed linker settings are identical for all projects that share code.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the skipped assemblies for the managed linker are different between the container app (\*) and the extension (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that the managed linker settings are identical for all projects that share code.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[mtouch] Use fewer error numbers for code sharing failures.
2017-02-28 15:25:21 +03:00
* because the extension has custom xml definitions for the managed linker (*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires is not supported for projects that use custom xml definitions for the managed linker.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[mtouch] Use fewer error numbers for code sharing failures.
2017-02-28 15:25:21 +03:00
* because the container app does not build for the ABI * (while the extension is building for this ABI).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that the container app builds for all the architectures any app extension builds for.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
For instance: this condition occurs when an extension builds for ARM64+ARMv7, but the container app only builds for ARM64.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the container app is building for the ABI \*, which is not compatible with the extension's ABI (\*).
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that all the projects build for the exact same API.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
For instance: this condition occurs when an extension builds for ARMv7+llvm+thumb2, but the container app only builds for ARMv7+llvm.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* because the container app is referencing the assembly '\*' from '\*', while the extension references a different version from '*'.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Native code sharing requires that all the projects that share code use the same versions for all assemblies.
[mtouch] Make code sharing failures real warnings.
2017-02-14 13:13:38 +03:00
Fixup Xamarin.Mac Hybrid AOT and improve testing (#1995) - Actually enable hybrid AOT by adding argument in right location - Hybrid AOT and stripping does not play well currently with partial AOT - Fix AOT makefile to work with nuget nunit - https://bugzilla.xamarin.com/show_bug.cgi?id=55041
2017-05-16 21:29:08 +03:00
<!-- MT0114: used by mmp -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0115" />
### MT0115: It is recommended to reference dynamic symbols using code (--dynamic-symbol-mode=code) when bitcode is enabled.
[mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. (#2162) * [mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. * Refactor required symbol collection to store more information about each symbol (field, function, Objective-C class), and in general make the code more straight forward. * Implement support for generating source code that references these symbols, and do this whenever we can't ask the native linker to keep these symbols (when using bitcode). Additionally make it possible to do this manually, so that the source code can be generated for non-bitcode platforms too (which is useful if the number of symbols is enormous, in which case we might surpass the maximum command-line length). * Also make it possible to completely ignore native symbols, or ignore them on a per-symbol basis. This provides a fallback for users if we get something right and we try to preserve something that shouldn't be preserved (for instance if it doesn't exist), and the user ends up with unfixable linker errors. * Don't collect Objective-C classes unless they're in an assembly with LinkWith attributes. We don't need to preserve Objective-C classes in any other circumstances. * Implement everything for both Xamarin.iOS and Xamarin.Mac, and share the code between them. * Remove previous workaround for bug #51710, since it's no longer needed. * Add tests. https://bugzilla.xamarin.com/show_bug.cgi?id=54417 https://bugzilla.xamarin.com/show_bug.cgi?id=51710 * [mtouch] Make sure to only keep symbols from the current app when code sharing. This fixes a build problem with the interdependent-binding-projects test when testing in Today Extension mode.
2017-06-02 19:29:19 +03:00
Xamarin.iOS projects will often reference native symbols dynamically, which
means that the native linker might remove such native symbols during the
native linking process, because the native linker does not see that these
symbols are used.
Usually Xamarin.iOS will ask the native linker to keep such symbols (using the
`-u symbol` linker flag), but when compiling for bitcode the native linker
does not accept the `-u` flag.
Xamarin.iOS has implemented an alternative solution: we generate extra native
code which references these symbols, and thus the native linker will see that
these symbols are used. This is automatically done when compiling to bitcode.
If `--dynamic-symbol-mode=linker` is passed to mtouch, this alternative
solution will be disabled, and Xamarin.iOS will try to pass `-u` to the native
linker. This will most likely result in native linker errors.
The solution is to remove the `--dynamic-symbol-mode=linker` argument from the additional mtouch arguments in the project's Build options.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<!-- 0116 - 0124: free to use -->
<a name="MT0116" />
### MT0116: Invalid architecture: {arch}. 32-bit architectures are not supported when deployment target is 11 or later. Make sure the project does not build for a 32-bit architecture.
[mtouch] Do state why we did not copy the aot (msym) files. (#2594)
2017-09-07 20:14:53 +03:00
[mtouch] Don't allow building for 32-bit when deployment target is >= 11. Fixes #57966. (#2303) * [mtouch] Don't allow building for 32-bit when deployment target is >= 11. Fixes #57966. Also bump maccore to get an mlaunch error for launching a 32-bit app in a 64-bit-only simulator. https://bugzilla.xamarin.com/show_bug.cgi?id=57966 * [tests][msbuild] Make sure all Info.plists have deployment targets. Otherwise we get different behavior (32-bit allowed or not) depending on which Xcode is used to build. * [mtouch] Default to 64-bit arch if not specified and targeting iOS 11+. * [tests] Tweak tests to either specify a deployment target < 11 or not build a 32-bit arch.
2017-07-11 09:54:50 +03:00
iOS 11 does not contain support for 32-bit applications, so it's not supported
to build for a 32-bit application when the deployment target is iOS 11 or
later.
Either change the target architecture in the project's iOS build options to
arm64, or change the deployment target in the project's Info.plist to an
earlier iOS version.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0117" />
Merge branch 'xcode9' into xcode9-master-merge
2017-09-15 18:05:30 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0117: Can't launch a 32-bit app on a simulator that only supports 64-bit.
<a name="MT0118" />
### MT0118: Aot files could not be found at the expected directory '{msymdir}'.
Merge branch 'xcode9' into xcode9-master-merge
2017-09-15 18:05:30 +03:00
[mtouch/mmp] Downgrade MT0123 to a verbose log statement instead. (#2701) * [mtouch/mmp] Downgrade MT0123 to a verbose log statement instead. It's unlikely to be useful for normal people who've just set LANG for whatever unrelated reason. If it's needed to diagnose failures, it'll still show up in verbose logs. * [docs] Remove MT0123, it's no longer being used, and we never released a version that used it either. * [tests][mtouch] Update tests according to code changes (MT0123 removal).
2017-09-18 18:14:17 +03:00
<!-- 0119 - 0123: free to use -->
[mtouch] Print verbosity using an invariant culture. Fixes #58849. (#2507) * [mtouch/mmp] Set CultureInfo.CurrentCulture according to LANG. This makes it easier to run mtouch/mmp under different locales when testing. Unfortunately mono checks the system locale before checking LANG, which means that there's no built-in way in macOS/mono to specify the current locale without changing the system locale. * [mtouch] Print verbosity using an invariant culture. Fixes #58849. https://bugzilla.xamarin.com/show_bug.cgi?id=58849 * [mtouch/mmp] Fix error code. * [mtouch/mmp] Log/warn when we set the current language.
2017-08-22 10:40:26 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0123" />
### MT0123: The executable assembly * does not reference *.
[mtouch] Show MT0123 if the executable assembly does not reference the product assembly. Fixes #59798. (#2801) It does not make sense to create Xamarin.iOS projects that don't reference Xamarin.iOS.dll, so make this an explicit error. This fixes a NullReferenceException which could (when building for device, or when not using simlauncher) occur, and instead shows the MT0123 error. > MTOUCH : error MT0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com > System.NullReferenceException: Object reference not set to an instance of an object > at Xamarin.Bundler.Target.GatherFrameworks () [0x00065] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/common/Target.cs:122 > at Xamarin.Bundler.Target.ProcessAssemblies () [0x000c2] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/mtouch/Target.cs:802 > at Xamarin.Bundler.Application.ProcessAssemblies () [0x0002f] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/mtouch/Application.cs:1407 > at Xamarin.Bundler.Application.BuildManaged () [0x00001] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/mtouch/Application.cs:831 > at Xamarin.Bundler.Application+<>c.<BuildAll>b__134_1 (Xamarin.Bundler.Application v) [0x00000] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/mtouch/Application.cs:779 > at System.Collections.Generic.List`1[T].ForEach (System.Action`1[T] action) [0x00024] in <48b95f3df5804531818f80e28ec60191>:0 > at Xamarin.Bundler.Application.BuildAll () [0x00050] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/mtouch/Application.cs:779 > at Xamarin.Bundler.Driver.Main2 (System.String[] args) [0x00481] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/mtouch/mtouch.cs:1420 > at Xamarin.Bundler.Driver.Main (System.String[] args) [0x0000f] in /Users/builder/data/lanes/5024/152b654a/source/xamarin-macios/tools/mtouch/mtouch.cs:945 https://bugzilla.xamarin.com/show_bug.cgi?id=59798
2017-09-28 18:31:55 +03:00
No reference could be found to the platform assembly (Xamarin.iOS.dll / Xamarin.TVOS.dll / Xamarin.WatchOS.dll) in the executable assembly.
This typically happens where there is no code in the executable project that uses anything from the platform assembly; for instance an empty Main method (and no other code) would show this error:
```csharp
class Program {
void Main (string[] args)
{
}
}
```
Using an API from the platform assembly will solve the error:
```csharp
class Program {
void Main (string[] args)
{
System.Console.WriteLine (typeof (UIKit.UIWindow));
}
}
```
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0124" />
### MT0124: Could not set the current language to '{lang}' (according to LANG={LANG}): {exception}
[mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. (#2162) * [mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. * Refactor required symbol collection to store more information about each symbol (field, function, Objective-C class), and in general make the code more straight forward. * Implement support for generating source code that references these symbols, and do this whenever we can't ask the native linker to keep these symbols (when using bitcode). Additionally make it possible to do this manually, so that the source code can be generated for non-bitcode platforms too (which is useful if the number of symbols is enormous, in which case we might surpass the maximum command-line length). * Also make it possible to completely ignore native symbols, or ignore them on a per-symbol basis. This provides a fallback for users if we get something right and we try to preserve something that shouldn't be preserved (for instance if it doesn't exist), and the user ends up with unfixable linker errors. * Don't collect Objective-C classes unless they're in an assembly with LinkWith attributes. We don't need to preserve Objective-C classes in any other circumstances. * Implement everything for both Xamarin.iOS and Xamarin.Mac, and share the code between them. * Remove previous workaround for bug #51710, since it's no longer needed. * Add tests. https://bugzilla.xamarin.com/show_bug.cgi?id=54417 https://bugzilla.xamarin.com/show_bug.cgi?id=51710 * [mtouch] Make sure to only keep symbols from the current app when code sharing. This fixes a build problem with the interdependent-binding-projects test when testing in Today Extension mode.
2017-06-02 19:29:19 +03:00
[mtouch] Print verbosity using an invariant culture. Fixes #58849. (#2507) * [mtouch/mmp] Set CultureInfo.CurrentCulture according to LANG. This makes it easier to run mtouch/mmp under different locales when testing. Unfortunately mono checks the system locale before checking LANG, which means that there's no built-in way in macOS/mono to specify the current locale without changing the system locale. * [mtouch] Print verbosity using an invariant culture. Fixes #58849. https://bugzilla.xamarin.com/show_bug.cgi?id=58849 * [mtouch/mmp] Fix error code. * [mtouch/mmp] Log/warn when we set the current language.
2017-08-22 10:40:26 +03:00
This is a warning, indicating that the current language couldn't be set to the language in the error message.
The current language will default to the system language.
[mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. (#2162) * [mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. * Refactor required symbol collection to store more information about each symbol (field, function, Objective-C class), and in general make the code more straight forward. * Implement support for generating source code that references these symbols, and do this whenever we can't ask the native linker to keep these symbols (when using bitcode). Additionally make it possible to do this manually, so that the source code can be generated for non-bitcode platforms too (which is useful if the number of symbols is enormous, in which case we might surpass the maximum command-line length). * Also make it possible to completely ignore native symbols, or ignore them on a per-symbol basis. This provides a fallback for users if we get something right and we try to preserve something that shouldn't be preserved (for instance if it doesn't exist), and the user ends up with unfixable linker errors. * Don't collect Objective-C classes unless they're in an assembly with LinkWith attributes. We don't need to preserve Objective-C classes in any other circumstances. * Implement everything for both Xamarin.iOS and Xamarin.Mac, and share the code between them. * Remove previous workaround for bug #51710, since it's no longer needed. * Add tests. https://bugzilla.xamarin.com/show_bug.cgi?id=54417 https://bugzilla.xamarin.com/show_bug.cgi?id=51710 * [mtouch] Make sure to only keep symbols from the current app when code sharing. This fixes a build problem with the interdependent-binding-projects test when testing in Today Extension mode.
2017-06-02 19:29:19 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0125" />
[mtouch] Disable incremental builds for the simulator. Fixes #55712. (#2054) It does not make sense to support incremental builds for the simulator (since no AOT compilation is done), it just makes the test matrix more complicated. So simplify things by removing support for incremental builds. We also ignore any (other) --assembly-build-target arguments, because building to frameworks doesn't make sense either in the simulator. https://bugzilla.xamarin.com/show_bug.cgi?id=55712
2017-04-28 20:34:37 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0125: The --assembly-build-target command-line argument is ignored in the simulator.
[mtouch] Disable incremental builds for the simulator. Fixes #55712. (#2054) It does not make sense to support incremental builds for the simulator (since no AOT compilation is done), it just makes the test matrix more complicated. So simplify things by removing support for incremental builds. We also ignore any (other) --assembly-build-target arguments, because building to frameworks doesn't make sense either in the simulator. https://bugzilla.xamarin.com/show_bug.cgi?id=55712
2017-04-28 20:34:37 +03:00
No action is required, this message is purely informational.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0126" />
[doc] Document MT0127. (#1782)
2017-02-28 17:53:04 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0126: Incremental builds have been disabled because incremental builds are not supported in the simulator.
[doc] Document MT0127. (#1782)
2017-02-28 17:53:04 +03:00
No action is required, this message is purely informational.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0127" />
[mtouch][mmp] Report invalid debug symbols files. Fixes #3200 (#3203) * [mtouch][mmp] Report invalid debug symbols files. Fixes #3200 Try to read the assembly with symbols and, if that fails, warn and fallback to loading them without symbols. This fixes cases were it's not easy to update or delete (e.g. nuget) bad symbols files - so this cannot be an error without causing a lot of pain. However it needs to be reported, otherwise it wont be fixed (by the publisher) and it can limit the debugability of the application and the usefulness of the stacktraces. Finally merge most of the resolver's code between mtouch and mmp so we don't have to fix such issue twice anymore. note: this needs to be slightly updated once we get a version of cecil that can give us a more precise error message. Also bring Rolf's tests from https://github.com/xamarin/xamarin-macios/pull/3079 reference: https://github.com/xamarin/xamarin-macios/issues/3200
2018-01-13 01:39:38 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0127: Incremental builds have been disabled because this version of Xamarin.iOS does not support incremental builds in projects that include more than one third-party binding libraries.
[Mmp] Allow multiple assemblies to be passed to generate the registrar (#3129) By convention, the first assembly is the target platform assembly * Add support for recursive extra search directories.
2018-01-26 03:57:44 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Incremental builds have been disabled automatically because this version of Xamarin.iOS does not always build projects with multiple third-party binding libraries correctly.
[Mmp] Allow multiple assemblies to be passed to generate the registrar (#3129) By convention, the first assembly is the target platform assembly * Add support for recursive extra search directories.
2018-01-26 03:57:44 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
No action is required, this message is purely informational.
[mtouch/mmp] Give users more control over optimizations, and share more code between mtouch and mmp. (#3242) * [mtouch/mmp] Give users more control over optimizations, and share more code between mtouch and mmp. 1. Add an --optimize flag to mtouch/mmp that allows users to select which optimizations to apply (or not). This makes it easier to add future optimizations, and allow users to disable any optimization that causes problems without having to disable many other features. 2. Share as much optimization code as possible between mtouch and mmp. This immediately gives a benefit to mmp, which has three new optimizations only mtouch had: NSObject.IsDirectBinding inlining, IntPtr.Size inlining and dead code elimination. This results in ~6kb of disk space saved for a linked Xamarin.Mac app: * link sdk: [Debug][1], [Release][2] * link all: [Debug][3], [Release][4] Testing also verifies that monotouchtest ([Debug][5], [Release][6]) has not changed size at all, which means that no default optimizations have changed inadvertedly. [1]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-sdk-mac--debug [2]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-sdk-mac--release [3]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-all-mac--debug [4]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-all-mac--release [5]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#monotouchtest-iphonedebug64 [6]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#monotouchtest-iphonerelease64 * [tools] Don't enable the IsDirectBinding optimization by default for Xamarin.Mac apps, it's not safe. * Fix whitespace issues. * [doc] Document optimizations. * Officially support optimizations by adding them to the Versions.plist. * [linker] Improve IntPtr.Size inliner + dead code eliminatior and add tests. * Properly handle operands for the ldc_i4_s instruction (they're sbyte). * Fix less-than condition to actually do a less-than comparison. * Make sure to look up the bitness in the Target, not the Application, since the Application's value will be incorrect when building fat apps (both Is32Build and Is64Build will be true). * Remove unnecessary checks for the IntPtr.Size inliner: this optimization does not depend on other instructions than the IntPtr.get_Size call, so remove the checks that verify surrounding instructions. This makes the IntPtr.Size inliner kick in in more scenarios (such as the new tests). * Add tests. * [tests] Add mmp tests for optimizations. * [tests] Fix XM optimization tests. * [tests] Fix test build error.
2018-01-23 13:33:48 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
For further information see bug #[52727](https://bugzilla.xamarin.com/show_bug.cgi?id=52727).
[mtouch/mmp] Give users more control over optimizations, and share more code between mtouch and mmp. (#3242) * [mtouch/mmp] Give users more control over optimizations, and share more code between mtouch and mmp. 1. Add an --optimize flag to mtouch/mmp that allows users to select which optimizations to apply (or not). This makes it easier to add future optimizations, and allow users to disable any optimization that causes problems without having to disable many other features. 2. Share as much optimization code as possible between mtouch and mmp. This immediately gives a benefit to mmp, which has three new optimizations only mtouch had: NSObject.IsDirectBinding inlining, IntPtr.Size inlining and dead code elimination. This results in ~6kb of disk space saved for a linked Xamarin.Mac app: * link sdk: [Debug][1], [Release][2] * link all: [Debug][3], [Release][4] Testing also verifies that monotouchtest ([Debug][5], [Release][6]) has not changed size at all, which means that no default optimizations have changed inadvertedly. [1]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-sdk-mac--debug [2]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-sdk-mac--release [3]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-all-mac--debug [4]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-all-mac--release [5]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#monotouchtest-iphonedebug64 [6]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#monotouchtest-iphonerelease64 * [tools] Don't enable the IsDirectBinding optimization by default for Xamarin.Mac apps, it's not safe. * Fix whitespace issues. * [doc] Document optimizations. * Officially support optimizations by adding them to the Versions.plist. * [linker] Improve IntPtr.Size inliner + dead code eliminatior and add tests. * Properly handle operands for the ldc_i4_s instruction (they're sbyte). * Fix less-than condition to actually do a less-than comparison. * Make sure to look up the bitness in the Target, not the Application, since the Application's value will be incorrect when building fat apps (both Is32Build and Is64Build will be true). * Remove unnecessary checks for the IntPtr.Size inliner: this optimization does not depend on other instructions than the IntPtr.get_Size call, so remove the checks that verify surrounding instructions. This makes the IntPtr.Size inliner kick in in more scenarios (such as the new tests). * Add tests. * [tests] Add mmp tests for optimizations. * [tests] Fix XM optimization tests. * [tests] Fix test build error.
2018-01-23 13:33:48 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0128" />
[mtouch/mmp] Give users more control over optimizations, and share more code between mtouch and mmp. (#3242) * [mtouch/mmp] Give users more control over optimizations, and share more code between mtouch and mmp. 1. Add an --optimize flag to mtouch/mmp that allows users to select which optimizations to apply (or not). This makes it easier to add future optimizations, and allow users to disable any optimization that causes problems without having to disable many other features. 2. Share as much optimization code as possible between mtouch and mmp. This immediately gives a benefit to mmp, which has three new optimizations only mtouch had: NSObject.IsDirectBinding inlining, IntPtr.Size inlining and dead code elimination. This results in ~6kb of disk space saved for a linked Xamarin.Mac app: * link sdk: [Debug][1], [Release][2] * link all: [Debug][3], [Release][4] Testing also verifies that monotouchtest ([Debug][5], [Release][6]) has not changed size at all, which means that no default optimizations have changed inadvertedly. [1]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-sdk-mac--debug [2]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-sdk-mac--release [3]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-all-mac--debug [4]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#link-all-mac--release [5]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#monotouchtest-iphonedebug64 [6]: https://gist.github.com/rolfbjarne/6b731e3b5ca6170355662e6505c3d492#monotouchtest-iphonerelease64 * [tools] Don't enable the IsDirectBinding optimization by default for Xamarin.Mac apps, it's not safe. * Fix whitespace issues. * [doc] Document optimizations. * Officially support optimizations by adding them to the Versions.plist. * [linker] Improve IntPtr.Size inliner + dead code eliminatior and add tests. * Properly handle operands for the ldc_i4_s instruction (they're sbyte). * Fix less-than condition to actually do a less-than comparison. * Make sure to look up the bitness in the Target, not the Application, since the Application's value will be incorrect when building fat apps (both Is32Build and Is64Build will be true). * Remove unnecessary checks for the IntPtr.Size inliner: this optimization does not depend on other instructions than the IntPtr.get_Size call, so remove the checks that verify surrounding instructions. This makes the IntPtr.Size inliner kick in in more scenarios (such as the new tests). * Add tests. * [tests] Add mmp tests for optimizations. * [tests] Fix XM optimization tests. * [tests] Fix test build error.
2018-01-23 13:33:48 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0128: Could not touch the file '*': *
Update docs about build optimizations. (#3285) * Show final link to official documentation in error help. * Add makefile targets to copy docs to the documentation repo.
2018-01-24 09:26:09 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
A failure occurred when touching a file (which is done to ensure partial builds are done correctly).
[Mmp] Allow multiple assemblies to be passed to generate the registrar (#3129) By convention, the first assembly is the target platform assembly * Add support for recursive extra search directories.
2018-01-26 03:57:44 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This warning can most likely be ignored; in case of any problems file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) and it will be investigated.
[Mmp] Allow multiple assemblies to be passed to generate the registrar (#3129) By convention, the first assembly is the target platform assembly * Add support for recursive extra search directories.
2018-01-26 03:57:44 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT0135" />
Warn when building 32-bit macOS applications (#3564) (#3579) - https://github.com/xamarin/xamarin-macios/issues/3325
2018-02-23 00:38:32 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT0135: Did not link system framework '{0}' (referenced by assembly '{1}') because it was introduced in {2} {3}, and we're using the {2} {4} SDK.
[mmp][mtouch] Better guard framework SDK checks (#3757) (#3796) - https://github.com/xamarin/xamarin-macios/issues/3725 - These frameworks "CoreAudioKit Metal MetalKit MetalPerformanceShaders CoreNFC DeviceCheck" were special cased, but that special case did do an SDK check. - Create a helper method to share check - Add test for MM0135
2018-03-22 04:00:23 +03:00
To build your application, Xamarin.iOS must link against system libraries, some of which depend upon the SDK version specified in the error message. Since you are using an older version of the SDK, invocations to those APIs may fail at runtime.
The recommended way to fix this error is to upgrade Xcode to get the needed SDK. If you have multiple versions of Xcode installed or want to use an Xcode in a non-default location, make sure to set the correct Xcode location in your IDE's preferences.
Alternatively, enable the managed [linker](https://docs.microsoft.com/en-us/xamarin/ios/deploy-test/linker) to remove unused APIs, including (in most cases) the new ones which require the specified library. However, this will not work if your project requires APIs introduced in a newer SDK than the one your Xcode provides.
As a last-straw solution, use an older version of Xamarin.iOS that does not require these new SDKs to be present during the build process.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT1xxx: Project related error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT10xx: Installer / mtouch
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT1xxx file copy / symlinks (project related)
MT10xx installer.cs / mtouch.cs
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1001" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1001: Could not find an application at the specified directory
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1002" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1002: Could not create symlinks, files were copied
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1003" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1003: Could not kill the application '*'. You may have to kill the application manually.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1004" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1004: Could not get the list of installed applications.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT1xxx: Project related error messages
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1005" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1005: Could not kill the application '\*' on the device '\*': *- You may have to kill the application manually.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1006" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1006: Could not install the application '\*' on the device '\*': *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1007" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1007: Failed to launch the application '\*' on the device '\*': *. You can still launch the application manually by tapping on it.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1008" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1008: Failed to launch the simulator
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This error is reported if mtouch failed to launch the
simulator. This can happen sometimes because there is
already a stale or dead simulator process running.
The following command issued on the Unix command line can
be used to kill stuck simulator processes:
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
```bash
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
$ launchctl list|grep UIKitApplication|awk '{print $3}'|xargs launchctl remove
```
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1009" />
### MT1009: Could not copy the assembly '\*' to '\*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[doc] Add blurb about MT1009. (#1608)
2017-02-01 16:30:45 +03:00
This is a known issue in certain versions of Xamarin.iOS.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[doc] Add blurb about MT1009. (#1608)
2017-02-01 16:30:45 +03:00
If this occurs to you, try the following workaround:
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
```bash
sudo chmod 0644 /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/*/*.mdb
```
[doc] Add blurb about MT1009. (#1608)
2017-02-01 16:30:45 +03:00
However, since this issue has been resolved in the latest version of
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Xamarin.iOS, please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new)
[doc] Add blurb about MT1009. (#1608)
2017-02-01 16:30:45 +03:00
with your full version information and build log output.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1010" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1010: Could not load the assembly '*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1011" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1011: Could not add missing resource file: '*'
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1012" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1012: Failed to list the apps on the device '*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1013" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1013: Dependency tracking error: no files to compare. Please file a bug report at http://bugzilla.xamarin.com with a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1014" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1014: Failed to re-use cached version of '*': *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1015" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1015: Failed to create the executable '*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1015" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1015: Failed to create the executable '*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1016" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1016: Failed to create the NOTICE file because a directory already exists with the same name.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Remove the directory `NOTICE` from the project.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1017" />
### MT1017: Failed to create the NOTICE file: *.
<a name="MT1018" />
### MT1018: Your application failed code-signing checks and could not be installed on the device '*'. Check your certificates, provisioning profiles, and bundle ids. Probably your device is not part of the selected provisioning profile (error: 0xe8008015).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1019" />
### MT1019: Your application has entitlements not supported by your current provisioning profile and could not be installed on the device '*'. Please check the iOS Device Log for more detailed information (error: 0xe8008016).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This can happen if:
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* Your application has entitlements that the current provisioning profile does not support.
Possible solutions:
- Specify a different provisioning profile that supports the entitlements your application needs.
- Remove the entitlements not supported in current provisioning profile.
* The device you're trying to deploy to is not included in the provisioning profile you're using.
Possible solutions:
- Create a new app from a template in Xcode, select the same provisioning profile, and deploy to same device. Sometimes Xcode can automatically refresh provisioning profiles with new devices (in other cases Xcode will ask you what to do).
-Go to the iOS Dev Center and update the provisioning profile with the new device, then download the updated provisioning profile to your machine.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
In most cases more information about the failure will be printed to the iOS Device Log, which can help diagnosing the issue.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1020" />
### MT1020: Failed to launch the application '\*' on the device '\*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1021" />
### MT1021: Could not copy the file '\*' to '\*': {2}
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A file could not be copied. The error message from the copy operation has more information about the error.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1022" />
### MT1022: Could not copy the directory '\*' to '\*': {2}
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A directory could not be copied. The error message from the copy operation has more information about the error.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1023" />
### MT1023: Could not communicate with the device to find the application '*' : *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to lookup an application on device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1024" />
### MT1024: The application signature could not be verified on device '*'. Please make sure that the provisioning profile is installed and not expired (error: 0xe8008017).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The device rejected the application install because the signature could not be verified.
Please make sure that the provisioning profile is installed and not expired.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1025" />
### MT1025: Could not list the crash reports on the device *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to list the crash reports on the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1026" />
### MT1026: Could not download the crash report * from the device *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to download the crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1027" />
### MT1027: Can't use Xcode 7+ to launch applications on devices with iOS * (Xcode 7 only supports iOS 6+).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
It is not possible to use Xcode 7+ to launch applications on devices with iOS version below 6.0.
Please use an older version of Xcode, or tap on the app manually to launch it.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1028" />
### MT1028: Invalid device specification: '*'. Expected 'ios', 'watchos' or 'all'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The device specification passed using --device is invalid. Valid values are: 'ios', 'watchos' or 'all'.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1029" />
### MT1029: Could not find an application at the specified directory: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The application path passed to --launchdev does not exist. Please specify a valid app bundle.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1030" />
### MT1030: Launching applications on device using a bundle identifier is deprecated. Please pass the full path to the bundle to launch.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
It's recommended to pass the path to the app to launch on device instead of just the bundle id.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1031" />
### MT1031: Could not launch the app '\*' on the device '\*' because the device is locked. Please unlock the device and try again.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Please unlock the device and try again.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1032" />
[xharness] Add support for uninstalling apps from device. (#1413) The new error message / number is used in mlaunch.
2017-01-02 10:58:46 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1032: This application executable might be too large (* MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.
<a name="MT1033" />
### MT1033: Could not uninstall the application '\*' from the device '\*': *
[xharness] Add support for uninstalling apps from device. (#1413) The new error message / number is used in mlaunch.
2017-01-02 10:58:46 +03:00
[mmp] Add support for building to a framework for the embeddinator.
2017-04-28 19:09:03 +03:00
<!-- 1034 used by mmp -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1035" />
### MT1035: Cannot include different versions of the framework '{name}'
[mtouch] Fix linking with the same third-party framework from both extension and container app. Fixes #56635. (#2112) If both an extension and the container app (or multiple extensions) reference the same binding assembly for a framework, then we'd error out with an internal error when trying to copy the framework from both locations to the container app. So instead detect when we're trying to copy multiple identical (by comparing the on-disk contents) frameworks, and only copy one of them. We'll still show an error if the frameworks are different, but now a nice MT1035 error with a proper error description instead of an internal error. https://bugzilla.xamarin.com/show_bug.cgi?id=56635
2017-05-19 18:05:38 +03:00
It is not possible to link with different versions of the same framework.
This typically happens when an extension references a different version of a framework than the container app (possibly through a third-party binding assembly).
Following this error there will be multiple [MT1036](#MT1036) errors listing the paths for each different framework.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1036" />
### MT1036: Framework '{name}' included from: {path} (Related to previous error)
[mtouch] Fix linking with the same third-party framework from both extension and container app. Fixes #56635. (#2112) If both an extension and the container app (or multiple extensions) reference the same binding assembly for a framework, then we'd error out with an internal error when trying to copy the framework from both locations to the container app. So instead detect when we're trying to copy multiple identical (by comparing the on-disk contents) frameworks, and only copy one of them. We'll still show an error if the frameworks are different, but now a nice MT1035 error with a proper error description instead of an internal error. https://bugzilla.xamarin.com/show_bug.cgi?id=56635
2017-05-19 18:05:38 +03:00
This error is reported only together with [MT1036](#MT1036). Please see [MT1036](#MT1036) for more information.
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT11xx: Debug Service
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT11xx DebugService.cs
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1101" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1101: Could not start app
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1102" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1102: Could not attach to the app (to kill it): *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1103" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1103: Could not detach
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1104" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1104: Failed to send packet: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1105" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1105: Unexpected response type
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1106" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1106: Could not get list of applications on the device: Request timed out.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1107" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1107: Application failed to launch: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Please check if your device is locked.
If you're deploying an enterprise app or using a free provisioning profile, you might have trust the developer (this is explained <a href="http://stackoverflow.com/a/30726375/183422">here</a>).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1108" />
### MT1108: Could not find developer tools for this XX (YY) device.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A few operations from mtouch require the <tt>DeveloperDiskImage.dmg</tt> file to be present. This
file is part of Xcode and is usually located relative to the
SDK that you are using to build against, in
the <tt>Xcode.app/Contents/Developer/iPhoneOS.platform/DeviceSupport/VERSION/DeveloperDiskImage.dmg</tt>.
This error can happen either because you do not have a
DeveloperDiskImage.dmg that matches the device that you have
connected.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1109" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1109: Application failed to launch because the device is locked. Please unlock the device and try again.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Please check if your device is locked.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1110" />
### MT1110: Application failed to launch because of iOS security restrictions. Please ensure the developer is trusted.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
If you're deploying an enterprise app or using a free provisioning profile, you might have trust the developer (this is explained <a href="http://stackoverflow.com/a/30726375/183422">here</a>).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1111" />
### MT1111: Application launched successfully, but it's not possible to wait for the app to exit as requested because it's not possible to detect app termination when launching using gdbserver.
[xharness] Properly handle failure by mlaunch to wait for app exit. (#2946) Detect MT1111 from mlaunch (which means mlaunch won't wait for the app to exit), and instead use test run completion to determine test completion. The main drawback is that if the test app crashes, it won't be detected (the test run will time out, and reported as such), but it's still an improvement over the current behavior (the tests may complete successfully, and still be reported as timed out). This also requires bumping maccore to get an updated mlaunch (one that reports MT1111).
2017-11-02 14:46:18 +03:00
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT12xx: Simulator
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT12xx simcontroller.cs
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1201" />
### MT1201: Could not load the simulator: *
<a name="MT1202" />
### MT1202: Invalid simulator configuration: *
<a name="MT1203" />
### MT1203: Invalid simulator specification: *
<a name="MT1204" />
### MT1204: Invalid simulator specification '*': runtime not specified.
<a name="MT1205" />
### MT1205: Invalid simulator specification '*': device type not specified.
<a name="MT1206" />
### MT1206: Could not find the simulator runtime '*'.
<a name="MT1207" />
### MT1207: Could not find the simulator device type '*'.
<a name="MT1208" />
### MT1208: Could not find the simulator runtime '*'.
<a name="MT1209" />
### MT1209: Could not find the simulator device type '*'.
<a name="MT1210" />
### MT1210: Invalid simulator specification: \*, unknown key '\*'
<a name="MT1211" />
### MT1211: The simulator version '\*' does not support the simulator type '\*'
<a name="MT1212" />
### MT1212: Failed to create a simulator version where type = * and runtime = *.
<a name="MT1213" />
### MT1213: Invalid simulator specification for Xcode 4: *
<a name="MT1214" />
### MT1214: Invalid simulator specification for Xcode 5: *
<a name="MT1215" />
### MT1215: Invalid SDK specified: *
<a name="MT1216" />
### MT1216: Could not find the simulator UDID '*'.
<a name="MT1217" />
### MT1217: Could not load the app bundle at '*'.
<a name="MT1218" />
### MT1218: No bundle identifier found in the app at '*'.
<a name="MT1219" />
### MT1219: Could not find the simulator for '*'.
<a name="MT1220" />
### MT1220: Could not find the latest simulator runtime for device '*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This usually indicates a problem with Xcode.
Things to try to fix this:
* Use the simulator once in Xcode.
* Pass an explicit SDK version using --sdk <version>.
* Reinstall Xcode.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1221" />
### MT1221: Could not find the paired iPhone simulator for the WatchOS simulator '*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
When launching a WatchOS app in a WatchOS simulator, there must be a paired iOS Simulator as well.
Watch simulators can be paired with iOS Simulators using Xcode's Devices UI (menu Window -> Devices).
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT13xx: [LinkWith]
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT13xx [LinkWith]
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1301" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1301: Native library `*` (\*) was ignored since it does not match the current build architecture(s) (\*)
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1302" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1302: Could not extract the native library '*' from '+'. Please ensure the native library was properly embedded in the managed assembly (if the assembly was built using a binding project, the native library must be included in the project, and its Build Action must be 'ObjcBindingNativeLibrary').
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1303" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT1303: Could not decompress the native framework '\*' from '\*'. Please review the build log for more information from the native 'zip' command.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Could not decompress the specified native framework from the binding library.
Please review the bulid log for more information about this failure from the native 'zip' command.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1304" />
### MT1304: The embedded framework '*' in * is invalid: it does not contain an Info.plist.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The specified embedded framework does not contain an Info.plist, and is therefore not a valid framework.
Please make sure the framework is valid.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1305" />
### MT1305: The binding library '\*' contains a user framework (\*), but embedded user frameworks require iOS 8.0 (the current deployment target is *). Please set the deployment target in the Info.plist file to at least 8.0.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The specified binding library contains an embedded framework, but Xamarin.iOS only supports embedded frameworks on iOS 8.0 or later.
Please set the deployment target in the Info.plist file to at least 8.0 to solve this error (or don't use embedded frameworks).
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT14xx: Crash Reports
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT14xx CrashReports.cs
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1400" />
### MT1400: Could not open crash report service: AFCConnectionOpen returned *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to access crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1401" />
### MT1401: Could not close crash report service: AFCConnectionClose returned *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to access crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1402" />
### MT1402: Could not read file info for *: AFCFileInfoOpen returned *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to access crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1403" />
### MT1403: Could not read crash report: AFCDirectoryOpen (*) returned: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to access crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1404" />
### MT1404: Could not read crash report: AFCFileRefOpen (*) returned: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to access crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1405" />
### MT1405: Could not read crash report: AFCFileRefRead (*) returned: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to access crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1406" />
### MT1406: Could not list crash reports: AFCDirectoryOpen (*) returned: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when trying to access crash reports from the device.
Things to try to solve this:
* Delete the application from the device and try again.
* Disconnect the device and reconnect it.
* Reboot the device.
* Reboot the Mac.
* Synchronize the device with iTunes (this will remove any crash reports from the device).
[macos] Fix target framework detection issues in mmp (#2096) - Also detect mismatches between referenced XM.dll and target framework selected
2017-05-30 17:23:28 +03:00
<!--- 1407 used by mmp -->
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT16xx: MachO
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT16xx MachO.cs
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1600" />
### MT1600: Not a Mach-O dynamic library (unknown header '0x*'): *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred while processing the dynamic library in question.
Please make sure the dynamic library is a valid Mach-O dynamic library.
The format of a library can be verified using the `file` command from a terminal:
file -arch all -l /path/to/library.dylib
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1601" />
### MT1601: Not a static library (unknown header '*'): *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred while processing the static library in question.
Please make sure the static library is a valid Mach-O static library.
The format of a library can be verified using the `file` command from a terminal:
file -arch all -l /path/to/library.a
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1602" />
### MT1602: Not a Mach-O dynamic library (unknown header '0x*'): *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred while processing the dynamic library in question.
Please make sure the dynamic library is a valid Mach-O dynamic library.
The format of a library can be verified using the `file` command from a terminal:
file -arch all -l /path/to/library.dylib
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1603" />
### MT1603: Unknown format for fat entry at position * in *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred while processing the fat archive in question.
Please make sure the fat archive is valid.
The format of a fat archive can be verified using the `file` command from a terminal:
file -arch all -l /path/to/file
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT1604" />
### MT1604: File of type * is not a MachO file (*).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred while processing the MachO file in question.
Please make sure the file is a valid Mach-O dynamic library.
The format of a file can be verified using the `file` command from a terminal:
file -arch all -l /path/to/file
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT2xxx: Linker error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT2xxx Linker
MT20xx Linker (general) errors
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2001" />
### MT2001: Could not link assemblies
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[linker] Capture and show more information when a MT2001 error occurs (#1947)
2017-03-30 22:41:56 +03:00
This error means that the managed linker encountered an unexpected error, e.g. an exception, and could not complete or save the assembly being processed. More information about the exact error will be part of the build log, e.g.
```
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
error MT2001: Could not link assemblies.
[linker] Capture and show more information when a MT2001 error occurs (#1947)
2017-03-30 22:41:56 +03:00
Method: `System.Void Todo.TodoListPageCS/<<-ctor>b__1_0>d::SetStateMachine(System.Runtime.CompilerServices.IAsyncStateMachine)`
Assembly: `QuickTodo, Version=1.0.6297.28241, Culture=neutral, PublicKeyToken=null`
Reason: Value cannot be null.
Parameter name: instruction
```
It is important to file a bug report for such issues. In most case a workaround can be provided until a proper fix is published. The above information is critical (along with a test case and/or the assembly binairy) to resolve the issue.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2002" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2002: Can not resolve reference: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2003" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2003: Option '*' will be ignored since linking is disabled
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2004" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2004: Extra linker definitions file '*' could not be located.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2005" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2005: Definitions from '*' could not be parsed.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2006" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2006: Can not load mscorlib.dll from: *. Please reinstall Xamarin.iOS.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This generally indicates that there is a problem with your Xamarin.iOS installation. Please try reinstalling Xamarin.iOS.
<!--- 2007 used by mmp -->
<!--- 2009 used by mmp -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2010" />
### MT2010: Unknown HttpMessageHandler `*`. Valid values are HttpClientHandler (default), CFNetworkHandler or NSUrlSessionHandler
<a name="MT2011" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2011: Unknown TlsProvider `*`. Valid values are default or appletls.
[mtouch][mmp] Only allow `appletls` for the TLS provider (#1132) The old `legacy` option will now be reported as a warning. That's by design an warning would require manually editing the .csproj file (when the UI gets removed, as planned, from the IDE). This is part of https://trello.com/c/SrgU38DN/647-only-ship-support-appletls Note: The BCL changes will happen in later stages.
2016-11-08 22:42:40 +03:00
The value given to `tls-provider=` is not a valid TLS (Transport Layer Security) provider.
The `default` and `appletls` are the only valid values and both represent the same option, which is to provide the SSL/TLS support using the native Apple TLS API.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--- 2012 used by mmp -->
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!--- 2013 used by mmp -->
<!--- 2014 used by mmp -->
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2015" />
### MT2015: Invalid HttpMessageHandler `*` for watchOS. The only valid value is NSUrlSessionHandler.
Fix default http message handler for watchOS. (#873) * Fix default http message handler for watchOS. Fix default http message handler for watchOS to be NSUrlSessionHandler (the previous attempt at eb7c2fd was quite incomplete), and make sure HttpClientHandler is never used (show errors if someone tries). * [tests] Remove explicit http client handler from project files. Just use the default instead, since the set of valid http client handlers varies between platforms.
2016-09-22 15:29:18 +03:00
[mtouch] Make MT2015 (invalid HttpMessageHandler) a warning for known http message handlers on watchOS. Fixes #46552. (#1134) Earlier versions of Xamarin Studio stored an invalid http message handler in watchOS project files, which would cause a build error. In addition Xamarin Studio removed the UI to set the http message handler (since only one value is valid), which meant that the user had to edit the project file by hand to get around this build error. So make it a warning instead (and document what the user has to do to fix the warning). https://bugzilla.xamarin.com/show_bug.cgi?id=46552
2016-11-08 19:13:53 +03:00
This is a warning that occurs because the project file specifies an invalid HttpMessageHandler.
Earlier versions of our preview tools generated by default an invalid value in the project file.
To fix this warning, open the project file in a text editor, and remove all HttpMessageHandler nodes from the XML.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2016" />
### MT2016: Invalid TlsProvider `legacy` option. The only valid value `appletls` will be used.
[mtouch][mmp] Only allow `appletls` for the TLS provider (#1132) The old `legacy` option will now be reported as a warning. That's by design an warning would require manually editing the .csproj file (when the UI gets removed, as planned, from the IDE). This is part of https://trello.com/c/SrgU38DN/647-only-ship-support-appletls Note: The BCL changes will happen in later stages.
2016-11-08 22:42:40 +03:00
The `legacy` provider, which was a fully managed SSLv3 / TLSv1 only provider, is not shipped with Xamarin.iOS anymore. Projects that were using this old provider and now build with the newer `appletls` one.
To fix this warning, open the project file in a text editor, and remove all `MtouchTlsProvider`` nodes from the XML.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2017" />
### MT2017: Could not process XML description.
[mmp/btouch] Better error when bad xml linker input is given to mmp/mtouch (#1614) Fixes: https://bugzilla.xamarin.com/show_bug.cgi?id=52238 If you give mtouch/mmp a linker xml file with bad input for example a Xamarin.iOS app and the linker.xml has a reference to Xamarin.Mac instead of X.I.dll i.e. <?xml version="1.0" encoding="UTF-8" ?> <linker> <assembly fullname="Xamarin.Mac"> <type fullname="ObjCRuntime.Constants"/> </assembly> </linker> You will get a not so helpful generic error MT2001 Could not link assemblies. Reason: Failed to process XML description: <unspecified> It seems that when you use a xml file for linker you get a `XmlResolutionException` from cecil when it fails to resolve and the better error comes from the inner exception so we use that instead. New error output for XmlResolutionException: MT2017: Could not process XML description: Failed to resolve assembly: 'Xamarin.Mac, Culture=neutral, PublicKeyToken=null'
2017-02-03 23:04:06 +03:00
This means there is an error on the [custom XML linker configuration file](https://developer.xamarin.com/guides/cross-platform/advanced/custom_linking/) you provided, please review your file.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2018" />
### MT2018: The assembly '\*' is referenced from two different locations: '\*' and '*'.
[mtouch] Create a custom AssemblyCollection class. Create a custom AssemblyCollection class that contains a dictionary with assembly identity (name) -> Assembly mapping. This also means that we can detect if we end up loading multiple assemblies with the same identity, and show an error in that case (even if that case should never happen since we cache assemblies based on the identity, it's nice to have code that ensures it).
2017-01-24 12:48:40 +03:00
The assembly mentioned in the error message is loaded from multiple locations. Make sure to always use the same version of an assembly.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2019" />
### MT2019: Can not load the root assembly '*'
[mtouch] Warn if mtouch loads an assembly from a different location than requested. Warn if mtouch loads an assembly from a different location than requested (which might be because there are multiple assemblies with the same name). Also rework the MT0023 check a bit by explicitly loading the root assembly first, and then detecting if any loaded assemblies matches the root assembly. This results in code that's a bit more obvious, and it also works correctly with extensions (previously the entire MT0023 check was skipped for extensions).
2017-01-25 12:47:51 +03:00
The root assembly could not be loaded. Please verify that the path in the error message refers to an existing file, and that it's a valid .NET assembly.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT202x" />
### MT202x: Binding Optimizer failed processing `...`.
[mtouch][linker] Provide a more specific error code when OptimizeGeneratedCodeSubStep fails (#903) The MT2001 error is a general, something went bad, in the linker code base. The stack trace is often enough to track down issues but in some cases it would be easier to ask customers for a specific assembly (rather than their complete project) to investigate an issue. Example: error MT2103: Binding Optimizer failed processing `System.Void GoogleConversionTracking.Unified.GoogleConversionPing::.ctor()`. --- inner exception System.NullReferenceException: Object reference not set to an instance of an object at MonoTouch.Tuner.OptimizeGeneratedCodeSubStep.ProcessIsDirectBinding (Mono.Cecil.MethodDefinition caller, Mono.Cecil.Cil.Instruction ins) [0x00026] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/MonoTouch.Tuner/OptimizeGeneratedCodeSubStep.cs:264 at MonoTouch.Tuner.OptimizeGeneratedCodeSubStep.ProcessCalls (Mono.Cecil.MethodDefinition caller, Int32 i) [0x00337] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/MonoTouch.Tuner/OptimizeGeneratedCodeSubStep.cs:197 at MonoTouch.Tuner.OptimizeGeneratedCodeSubStep.Process (Mono.Cecil.MethodDefinition method) [0x0007b] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/MonoTouch.Tuner/OptimizeGeneratedCodeSubStep.cs:81 at Xamarin.Linker.StateSubStep.ProcessMethod (Mono.Cecil.MethodDefinition method) [0x00004] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/CoreOptimizeGeneratedCode.cs:48 --- at Xamarin.Linker.StateSubStep.ProcessMethod (Mono.Cecil.MethodDefinition method) [0x00014] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/CoreOptimizeGeneratedCode.cs:50 at Mono.Tuner.SubStepDispatcher.DispatchMethod (Mono.Cecil.MethodDefinition method) [0x0001d] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:215 at Mono.Tuner.SubStepDispatcher.BrowseMethods (ICollection methods) [0x0001c] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:167 at Mono.Tuner.SubStepDispatcher.BrowseTypes (ICollection types) [0x0006b] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:145 at Mono.Tuner.SubStepDispatcher.BrowseAssemblies (IEnumerable`1 assemblies) [0x00050] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:123 at Mono.Tuner.SubStepDispatcher.Process (Mono.Linker.LinkContext context) [0x0000f] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:104 at Mono.Linker.Pipeline.Process (Mono.Linker.LinkContext context) [0x00027] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/linker/Mono.Linker/Pipeline.cs:118 at MonoTouch.Tuner.Linker.Process (MonoTouch.Tuner.LinkerOptions options, MonoTouch.Tuner.MonoTouchLinkContext& context, System.Collections.Generic.List`1& assemblies) [0x000ac] in /Users/poupou/git/xamarin/xamarin-macios/tools/mtouch/Tuning.cs:79 Right now the MT2001 would only include the inner exception, which does not include any clue to which assembly caused the exception. Note: The same pattern to be applied to other BaseSubStep subclasses in separate commits. Related to (but not the fix for) https://bugzilla.xamarin.com/show_bug.cgi?id=44701
2016-09-28 18:46:14 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to optimize generated binding code. The element causing the issue is named in the error message. To fix this issue the assembly named (or containing the type or method named) will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[mtouch][linker] Provide a more specific error code when OptimizeGeneratedCodeSubStep fails (#903) The MT2001 error is a general, something went bad, in the linker code base. The stack trace is often enough to track down issues but in some cases it would be easier to ask customers for a specific assembly (rather than their complete project) to investigate an issue. Example: error MT2103: Binding Optimizer failed processing `System.Void GoogleConversionTracking.Unified.GoogleConversionPing::.ctor()`. --- inner exception System.NullReferenceException: Object reference not set to an instance of an object at MonoTouch.Tuner.OptimizeGeneratedCodeSubStep.ProcessIsDirectBinding (Mono.Cecil.MethodDefinition caller, Mono.Cecil.Cil.Instruction ins) [0x00026] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/MonoTouch.Tuner/OptimizeGeneratedCodeSubStep.cs:264 at MonoTouch.Tuner.OptimizeGeneratedCodeSubStep.ProcessCalls (Mono.Cecil.MethodDefinition caller, Int32 i) [0x00337] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/MonoTouch.Tuner/OptimizeGeneratedCodeSubStep.cs:197 at MonoTouch.Tuner.OptimizeGeneratedCodeSubStep.Process (Mono.Cecil.MethodDefinition method) [0x0007b] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/MonoTouch.Tuner/OptimizeGeneratedCodeSubStep.cs:81 at Xamarin.Linker.StateSubStep.ProcessMethod (Mono.Cecil.MethodDefinition method) [0x00004] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/CoreOptimizeGeneratedCode.cs:48 --- at Xamarin.Linker.StateSubStep.ProcessMethod (Mono.Cecil.MethodDefinition method) [0x00014] in /Users/poupou/git/xamarin/xamarin-macios/tools/linker/CoreOptimizeGeneratedCode.cs:50 at Mono.Tuner.SubStepDispatcher.DispatchMethod (Mono.Cecil.MethodDefinition method) [0x0001d] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:215 at Mono.Tuner.SubStepDispatcher.BrowseMethods (ICollection methods) [0x0001c] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:167 at Mono.Tuner.SubStepDispatcher.BrowseTypes (ICollection types) [0x0006b] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:145 at Mono.Tuner.SubStepDispatcher.BrowseAssemblies (IEnumerable`1 assemblies) [0x00050] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:123 at Mono.Tuner.SubStepDispatcher.Process (Mono.Linker.LinkContext context) [0x0000f] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/tuner/Mono.Tuner/Dispatcher.cs:104 at Mono.Linker.Pipeline.Process (Mono.Linker.LinkContext context) [0x00027] in /Users/poupou/git/xamarin/xamarin-macios/external/mono/mcs/tools/linker/Mono.Linker/Pipeline.cs:118 at MonoTouch.Tuner.Linker.Process (MonoTouch.Tuner.LinkerOptions options, MonoTouch.Tuner.MonoTouchLinkContext& context, System.Collections.Generic.List`1& assemblies) [0x000ac] in /Users/poupou/git/xamarin/xamarin-macios/tools/mtouch/Tuning.cs:79 Right now the MT2001 would only include the inner exception, which does not include any clue to which assembly caused the exception. Note: The same pattern to be applied to other BaseSubStep subclasses in separate commits. Related to (but not the fix for) https://bugzilla.xamarin.com/show_bug.cgi?id=44701
2016-09-28 18:46:14 +03:00
The last digit `x` will be:
* `0` for an assembly name;
* `1` for a type name;
* `3` for a method name;
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2030" />
### MT2030: Remove User Resources failed processing `...`.
[mtouch][mmp] Unify user resources removal as a link step (#1026) Right now the logic exists in a few places, both in and outside the linker. We recently began to use part of the linker pipeline in normal / all builds so it's easier to share (and unify) the code now. The real gain is to avoid copying assemblies, in particular large ones, more than strictly needed while building. E.g. a build including a very large 1.3GB assembly, with several native libraries embedded, save a lot of time avoiding the rewrites mtouch (before) Total time: 64202 ms mtouch (after) Total time: 34840 ms * Add XM support for RemoveUserResourcesSubStep * Tests supplied by @chamons
2016-11-01 20:11:25 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to remove user resources. The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[mtouch][mmp] Unify user resources removal as a link step (#1026) Right now the logic exists in a few places, both in and outside the linker. We recently began to use part of the linker pipeline in normal / all builds so it's easier to share (and unify) the code now. The real gain is to avoid copying assemblies, in particular large ones, more than strictly needed while building. E.g. a build including a very large 1.3GB assembly, with several native libraries embedded, save a lot of time avoiding the rewrites mtouch (before) Total time: 64202 ms mtouch (after) Total time: 34840 ms * Add XM support for RemoveUserResourcesSubStep * Tests supplied by @chamons
2016-11-01 20:11:25 +03:00
User resources are files included inside assemblies (as resources) that needs to be extracted, at build time, to create the application bundle. This includes:
* `__monotouch_content_*` and `__monotouch_pages_*` resources; and
* Native libraries embedded inside a binding assembly;
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2040" />
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2040: Default HttpMessageHandler setter failed processing `...`.
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to set the default `HttpMessageHandler` for the application. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2050" />
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2050: Code Remover failed processing `...`.
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to remove code from BCL shipping with the application. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2060" />
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2060: Sealer failed processing `...`.
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to seal types or methods (final) or when devirtualizing some methods. The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2070" />
[linker] Preserve smart enum conversion methods when needed.
2017-07-06 11:42:27 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2070: Metadata Reducer failed processing `...`.
[docs] Add missing entry about MT2090 errors. (#2297)
2017-07-07 18:17:39 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to reduce the metadata from the application. The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[docs] Add missing entry about MT2090 errors. (#2297)
2017-07-07 18:17:39 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2080" />
[linker] Preserve smart enum conversion methods when needed.
2017-07-06 11:42:27 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2080: MarkNSObjects failed processing `...`.
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to mark `NSObject` subclasses from the application. The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[linker] Update BaseSubStep subclasses to use ExceptionalSubStep (#1507) This allows mtouch to give better error message when something unexpected occurs in the linker pipeline (at least for the sub-steps). Practically it means fewer, contextless MT2001 errors. The replacements error code are more precise, e.g. * what was being done; * what was being processed and helps both diagnosing and, possibly, gives clues for workarounds
2017-01-16 19:42:41 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2090" />
[Do not merge yet] Update to mono 2017-04 branch (#1960) * Update to mono 2017-04 branch * Patch from Zoltan to fix build error with CppSharp.CppParser.dll * Include new linker files in Makefile, based on mareks commit * [msbuild] Fix running bgen for Xamarin.Mac. bgen must be executed with the system mono, not bmac-mobile-mono, and without the MONO_PATH variable set. * System.Data tests should act as if they are running on mobile profile * Add --runtime=mobile to mono flags in Modern * Move runtime launcher options up * System.Data tests should use Mobile profile (mac fix) * Bump 2017-04 to pick up AOT and assembly resolution fixes * Build fixes for netstandard.dll and System.Drawing.Primitives.dll The new handling went in with https://github.com/mono/mono/pull/4501. I also noticed that WatchOS was missing a target for System.Drawing.Primitives.dll, so I added that. * Add netstandard.dll to 2.1/Facades and System.Drawing.Primitives.dll to WatchOS * Fix 2.1/Facades/netstandard.dll build * Fix the netstandard targets * Bump mono to latest 2017-04 commit * [xharness] Fix adding defines to csproj by correctly detecting existing defines. * Bump mono to latest 2017-04 commit * [mtouch] Update csproj with new files. * [mtouch] Improve reporting for MarkExceptions from the linker. * Bump mono to latest 2017-04 commit * Bump mono to pick up latest 2017-04 branch commit (Fixes #55436) Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=55436 * Add a missing Makefile dependency * Chris Hamons patch to apply --runtime=mobile as necessary at AOT time (It is currently being applied for some configurations at runtime only) * Bump system mono * Bump mono for assembly loader changes * Bump system mono * Update assemblies list as some where moved to facades https://github.com/mono/mono/commit/6ca5ec442b494bed8cfb44258c1c73c091ba3122 https://github.com/mono/mono/commit/c38e4d9220b16488e6f8f9e1f05aed4a8af16e62 * Bump mono to latest 2017-04 commit * Add another new facade * Bump mono to tip of 2017-04. * Bump mono to tip of 2017-04. * [tests][mtouch] Adjust tests to cope with fewer assemblies being included in linked apps. Fixes #56307 and #56308. System.dll is now completely linked away unless the app actually uses any System.dll API. This is the change that caused this to change: https://github.com/mono/mono/commit/4960d5d2a28a08476ee4239e1746f04afce41c13 Previously the following types would always be kept by the linker: ``` $ monodis --typedef System.dll Typedef Table 1: (null) (flist=1, mlist=1, flags=0x0, extends=0x0) 2: ObjCRuntime.INativeObject (flist=1, mlist=1, flags=0xa0, extends=0x0) 3: Mono.Net.CFObject (flist=1, mlist=2, flags=0x100000, extends=0x5) 4: Mono.Net.CFArray (flist=4, mlist=19, flags=0x100, extends=0xc) 5: Mono.Net.CFNumber (flist=5, mlist=32, flags=0x100100, extends=0xc) 6: Mono.Net.CFRange (flist=5, mlist=41, flags=0x100108, extends=0x25) 7: Mono.Net.CFString (flist=7, mlist=42, flags=0x100100, extends=0xc) 8: Mono.Net.CFData (flist=8, mlist=53, flags=0x100100, extends=0xc) 9: Mono.Net.CFDictionary (flist=8, mlist=63, flags=0x0, extends=0xc) 10: Mono.Net.CFMutableDictionary (flist=10, mlist=75, flags=0x100100, extends=0x24) 11: Mono.Net.CFUrl (flist=10, mlist=80, flags=0x100100, extends=0xc) 12: Mono.Net.CFRunLoop (flist=10, mlist=83, flags=0x100100, extends=0xc) 13: Mono.Net.CFBoolean (flist=10, mlist=94, flags=0x100, extends=0x5) 14: Mono.AppleTls.SecCertificate (flist=13, mlist=106, flags=0x100100, extends=0x5) 15: Mono.AppleTls.SecIdentity (flist=14, mlist=122, flags=0x100, extends=0x5) 16: Mono.AppleTls.SecIdentity/ImportOptions (flist=19, mlist=134, flags=0x100105, extends=0x5) 17: Mono.AppleTls.SecKey (flist=19, mlist=134, flags=0x100100, extends=0x5) 18: Mono.AppleTls.SecStatusCode (flist=21, mlist=141, flags=0x100, extends=0x69) 19: Mono.AppleTls.SecTrustResult (flist=395, mlist=141, flags=0x100, extends=0x69) 20: Mono.AppleTls.SecImportExport (flist=404, mlist=141, flags=0x100100, extends=0x5) 21: Mono.AppleTls.SecImportExport/<>c (flist=404, mlist=144, flags=0x102103, extends=0x5) 22: Mono.AppleTls.SecPolicy (flist=406, mlist=147, flags=0x100100, extends=0x5) 23: Mono.AppleTls.SecTrust (flist=407, mlist=154, flags=0x100100, extends=0x5) 24: System.Security.Cryptography.OidGroup (flist=408, mlist=174, flags=0x101, extends=0x69) 25: System.Security.Cryptography.Oid (flist=420, mlist=174, flags=0x100101, extends=0x5) 26: System.Security.Cryptography.CAPI (flist=423, mlist=176, flags=0x100180, extends=0x5) 27: System.Security.Cryptography.AsnEncodedData (flist=423, mlist=178, flags=0x100101, extends=0x5) 28: System.Security.Cryptography.X509Certificates.X509Utils (flist=424, mlist=179, flags=0x100100, extends=0x5) 29: System.Security.Cryptography.X509Certificates.PublicKey (flist=424, mlist=181, flags=0x100101, extends=0x5) 30: System.Security.Cryptography.X509Certificates.X509Certificate2 (flist=429, mlist=188, flags=0x102101, extends=0x51) 31: System.Security.Cryptography.X509Certificates.X509Certificate2Impl (flist=431, mlist=204, flags=0x100080, extends=0x55) 32: System.Security.Cryptography.X509Certificates.X509CertificateCollection (flist=431, mlist=209, flags=0x102101, extends=0x6d) 33: System.Security.Cryptography.X509Certificates.X509CertificateCollection/X509CertificateEnumerator (flist=431, mlist=212, flags=0x100102, extends=0x5) 34: System.Security.Cryptography.X509Certificates.X509Helper2 (flist=432, mlist=217, flags=0x100180, extends=0x5) 35: <PrivateImplementationDetails> (flist=432, mlist=218, flags=0x100, extends=0x5) 36: <PrivateImplementationDetails>/__StaticArrayInitTypeSize=9 (flist=433, mlist=219, flags=0x113, extends=0x25) ``` Some of the above types from System.dll implemented ObjCRuntime.INativeObject (from System.dll), which our linker detected as implementing ObjCRuntime.INativeObject (from Xamarin.iOS.dll), so these types were treated as custom NSObject subclasses, and the MarkNSObjects linker step would mark them (which would in turn cause all the other types in the list to be marked). With that change, these types now implement ObjCRuntimeInternal.INativeObject, and the linker does not treat them as custom NSObject subclasses anymore. I think the new behavior is correct: these types do not actually inherit from the real NSObject/INativeObject, so the linker should not treat them as such. This may run into different bugs because the linker might now remove more stuff than before, but that would be a different issue. This means that the fix is to modify these tests accordingly. https://bugzilla.xamarin.com/show_bug.cgi?id=56307 https://bugzilla.xamarin.com/show_bug.cgi?id=56308 * Bump mono to latest. * Fix merge conflict that was missed * [mtouch] Renumber new error which clashes with an existing error number in master.
2017-05-29 19:39:29 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2090: Inliner failed processing `...`.
[Do not merge yet] Update to mono 2017-04 branch (#1960) * Update to mono 2017-04 branch * Patch from Zoltan to fix build error with CppSharp.CppParser.dll * Include new linker files in Makefile, based on mareks commit * [msbuild] Fix running bgen for Xamarin.Mac. bgen must be executed with the system mono, not bmac-mobile-mono, and without the MONO_PATH variable set. * System.Data tests should act as if they are running on mobile profile * Add --runtime=mobile to mono flags in Modern * Move runtime launcher options up * System.Data tests should use Mobile profile (mac fix) * Bump 2017-04 to pick up AOT and assembly resolution fixes * Build fixes for netstandard.dll and System.Drawing.Primitives.dll The new handling went in with https://github.com/mono/mono/pull/4501. I also noticed that WatchOS was missing a target for System.Drawing.Primitives.dll, so I added that. * Add netstandard.dll to 2.1/Facades and System.Drawing.Primitives.dll to WatchOS * Fix 2.1/Facades/netstandard.dll build * Fix the netstandard targets * Bump mono to latest 2017-04 commit * [xharness] Fix adding defines to csproj by correctly detecting existing defines. * Bump mono to latest 2017-04 commit * [mtouch] Update csproj with new files. * [mtouch] Improve reporting for MarkExceptions from the linker. * Bump mono to latest 2017-04 commit * Bump mono to pick up latest 2017-04 branch commit (Fixes #55436) Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=55436 * Add a missing Makefile dependency * Chris Hamons patch to apply --runtime=mobile as necessary at AOT time (It is currently being applied for some configurations at runtime only) * Bump system mono * Bump mono for assembly loader changes * Bump system mono * Update assemblies list as some where moved to facades https://github.com/mono/mono/commit/6ca5ec442b494bed8cfb44258c1c73c091ba3122 https://github.com/mono/mono/commit/c38e4d9220b16488e6f8f9e1f05aed4a8af16e62 * Bump mono to latest 2017-04 commit * Add another new facade * Bump mono to tip of 2017-04. * Bump mono to tip of 2017-04. * [tests][mtouch] Adjust tests to cope with fewer assemblies being included in linked apps. Fixes #56307 and #56308. System.dll is now completely linked away unless the app actually uses any System.dll API. This is the change that caused this to change: https://github.com/mono/mono/commit/4960d5d2a28a08476ee4239e1746f04afce41c13 Previously the following types would always be kept by the linker: ``` $ monodis --typedef System.dll Typedef Table 1: (null) (flist=1, mlist=1, flags=0x0, extends=0x0) 2: ObjCRuntime.INativeObject (flist=1, mlist=1, flags=0xa0, extends=0x0) 3: Mono.Net.CFObject (flist=1, mlist=2, flags=0x100000, extends=0x5) 4: Mono.Net.CFArray (flist=4, mlist=19, flags=0x100, extends=0xc) 5: Mono.Net.CFNumber (flist=5, mlist=32, flags=0x100100, extends=0xc) 6: Mono.Net.CFRange (flist=5, mlist=41, flags=0x100108, extends=0x25) 7: Mono.Net.CFString (flist=7, mlist=42, flags=0x100100, extends=0xc) 8: Mono.Net.CFData (flist=8, mlist=53, flags=0x100100, extends=0xc) 9: Mono.Net.CFDictionary (flist=8, mlist=63, flags=0x0, extends=0xc) 10: Mono.Net.CFMutableDictionary (flist=10, mlist=75, flags=0x100100, extends=0x24) 11: Mono.Net.CFUrl (flist=10, mlist=80, flags=0x100100, extends=0xc) 12: Mono.Net.CFRunLoop (flist=10, mlist=83, flags=0x100100, extends=0xc) 13: Mono.Net.CFBoolean (flist=10, mlist=94, flags=0x100, extends=0x5) 14: Mono.AppleTls.SecCertificate (flist=13, mlist=106, flags=0x100100, extends=0x5) 15: Mono.AppleTls.SecIdentity (flist=14, mlist=122, flags=0x100, extends=0x5) 16: Mono.AppleTls.SecIdentity/ImportOptions (flist=19, mlist=134, flags=0x100105, extends=0x5) 17: Mono.AppleTls.SecKey (flist=19, mlist=134, flags=0x100100, extends=0x5) 18: Mono.AppleTls.SecStatusCode (flist=21, mlist=141, flags=0x100, extends=0x69) 19: Mono.AppleTls.SecTrustResult (flist=395, mlist=141, flags=0x100, extends=0x69) 20: Mono.AppleTls.SecImportExport (flist=404, mlist=141, flags=0x100100, extends=0x5) 21: Mono.AppleTls.SecImportExport/<>c (flist=404, mlist=144, flags=0x102103, extends=0x5) 22: Mono.AppleTls.SecPolicy (flist=406, mlist=147, flags=0x100100, extends=0x5) 23: Mono.AppleTls.SecTrust (flist=407, mlist=154, flags=0x100100, extends=0x5) 24: System.Security.Cryptography.OidGroup (flist=408, mlist=174, flags=0x101, extends=0x69) 25: System.Security.Cryptography.Oid (flist=420, mlist=174, flags=0x100101, extends=0x5) 26: System.Security.Cryptography.CAPI (flist=423, mlist=176, flags=0x100180, extends=0x5) 27: System.Security.Cryptography.AsnEncodedData (flist=423, mlist=178, flags=0x100101, extends=0x5) 28: System.Security.Cryptography.X509Certificates.X509Utils (flist=424, mlist=179, flags=0x100100, extends=0x5) 29: System.Security.Cryptography.X509Certificates.PublicKey (flist=424, mlist=181, flags=0x100101, extends=0x5) 30: System.Security.Cryptography.X509Certificates.X509Certificate2 (flist=429, mlist=188, flags=0x102101, extends=0x51) 31: System.Security.Cryptography.X509Certificates.X509Certificate2Impl (flist=431, mlist=204, flags=0x100080, extends=0x55) 32: System.Security.Cryptography.X509Certificates.X509CertificateCollection (flist=431, mlist=209, flags=0x102101, extends=0x6d) 33: System.Security.Cryptography.X509Certificates.X509CertificateCollection/X509CertificateEnumerator (flist=431, mlist=212, flags=0x100102, extends=0x5) 34: System.Security.Cryptography.X509Certificates.X509Helper2 (flist=432, mlist=217, flags=0x100180, extends=0x5) 35: <PrivateImplementationDetails> (flist=432, mlist=218, flags=0x100, extends=0x5) 36: <PrivateImplementationDetails>/__StaticArrayInitTypeSize=9 (flist=433, mlist=219, flags=0x113, extends=0x25) ``` Some of the above types from System.dll implemented ObjCRuntime.INativeObject (from System.dll), which our linker detected as implementing ObjCRuntime.INativeObject (from Xamarin.iOS.dll), so these types were treated as custom NSObject subclasses, and the MarkNSObjects linker step would mark them (which would in turn cause all the other types in the list to be marked). With that change, these types now implement ObjCRuntimeInternal.INativeObject, and the linker does not treat them as custom NSObject subclasses anymore. I think the new behavior is correct: these types do not actually inherit from the real NSObject/INativeObject, so the linker should not treat them as such. This may run into different bugs because the linker might now remove more stuff than before, but that would be a different issue. This means that the fix is to modify these tests accordingly. https://bugzilla.xamarin.com/show_bug.cgi?id=56307 https://bugzilla.xamarin.com/show_bug.cgi?id=56308 * Bump mono to latest. * Fix merge conflict that was missed * [mtouch] Renumber new error which clashes with an existing error number in master.
2017-05-29 19:39:29 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to inline code from the application. The assembly causing the issue is named in the error message. In order to fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[Do not merge yet] Update to mono 2017-04 branch (#1960) * Update to mono 2017-04 branch * Patch from Zoltan to fix build error with CppSharp.CppParser.dll * Include new linker files in Makefile, based on mareks commit * [msbuild] Fix running bgen for Xamarin.Mac. bgen must be executed with the system mono, not bmac-mobile-mono, and without the MONO_PATH variable set. * System.Data tests should act as if they are running on mobile profile * Add --runtime=mobile to mono flags in Modern * Move runtime launcher options up * System.Data tests should use Mobile profile (mac fix) * Bump 2017-04 to pick up AOT and assembly resolution fixes * Build fixes for netstandard.dll and System.Drawing.Primitives.dll The new handling went in with https://github.com/mono/mono/pull/4501. I also noticed that WatchOS was missing a target for System.Drawing.Primitives.dll, so I added that. * Add netstandard.dll to 2.1/Facades and System.Drawing.Primitives.dll to WatchOS * Fix 2.1/Facades/netstandard.dll build * Fix the netstandard targets * Bump mono to latest 2017-04 commit * [xharness] Fix adding defines to csproj by correctly detecting existing defines. * Bump mono to latest 2017-04 commit * [mtouch] Update csproj with new files. * [mtouch] Improve reporting for MarkExceptions from the linker. * Bump mono to latest 2017-04 commit * Bump mono to pick up latest 2017-04 branch commit (Fixes #55436) Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=55436 * Add a missing Makefile dependency * Chris Hamons patch to apply --runtime=mobile as necessary at AOT time (It is currently being applied for some configurations at runtime only) * Bump system mono * Bump mono for assembly loader changes * Bump system mono * Update assemblies list as some where moved to facades https://github.com/mono/mono/commit/6ca5ec442b494bed8cfb44258c1c73c091ba3122 https://github.com/mono/mono/commit/c38e4d9220b16488e6f8f9e1f05aed4a8af16e62 * Bump mono to latest 2017-04 commit * Add another new facade * Bump mono to tip of 2017-04. * Bump mono to tip of 2017-04. * [tests][mtouch] Adjust tests to cope with fewer assemblies being included in linked apps. Fixes #56307 and #56308. System.dll is now completely linked away unless the app actually uses any System.dll API. This is the change that caused this to change: https://github.com/mono/mono/commit/4960d5d2a28a08476ee4239e1746f04afce41c13 Previously the following types would always be kept by the linker: ``` $ monodis --typedef System.dll Typedef Table 1: (null) (flist=1, mlist=1, flags=0x0, extends=0x0) 2: ObjCRuntime.INativeObject (flist=1, mlist=1, flags=0xa0, extends=0x0) 3: Mono.Net.CFObject (flist=1, mlist=2, flags=0x100000, extends=0x5) 4: Mono.Net.CFArray (flist=4, mlist=19, flags=0x100, extends=0xc) 5: Mono.Net.CFNumber (flist=5, mlist=32, flags=0x100100, extends=0xc) 6: Mono.Net.CFRange (flist=5, mlist=41, flags=0x100108, extends=0x25) 7: Mono.Net.CFString (flist=7, mlist=42, flags=0x100100, extends=0xc) 8: Mono.Net.CFData (flist=8, mlist=53, flags=0x100100, extends=0xc) 9: Mono.Net.CFDictionary (flist=8, mlist=63, flags=0x0, extends=0xc) 10: Mono.Net.CFMutableDictionary (flist=10, mlist=75, flags=0x100100, extends=0x24) 11: Mono.Net.CFUrl (flist=10, mlist=80, flags=0x100100, extends=0xc) 12: Mono.Net.CFRunLoop (flist=10, mlist=83, flags=0x100100, extends=0xc) 13: Mono.Net.CFBoolean (flist=10, mlist=94, flags=0x100, extends=0x5) 14: Mono.AppleTls.SecCertificate (flist=13, mlist=106, flags=0x100100, extends=0x5) 15: Mono.AppleTls.SecIdentity (flist=14, mlist=122, flags=0x100, extends=0x5) 16: Mono.AppleTls.SecIdentity/ImportOptions (flist=19, mlist=134, flags=0x100105, extends=0x5) 17: Mono.AppleTls.SecKey (flist=19, mlist=134, flags=0x100100, extends=0x5) 18: Mono.AppleTls.SecStatusCode (flist=21, mlist=141, flags=0x100, extends=0x69) 19: Mono.AppleTls.SecTrustResult (flist=395, mlist=141, flags=0x100, extends=0x69) 20: Mono.AppleTls.SecImportExport (flist=404, mlist=141, flags=0x100100, extends=0x5) 21: Mono.AppleTls.SecImportExport/<>c (flist=404, mlist=144, flags=0x102103, extends=0x5) 22: Mono.AppleTls.SecPolicy (flist=406, mlist=147, flags=0x100100, extends=0x5) 23: Mono.AppleTls.SecTrust (flist=407, mlist=154, flags=0x100100, extends=0x5) 24: System.Security.Cryptography.OidGroup (flist=408, mlist=174, flags=0x101, extends=0x69) 25: System.Security.Cryptography.Oid (flist=420, mlist=174, flags=0x100101, extends=0x5) 26: System.Security.Cryptography.CAPI (flist=423, mlist=176, flags=0x100180, extends=0x5) 27: System.Security.Cryptography.AsnEncodedData (flist=423, mlist=178, flags=0x100101, extends=0x5) 28: System.Security.Cryptography.X509Certificates.X509Utils (flist=424, mlist=179, flags=0x100100, extends=0x5) 29: System.Security.Cryptography.X509Certificates.PublicKey (flist=424, mlist=181, flags=0x100101, extends=0x5) 30: System.Security.Cryptography.X509Certificates.X509Certificate2 (flist=429, mlist=188, flags=0x102101, extends=0x51) 31: System.Security.Cryptography.X509Certificates.X509Certificate2Impl (flist=431, mlist=204, flags=0x100080, extends=0x55) 32: System.Security.Cryptography.X509Certificates.X509CertificateCollection (flist=431, mlist=209, flags=0x102101, extends=0x6d) 33: System.Security.Cryptography.X509Certificates.X509CertificateCollection/X509CertificateEnumerator (flist=431, mlist=212, flags=0x100102, extends=0x5) 34: System.Security.Cryptography.X509Certificates.X509Helper2 (flist=432, mlist=217, flags=0x100180, extends=0x5) 35: <PrivateImplementationDetails> (flist=432, mlist=218, flags=0x100, extends=0x5) 36: <PrivateImplementationDetails>/__StaticArrayInitTypeSize=9 (flist=433, mlist=219, flags=0x113, extends=0x25) ``` Some of the above types from System.dll implemented ObjCRuntime.INativeObject (from System.dll), which our linker detected as implementing ObjCRuntime.INativeObject (from Xamarin.iOS.dll), so these types were treated as custom NSObject subclasses, and the MarkNSObjects linker step would mark them (which would in turn cause all the other types in the list to be marked). With that change, these types now implement ObjCRuntimeInternal.INativeObject, and the linker does not treat them as custom NSObject subclasses anymore. I think the new behavior is correct: these types do not actually inherit from the real NSObject/INativeObject, so the linker should not treat them as such. This may run into different bugs because the linker might now remove more stuff than before, but that would be a different issue. This means that the fix is to modify these tests accordingly. https://bugzilla.xamarin.com/show_bug.cgi?id=56307 https://bugzilla.xamarin.com/show_bug.cgi?id=56308 * Bump mono to latest. * Fix merge conflict that was missed * [mtouch] Renumber new error which clashes with an existing error number in master.
2017-05-29 19:39:29 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<!-- MT21xx: more linker errors -->
[Do not merge yet] Update to mono 2017-04 branch (#1960) * Update to mono 2017-04 branch * Patch from Zoltan to fix build error with CppSharp.CppParser.dll * Include new linker files in Makefile, based on mareks commit * [msbuild] Fix running bgen for Xamarin.Mac. bgen must be executed with the system mono, not bmac-mobile-mono, and without the MONO_PATH variable set. * System.Data tests should act as if they are running on mobile profile * Add --runtime=mobile to mono flags in Modern * Move runtime launcher options up * System.Data tests should use Mobile profile (mac fix) * Bump 2017-04 to pick up AOT and assembly resolution fixes * Build fixes for netstandard.dll and System.Drawing.Primitives.dll The new handling went in with https://github.com/mono/mono/pull/4501. I also noticed that WatchOS was missing a target for System.Drawing.Primitives.dll, so I added that. * Add netstandard.dll to 2.1/Facades and System.Drawing.Primitives.dll to WatchOS * Fix 2.1/Facades/netstandard.dll build * Fix the netstandard targets * Bump mono to latest 2017-04 commit * [xharness] Fix adding defines to csproj by correctly detecting existing defines. * Bump mono to latest 2017-04 commit * [mtouch] Update csproj with new files. * [mtouch] Improve reporting for MarkExceptions from the linker. * Bump mono to latest 2017-04 commit * Bump mono to pick up latest 2017-04 branch commit (Fixes #55436) Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=55436 * Add a missing Makefile dependency * Chris Hamons patch to apply --runtime=mobile as necessary at AOT time (It is currently being applied for some configurations at runtime only) * Bump system mono * Bump mono for assembly loader changes * Bump system mono * Update assemblies list as some where moved to facades https://github.com/mono/mono/commit/6ca5ec442b494bed8cfb44258c1c73c091ba3122 https://github.com/mono/mono/commit/c38e4d9220b16488e6f8f9e1f05aed4a8af16e62 * Bump mono to latest 2017-04 commit * Add another new facade * Bump mono to tip of 2017-04. * Bump mono to tip of 2017-04. * [tests][mtouch] Adjust tests to cope with fewer assemblies being included in linked apps. Fixes #56307 and #56308. System.dll is now completely linked away unless the app actually uses any System.dll API. This is the change that caused this to change: https://github.com/mono/mono/commit/4960d5d2a28a08476ee4239e1746f04afce41c13 Previously the following types would always be kept by the linker: ``` $ monodis --typedef System.dll Typedef Table 1: (null) (flist=1, mlist=1, flags=0x0, extends=0x0) 2: ObjCRuntime.INativeObject (flist=1, mlist=1, flags=0xa0, extends=0x0) 3: Mono.Net.CFObject (flist=1, mlist=2, flags=0x100000, extends=0x5) 4: Mono.Net.CFArray (flist=4, mlist=19, flags=0x100, extends=0xc) 5: Mono.Net.CFNumber (flist=5, mlist=32, flags=0x100100, extends=0xc) 6: Mono.Net.CFRange (flist=5, mlist=41, flags=0x100108, extends=0x25) 7: Mono.Net.CFString (flist=7, mlist=42, flags=0x100100, extends=0xc) 8: Mono.Net.CFData (flist=8, mlist=53, flags=0x100100, extends=0xc) 9: Mono.Net.CFDictionary (flist=8, mlist=63, flags=0x0, extends=0xc) 10: Mono.Net.CFMutableDictionary (flist=10, mlist=75, flags=0x100100, extends=0x24) 11: Mono.Net.CFUrl (flist=10, mlist=80, flags=0x100100, extends=0xc) 12: Mono.Net.CFRunLoop (flist=10, mlist=83, flags=0x100100, extends=0xc) 13: Mono.Net.CFBoolean (flist=10, mlist=94, flags=0x100, extends=0x5) 14: Mono.AppleTls.SecCertificate (flist=13, mlist=106, flags=0x100100, extends=0x5) 15: Mono.AppleTls.SecIdentity (flist=14, mlist=122, flags=0x100, extends=0x5) 16: Mono.AppleTls.SecIdentity/ImportOptions (flist=19, mlist=134, flags=0x100105, extends=0x5) 17: Mono.AppleTls.SecKey (flist=19, mlist=134, flags=0x100100, extends=0x5) 18: Mono.AppleTls.SecStatusCode (flist=21, mlist=141, flags=0x100, extends=0x69) 19: Mono.AppleTls.SecTrustResult (flist=395, mlist=141, flags=0x100, extends=0x69) 20: Mono.AppleTls.SecImportExport (flist=404, mlist=141, flags=0x100100, extends=0x5) 21: Mono.AppleTls.SecImportExport/<>c (flist=404, mlist=144, flags=0x102103, extends=0x5) 22: Mono.AppleTls.SecPolicy (flist=406, mlist=147, flags=0x100100, extends=0x5) 23: Mono.AppleTls.SecTrust (flist=407, mlist=154, flags=0x100100, extends=0x5) 24: System.Security.Cryptography.OidGroup (flist=408, mlist=174, flags=0x101, extends=0x69) 25: System.Security.Cryptography.Oid (flist=420, mlist=174, flags=0x100101, extends=0x5) 26: System.Security.Cryptography.CAPI (flist=423, mlist=176, flags=0x100180, extends=0x5) 27: System.Security.Cryptography.AsnEncodedData (flist=423, mlist=178, flags=0x100101, extends=0x5) 28: System.Security.Cryptography.X509Certificates.X509Utils (flist=424, mlist=179, flags=0x100100, extends=0x5) 29: System.Security.Cryptography.X509Certificates.PublicKey (flist=424, mlist=181, flags=0x100101, extends=0x5) 30: System.Security.Cryptography.X509Certificates.X509Certificate2 (flist=429, mlist=188, flags=0x102101, extends=0x51) 31: System.Security.Cryptography.X509Certificates.X509Certificate2Impl (flist=431, mlist=204, flags=0x100080, extends=0x55) 32: System.Security.Cryptography.X509Certificates.X509CertificateCollection (flist=431, mlist=209, flags=0x102101, extends=0x6d) 33: System.Security.Cryptography.X509Certificates.X509CertificateCollection/X509CertificateEnumerator (flist=431, mlist=212, flags=0x100102, extends=0x5) 34: System.Security.Cryptography.X509Certificates.X509Helper2 (flist=432, mlist=217, flags=0x100180, extends=0x5) 35: <PrivateImplementationDetails> (flist=432, mlist=218, flags=0x100, extends=0x5) 36: <PrivateImplementationDetails>/__StaticArrayInitTypeSize=9 (flist=433, mlist=219, flags=0x113, extends=0x25) ``` Some of the above types from System.dll implemented ObjCRuntime.INativeObject (from System.dll), which our linker detected as implementing ObjCRuntime.INativeObject (from Xamarin.iOS.dll), so these types were treated as custom NSObject subclasses, and the MarkNSObjects linker step would mark them (which would in turn cause all the other types in the list to be marked). With that change, these types now implement ObjCRuntimeInternal.INativeObject, and the linker does not treat them as custom NSObject subclasses anymore. I think the new behavior is correct: these types do not actually inherit from the real NSObject/INativeObject, so the linker should not treat them as such. This may run into different bugs because the linker might now remove more stuff than before, but that would be a different issue. This means that the fix is to modify these tests accordingly. https://bugzilla.xamarin.com/show_bug.cgi?id=56307 https://bugzilla.xamarin.com/show_bug.cgi?id=56308 * Bump mono to latest. * Fix merge conflict that was missed * [mtouch] Renumber new error which clashes with an existing error number in master.
2017-05-29 19:39:29 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<!--- 2100 used by mmp -->
[Do not merge yet] Update to mono 2017-04 branch (#1960) * Update to mono 2017-04 branch * Patch from Zoltan to fix build error with CppSharp.CppParser.dll * Include new linker files in Makefile, based on mareks commit * [msbuild] Fix running bgen for Xamarin.Mac. bgen must be executed with the system mono, not bmac-mobile-mono, and without the MONO_PATH variable set. * System.Data tests should act as if they are running on mobile profile * Add --runtime=mobile to mono flags in Modern * Move runtime launcher options up * System.Data tests should use Mobile profile (mac fix) * Bump 2017-04 to pick up AOT and assembly resolution fixes * Build fixes for netstandard.dll and System.Drawing.Primitives.dll The new handling went in with https://github.com/mono/mono/pull/4501. I also noticed that WatchOS was missing a target for System.Drawing.Primitives.dll, so I added that. * Add netstandard.dll to 2.1/Facades and System.Drawing.Primitives.dll to WatchOS * Fix 2.1/Facades/netstandard.dll build * Fix the netstandard targets * Bump mono to latest 2017-04 commit * [xharness] Fix adding defines to csproj by correctly detecting existing defines. * Bump mono to latest 2017-04 commit * [mtouch] Update csproj with new files. * [mtouch] Improve reporting for MarkExceptions from the linker. * Bump mono to latest 2017-04 commit * Bump mono to pick up latest 2017-04 branch commit (Fixes #55436) Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=55436 * Add a missing Makefile dependency * Chris Hamons patch to apply --runtime=mobile as necessary at AOT time (It is currently being applied for some configurations at runtime only) * Bump system mono * Bump mono for assembly loader changes * Bump system mono * Update assemblies list as some where moved to facades https://github.com/mono/mono/commit/6ca5ec442b494bed8cfb44258c1c73c091ba3122 https://github.com/mono/mono/commit/c38e4d9220b16488e6f8f9e1f05aed4a8af16e62 * Bump mono to latest 2017-04 commit * Add another new facade * Bump mono to tip of 2017-04. * Bump mono to tip of 2017-04. * [tests][mtouch] Adjust tests to cope with fewer assemblies being included in linked apps. Fixes #56307 and #56308. System.dll is now completely linked away unless the app actually uses any System.dll API. This is the change that caused this to change: https://github.com/mono/mono/commit/4960d5d2a28a08476ee4239e1746f04afce41c13 Previously the following types would always be kept by the linker: ``` $ monodis --typedef System.dll Typedef Table 1: (null) (flist=1, mlist=1, flags=0x0, extends=0x0) 2: ObjCRuntime.INativeObject (flist=1, mlist=1, flags=0xa0, extends=0x0) 3: Mono.Net.CFObject (flist=1, mlist=2, flags=0x100000, extends=0x5) 4: Mono.Net.CFArray (flist=4, mlist=19, flags=0x100, extends=0xc) 5: Mono.Net.CFNumber (flist=5, mlist=32, flags=0x100100, extends=0xc) 6: Mono.Net.CFRange (flist=5, mlist=41, flags=0x100108, extends=0x25) 7: Mono.Net.CFString (flist=7, mlist=42, flags=0x100100, extends=0xc) 8: Mono.Net.CFData (flist=8, mlist=53, flags=0x100100, extends=0xc) 9: Mono.Net.CFDictionary (flist=8, mlist=63, flags=0x0, extends=0xc) 10: Mono.Net.CFMutableDictionary (flist=10, mlist=75, flags=0x100100, extends=0x24) 11: Mono.Net.CFUrl (flist=10, mlist=80, flags=0x100100, extends=0xc) 12: Mono.Net.CFRunLoop (flist=10, mlist=83, flags=0x100100, extends=0xc) 13: Mono.Net.CFBoolean (flist=10, mlist=94, flags=0x100, extends=0x5) 14: Mono.AppleTls.SecCertificate (flist=13, mlist=106, flags=0x100100, extends=0x5) 15: Mono.AppleTls.SecIdentity (flist=14, mlist=122, flags=0x100, extends=0x5) 16: Mono.AppleTls.SecIdentity/ImportOptions (flist=19, mlist=134, flags=0x100105, extends=0x5) 17: Mono.AppleTls.SecKey (flist=19, mlist=134, flags=0x100100, extends=0x5) 18: Mono.AppleTls.SecStatusCode (flist=21, mlist=141, flags=0x100, extends=0x69) 19: Mono.AppleTls.SecTrustResult (flist=395, mlist=141, flags=0x100, extends=0x69) 20: Mono.AppleTls.SecImportExport (flist=404, mlist=141, flags=0x100100, extends=0x5) 21: Mono.AppleTls.SecImportExport/<>c (flist=404, mlist=144, flags=0x102103, extends=0x5) 22: Mono.AppleTls.SecPolicy (flist=406, mlist=147, flags=0x100100, extends=0x5) 23: Mono.AppleTls.SecTrust (flist=407, mlist=154, flags=0x100100, extends=0x5) 24: System.Security.Cryptography.OidGroup (flist=408, mlist=174, flags=0x101, extends=0x69) 25: System.Security.Cryptography.Oid (flist=420, mlist=174, flags=0x100101, extends=0x5) 26: System.Security.Cryptography.CAPI (flist=423, mlist=176, flags=0x100180, extends=0x5) 27: System.Security.Cryptography.AsnEncodedData (flist=423, mlist=178, flags=0x100101, extends=0x5) 28: System.Security.Cryptography.X509Certificates.X509Utils (flist=424, mlist=179, flags=0x100100, extends=0x5) 29: System.Security.Cryptography.X509Certificates.PublicKey (flist=424, mlist=181, flags=0x100101, extends=0x5) 30: System.Security.Cryptography.X509Certificates.X509Certificate2 (flist=429, mlist=188, flags=0x102101, extends=0x51) 31: System.Security.Cryptography.X509Certificates.X509Certificate2Impl (flist=431, mlist=204, flags=0x100080, extends=0x55) 32: System.Security.Cryptography.X509Certificates.X509CertificateCollection (flist=431, mlist=209, flags=0x102101, extends=0x6d) 33: System.Security.Cryptography.X509Certificates.X509CertificateCollection/X509CertificateEnumerator (flist=431, mlist=212, flags=0x100102, extends=0x5) 34: System.Security.Cryptography.X509Certificates.X509Helper2 (flist=432, mlist=217, flags=0x100180, extends=0x5) 35: <PrivateImplementationDetails> (flist=432, mlist=218, flags=0x100, extends=0x5) 36: <PrivateImplementationDetails>/__StaticArrayInitTypeSize=9 (flist=433, mlist=219, flags=0x113, extends=0x25) ``` Some of the above types from System.dll implemented ObjCRuntime.INativeObject (from System.dll), which our linker detected as implementing ObjCRuntime.INativeObject (from Xamarin.iOS.dll), so these types were treated as custom NSObject subclasses, and the MarkNSObjects linker step would mark them (which would in turn cause all the other types in the list to be marked). With that change, these types now implement ObjCRuntimeInternal.INativeObject, and the linker does not treat them as custom NSObject subclasses anymore. I think the new behavior is correct: these types do not actually inherit from the real NSObject/INativeObject, so the linker should not treat them as such. This may run into different bugs because the linker might now remove more stuff than before, but that would be a different issue. This means that the fix is to modify these tests accordingly. https://bugzilla.xamarin.com/show_bug.cgi?id=56307 https://bugzilla.xamarin.com/show_bug.cgi?id=56308 * Bump mono to latest. * Fix merge conflict that was missed * [mtouch] Renumber new error which clashes with an existing error number in master.
2017-05-29 19:39:29 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2100" />
[Do not merge yet] Update to mono 2017-04 branch (#1960) * Update to mono 2017-04 branch * Patch from Zoltan to fix build error with CppSharp.CppParser.dll * Include new linker files in Makefile, based on mareks commit * [msbuild] Fix running bgen for Xamarin.Mac. bgen must be executed with the system mono, not bmac-mobile-mono, and without the MONO_PATH variable set. * System.Data tests should act as if they are running on mobile profile * Add --runtime=mobile to mono flags in Modern * Move runtime launcher options up * System.Data tests should use Mobile profile (mac fix) * Bump 2017-04 to pick up AOT and assembly resolution fixes * Build fixes for netstandard.dll and System.Drawing.Primitives.dll The new handling went in with https://github.com/mono/mono/pull/4501. I also noticed that WatchOS was missing a target for System.Drawing.Primitives.dll, so I added that. * Add netstandard.dll to 2.1/Facades and System.Drawing.Primitives.dll to WatchOS * Fix 2.1/Facades/netstandard.dll build * Fix the netstandard targets * Bump mono to latest 2017-04 commit * [xharness] Fix adding defines to csproj by correctly detecting existing defines. * Bump mono to latest 2017-04 commit * [mtouch] Update csproj with new files. * [mtouch] Improve reporting for MarkExceptions from the linker. * Bump mono to latest 2017-04 commit * Bump mono to pick up latest 2017-04 branch commit (Fixes #55436) Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=55436 * Add a missing Makefile dependency * Chris Hamons patch to apply --runtime=mobile as necessary at AOT time (It is currently being applied for some configurations at runtime only) * Bump system mono * Bump mono for assembly loader changes * Bump system mono * Update assemblies list as some where moved to facades https://github.com/mono/mono/commit/6ca5ec442b494bed8cfb44258c1c73c091ba3122 https://github.com/mono/mono/commit/c38e4d9220b16488e6f8f9e1f05aed4a8af16e62 * Bump mono to latest 2017-04 commit * Add another new facade * Bump mono to tip of 2017-04. * Bump mono to tip of 2017-04. * [tests][mtouch] Adjust tests to cope with fewer assemblies being included in linked apps. Fixes #56307 and #56308. System.dll is now completely linked away unless the app actually uses any System.dll API. This is the change that caused this to change: https://github.com/mono/mono/commit/4960d5d2a28a08476ee4239e1746f04afce41c13 Previously the following types would always be kept by the linker: ``` $ monodis --typedef System.dll Typedef Table 1: (null) (flist=1, mlist=1, flags=0x0, extends=0x0) 2: ObjCRuntime.INativeObject (flist=1, mlist=1, flags=0xa0, extends=0x0) 3: Mono.Net.CFObject (flist=1, mlist=2, flags=0x100000, extends=0x5) 4: Mono.Net.CFArray (flist=4, mlist=19, flags=0x100, extends=0xc) 5: Mono.Net.CFNumber (flist=5, mlist=32, flags=0x100100, extends=0xc) 6: Mono.Net.CFRange (flist=5, mlist=41, flags=0x100108, extends=0x25) 7: Mono.Net.CFString (flist=7, mlist=42, flags=0x100100, extends=0xc) 8: Mono.Net.CFData (flist=8, mlist=53, flags=0x100100, extends=0xc) 9: Mono.Net.CFDictionary (flist=8, mlist=63, flags=0x0, extends=0xc) 10: Mono.Net.CFMutableDictionary (flist=10, mlist=75, flags=0x100100, extends=0x24) 11: Mono.Net.CFUrl (flist=10, mlist=80, flags=0x100100, extends=0xc) 12: Mono.Net.CFRunLoop (flist=10, mlist=83, flags=0x100100, extends=0xc) 13: Mono.Net.CFBoolean (flist=10, mlist=94, flags=0x100, extends=0x5) 14: Mono.AppleTls.SecCertificate (flist=13, mlist=106, flags=0x100100, extends=0x5) 15: Mono.AppleTls.SecIdentity (flist=14, mlist=122, flags=0x100, extends=0x5) 16: Mono.AppleTls.SecIdentity/ImportOptions (flist=19, mlist=134, flags=0x100105, extends=0x5) 17: Mono.AppleTls.SecKey (flist=19, mlist=134, flags=0x100100, extends=0x5) 18: Mono.AppleTls.SecStatusCode (flist=21, mlist=141, flags=0x100, extends=0x69) 19: Mono.AppleTls.SecTrustResult (flist=395, mlist=141, flags=0x100, extends=0x69) 20: Mono.AppleTls.SecImportExport (flist=404, mlist=141, flags=0x100100, extends=0x5) 21: Mono.AppleTls.SecImportExport/<>c (flist=404, mlist=144, flags=0x102103, extends=0x5) 22: Mono.AppleTls.SecPolicy (flist=406, mlist=147, flags=0x100100, extends=0x5) 23: Mono.AppleTls.SecTrust (flist=407, mlist=154, flags=0x100100, extends=0x5) 24: System.Security.Cryptography.OidGroup (flist=408, mlist=174, flags=0x101, extends=0x69) 25: System.Security.Cryptography.Oid (flist=420, mlist=174, flags=0x100101, extends=0x5) 26: System.Security.Cryptography.CAPI (flist=423, mlist=176, flags=0x100180, extends=0x5) 27: System.Security.Cryptography.AsnEncodedData (flist=423, mlist=178, flags=0x100101, extends=0x5) 28: System.Security.Cryptography.X509Certificates.X509Utils (flist=424, mlist=179, flags=0x100100, extends=0x5) 29: System.Security.Cryptography.X509Certificates.PublicKey (flist=424, mlist=181, flags=0x100101, extends=0x5) 30: System.Security.Cryptography.X509Certificates.X509Certificate2 (flist=429, mlist=188, flags=0x102101, extends=0x51) 31: System.Security.Cryptography.X509Certificates.X509Certificate2Impl (flist=431, mlist=204, flags=0x100080, extends=0x55) 32: System.Security.Cryptography.X509Certificates.X509CertificateCollection (flist=431, mlist=209, flags=0x102101, extends=0x6d) 33: System.Security.Cryptography.X509Certificates.X509CertificateCollection/X509CertificateEnumerator (flist=431, mlist=212, flags=0x100102, extends=0x5) 34: System.Security.Cryptography.X509Certificates.X509Helper2 (flist=432, mlist=217, flags=0x100180, extends=0x5) 35: <PrivateImplementationDetails> (flist=432, mlist=218, flags=0x100, extends=0x5) 36: <PrivateImplementationDetails>/__StaticArrayInitTypeSize=9 (flist=433, mlist=219, flags=0x113, extends=0x25) ``` Some of the above types from System.dll implemented ObjCRuntime.INativeObject (from System.dll), which our linker detected as implementing ObjCRuntime.INativeObject (from Xamarin.iOS.dll), so these types were treated as custom NSObject subclasses, and the MarkNSObjects linker step would mark them (which would in turn cause all the other types in the list to be marked). With that change, these types now implement ObjCRuntimeInternal.INativeObject, and the linker does not treat them as custom NSObject subclasses anymore. I think the new behavior is correct: these types do not actually inherit from the real NSObject/INativeObject, so the linker should not treat them as such. This may run into different bugs because the linker might now remove more stuff than before, but that would be a different issue. This means that the fix is to modify these tests accordingly. https://bugzilla.xamarin.com/show_bug.cgi?id=56307 https://bugzilla.xamarin.com/show_bug.cgi?id=56308 * Bump mono to latest. * Fix merge conflict that was missed * [mtouch] Renumber new error which clashes with an existing error number in master.
2017-05-29 19:39:29 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2100: Smart Enum Conversion Preserver failed processing `...`.
[mtouch][mmp] Add better diagnose for bugs #59570 and #58063 (#2745) Bug #59570 was a dupe of #58063 but was harder (than it should be) to diagnose because the error did not point out which assembly had the issue (requiring a whole, large, customer solution to confirm). This adds a new MT2103 error which points to the assembly that could not be read. E.g. VSfM will now show > Error MT2103: Error processing assembly 'Shim, Version=2.0.1.0, Culture=neutral, PublicKeyToken=c55ec16d10c4b366': System.NullReferenceException: Object reference not set to an instance of an object (MT2103) (...) [1] https://bugzilla.xamarin.com/show_bug.cgi?id=59570 [2] https://bugzilla.xamarin.com/show_bug.cgi?id=58063
2017-09-22 03:22:12 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to mark the conversion methods for smart enums from the application. The assembly causing the issue is named in the error message. In order to fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[mtouch][mmp] Add better diagnose for bugs #59570 and #58063 (#2745) Bug #59570 was a dupe of #58063 but was harder (than it should be) to diagnose because the error did not point out which assembly had the issue (requiring a whole, large, customer solution to confirm). This adds a new MT2103 error which points to the assembly that could not be read. E.g. VSfM will now show > Error MT2103: Error processing assembly 'Shim, Version=2.0.1.0, Culture=neutral, PublicKeyToken=c55ec16d10c4b366': System.NullReferenceException: Object reference not set to an instance of an object (MT2103) (...) [1] https://bugzilla.xamarin.com/show_bug.cgi?id=59570 [2] https://bugzilla.xamarin.com/show_bug.cgi?id=58063
2017-09-22 03:22:12 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2101" />
[mtouch][mmp] Add better diagnose for bugs #59570 and #58063 (#2745) Bug #59570 was a dupe of #58063 but was harder (than it should be) to diagnose because the error did not point out which assembly had the issue (requiring a whole, large, customer solution to confirm). This adds a new MT2103 error which points to the assembly that could not be read. E.g. VSfM will now show > Error MT2103: Error processing assembly 'Shim, Version=2.0.1.0, Culture=neutral, PublicKeyToken=c55ec16d10c4b366': System.NullReferenceException: Object reference not set to an instance of an object (MT2103) (...) [1] https://bugzilla.xamarin.com/show_bug.cgi?id=59570 [2] https://bugzilla.xamarin.com/show_bug.cgi?id=58063
2017-09-22 03:22:12 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2101: Can't resolve the reference '\*', referenced from the method '\*' in '*'.
[mtouch][mmp] Add better diagnose for bugs #59570 and #58063 (#2745) Bug #59570 was a dupe of #58063 but was harder (than it should be) to diagnose because the error did not point out which assembly had the issue (requiring a whole, large, customer solution to confirm). This adds a new MT2103 error which points to the assembly that could not be read. E.g. VSfM will now show > Error MT2103: Error processing assembly 'Shim, Version=2.0.1.0, Culture=neutral, PublicKeyToken=c55ec16d10c4b366': System.NullReferenceException: Object reference not set to an instance of an object (MT2103) (...) [1] https://bugzilla.xamarin.com/show_bug.cgi?id=59570 [2] https://bugzilla.xamarin.com/show_bug.cgi?id=58063
2017-09-22 03:22:12 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
An invalid assembly reference was encountered when processing the method mentioned in the error message.
[macos] Error when linking mix-mode assemblies (#2911) - https://bugzilla.xamarin.com/show_bug.cgi?id=58583
2017-11-16 18:18:18 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[macos] Error when linking mix-mode assemblies (#2911) - https://bugzilla.xamarin.com/show_bug.cgi?id=58583
2017-11-16 18:18:18 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2102" />
[mtouch][mmp] Add better diagnose for bugs #59570 and #58063 (#2745) Bug #59570 was a dupe of #58063 but was harder (than it should be) to diagnose because the error did not point out which assembly had the issue (requiring a whole, large, customer solution to confirm). This adds a new MT2103 error which points to the assembly that could not be read. E.g. VSfM will now show > Error MT2103: Error processing assembly 'Shim, Version=2.0.1.0, Culture=neutral, PublicKeyToken=c55ec16d10c4b366': System.NullReferenceException: Object reference not set to an instance of an object (MT2103) (...) [1] https://bugzilla.xamarin.com/show_bug.cgi?id=59570 [2] https://bugzilla.xamarin.com/show_bug.cgi?id=58063
2017-09-22 03:22:12 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2102: Error processing the method '\*' in the assembly '\*': *
Add a BindingImpl attribute and use to to teach the linker look for it to search for optimizable code. (#3299) * [ObjCRuntime] Add a BindingImplAttribute. * [linker] Make ProviderToString an extension method on ICustomAttributeProvider to make it more discoverable. * [generator] Use [BindingImpl] instead of [CompilerGenerated]. The entire diff is big (89MB), so it can't be gisted. However, most of it is either removal of `using System.Runtime.CompilerServices;` or the change from `[CompilerGenerated]` to `[BindingImpl (...)]` like this: https://gist.github.com/rolfbjarne/8bfda3ed37b956d0342a1c1e9b079244 If I remove those parts of the diff, there's nothing significant left: https://gist.github.com/rolfbjarne/4156164d6bdb1376366200394eb8a091 * [linker] Teach the linker about the new [BindingImpl] attribute. In addition to the existing logic where the linker would optimize some [CompilerGenerated] code (sometimes with additional requirements), it will now also optimize all [BindingImpl (Optimizable)] code (without any additional requirements). * [tests] Add tests to make sure [BindingImpl (Optimizable)] works as expected. * [linker] Check for [BindingImpl] before [CompilerGenerated] and stop checking for [CompilerGenerated] in XAMCORE_4_0. Check for [BindingImpl] before checking for [CompilerGenerated], since the former is more common. Also stop checking for [CompilerGenerated] (at least to mean that code is optimizable) in our next non-compatible evolutionary leap (XAMCORE_4_0): * [introspection] Impl a better typo check.
2018-01-26 20:38:23 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Something unexpected occured when trying to mark the method mentioned in the error message.
Add a BindingImpl attribute and use to to teach the linker look for it to search for optimizable code. (#3299) * [ObjCRuntime] Add a BindingImplAttribute. * [linker] Make ProviderToString an extension method on ICustomAttributeProvider to make it more discoverable. * [generator] Use [BindingImpl] instead of [CompilerGenerated]. The entire diff is big (89MB), so it can't be gisted. However, most of it is either removal of `using System.Runtime.CompilerServices;` or the change from `[CompilerGenerated]` to `[BindingImpl (...)]` like this: https://gist.github.com/rolfbjarne/8bfda3ed37b956d0342a1c1e9b079244 If I remove those parts of the diff, there's nothing significant left: https://gist.github.com/rolfbjarne/4156164d6bdb1376366200394eb8a091 * [linker] Teach the linker about the new [BindingImpl] attribute. In addition to the existing logic where the linker would optimize some [CompilerGenerated] code (sometimes with additional requirements), it will now also optimize all [BindingImpl (Optimizable)] code (without any additional requirements). * [tests] Add tests to make sure [BindingImpl (Optimizable)] works as expected. * [linker] Check for [BindingImpl] before [CompilerGenerated] and stop checking for [CompilerGenerated] in XAMCORE_4_0. Check for [BindingImpl] before checking for [CompilerGenerated], since the former is more common. Also stop checking for [CompilerGenerated] (at least to mean that code is optimizable) in our next non-compatible evolutionary leap (XAMCORE_4_0): * [introspection] Impl a better typo check.
2018-01-26 20:38:23 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
Optimize calls to BlockLiteral.SetupBlock to inject the block signature. (#3391) * [linker] Optimize calls to BlockLiteral.SetupBlock to inject the block signature. Optimize calls to BlockLiteral.SetupBlock[Unsafe] to calculate the block signature at build time, and inject it into the call site. This makes block invocations 10-15x faster (I've added tests that asserts at least an 8x increase). It's also required in order to be able to remove the dynamic registrar code in the future (since calculating the block signature at runtime requires the dynamic registrar). * [mtouch/mmp] Add support for reporting errors/warnings that point to the code line causing the error/warning. Add support for reporting errors/warnings that point to the code line causing the error/warning by adding ErrorHelper overloads that take the exact instruction to report (previously we defaulted to the first line/instruction in a method). * [tests] Add support for asserting filename/linenumber in warning messages. * Make all methods that manually create BlockLiterals optimizable. * [tests] Create a BaseOptimizeGeneratedCodeTest test that's included in both XI's and XM's link all test. * [tests] Add link all test (for both XI and XM) to test the BlockLiteral.SetupBlock optimization. * [tests] Add mtouch/mmp tests for the BlockLiteral.SetupBlock optimization. * [tests][linker] Make the base test class abstract, so tests in the base class aren't executed twice. * [tests][linker] Don't execute linkall-only tests in linksdk. The optimization tests only apply when the test assembly is linked, and that only happens in linkall, so exclude those tests in linksdk. * [tests][mmptest] Update test according to mmp changes. Fixes these test failures: 1) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("inline-runtime-arch") The warning 'MM0132: Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' 2) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("foo") The warning 'MM0132: Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' * [tests][linker] Fix typo. Fixes this test failure: 1) SetupBlock_CustomDelegate (Linker.Shared.BaseOptimizeGeneratedCodeTest.SetupBlock_CustomDelegate) Counter Expected: 1 But was: 2 * [registrar] Minor adjustment to error message to match previous (and better) behavior. Fixes this test failure: 1) Failed : Xamarin.Registrar.GenericType_WithInvalidParameterTypes The error 'MT4136: The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' was not found in the output: Message #1 did not match: actual: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<Foundation.NSObject>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' expected: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' * [docs] mmp shows MM errors/warnings. * [docs] Improve according to reviews. * [tests] Fix merge failure causing test duplication.
2018-02-06 09:08:15 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2103" />
Optimize calls to BlockLiteral.SetupBlock to inject the block signature. (#3391) * [linker] Optimize calls to BlockLiteral.SetupBlock to inject the block signature. Optimize calls to BlockLiteral.SetupBlock[Unsafe] to calculate the block signature at build time, and inject it into the call site. This makes block invocations 10-15x faster (I've added tests that asserts at least an 8x increase). It's also required in order to be able to remove the dynamic registrar code in the future (since calculating the block signature at runtime requires the dynamic registrar). * [mtouch/mmp] Add support for reporting errors/warnings that point to the code line causing the error/warning. Add support for reporting errors/warnings that point to the code line causing the error/warning by adding ErrorHelper overloads that take the exact instruction to report (previously we defaulted to the first line/instruction in a method). * [tests] Add support for asserting filename/linenumber in warning messages. * Make all methods that manually create BlockLiterals optimizable. * [tests] Create a BaseOptimizeGeneratedCodeTest test that's included in both XI's and XM's link all test. * [tests] Add link all test (for both XI and XM) to test the BlockLiteral.SetupBlock optimization. * [tests] Add mtouch/mmp tests for the BlockLiteral.SetupBlock optimization. * [tests][linker] Make the base test class abstract, so tests in the base class aren't executed twice. * [tests][linker] Don't execute linkall-only tests in linksdk. The optimization tests only apply when the test assembly is linked, and that only happens in linkall, so exclude those tests in linksdk. * [tests][mmptest] Update test according to mmp changes. Fixes these test failures: 1) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("inline-runtime-arch") The warning 'MM0132: Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' 2) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("foo") The warning 'MM0132: Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' * [tests][linker] Fix typo. Fixes this test failure: 1) SetupBlock_CustomDelegate (Linker.Shared.BaseOptimizeGeneratedCodeTest.SetupBlock_CustomDelegate) Counter Expected: 1 But was: 2 * [registrar] Minor adjustment to error message to match previous (and better) behavior. Fixes this test failure: 1) Failed : Xamarin.Registrar.GenericType_WithInvalidParameterTypes The error 'MT4136: The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' was not found in the output: Message #1 did not match: actual: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<Foundation.NSObject>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' expected: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' * [docs] mmp shows MM errors/warnings. * [docs] Improve according to reviews. * [tests] Fix merge failure causing test duplication.
2018-02-06 09:08:15 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT2103: Error processing assembly '\*': *
Optimize calls to BlockLiteral.SetupBlock to inject the block signature. (#3391) * [linker] Optimize calls to BlockLiteral.SetupBlock to inject the block signature. Optimize calls to BlockLiteral.SetupBlock[Unsafe] to calculate the block signature at build time, and inject it into the call site. This makes block invocations 10-15x faster (I've added tests that asserts at least an 8x increase). It's also required in order to be able to remove the dynamic registrar code in the future (since calculating the block signature at runtime requires the dynamic registrar). * [mtouch/mmp] Add support for reporting errors/warnings that point to the code line causing the error/warning. Add support for reporting errors/warnings that point to the code line causing the error/warning by adding ErrorHelper overloads that take the exact instruction to report (previously we defaulted to the first line/instruction in a method). * [tests] Add support for asserting filename/linenumber in warning messages. * Make all methods that manually create BlockLiterals optimizable. * [tests] Create a BaseOptimizeGeneratedCodeTest test that's included in both XI's and XM's link all test. * [tests] Add link all test (for both XI and XM) to test the BlockLiteral.SetupBlock optimization. * [tests] Add mtouch/mmp tests for the BlockLiteral.SetupBlock optimization. * [tests][linker] Make the base test class abstract, so tests in the base class aren't executed twice. * [tests][linker] Don't execute linkall-only tests in linksdk. The optimization tests only apply when the test assembly is linked, and that only happens in linkall, so exclude those tests in linksdk. * [tests][mmptest] Update test according to mmp changes. Fixes these test failures: 1) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("inline-runtime-arch") The warning 'MM0132: Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' 2) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("foo") The warning 'MM0132: Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' * [tests][linker] Fix typo. Fixes this test failure: 1) SetupBlock_CustomDelegate (Linker.Shared.BaseOptimizeGeneratedCodeTest.SetupBlock_CustomDelegate) Counter Expected: 1 But was: 2 * [registrar] Minor adjustment to error message to match previous (and better) behavior. Fixes this test failure: 1) Failed : Xamarin.Registrar.GenericType_WithInvalidParameterTypes The error 'MT4136: The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' was not found in the output: Message #1 did not match: actual: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<Foundation.NSObject>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' expected: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' * [docs] mmp shows MM errors/warnings. * [docs] Improve according to reviews. * [tests] Fix merge failure causing test duplication.
2018-02-06 09:08:15 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
An unexpected error occured when processing an assembly.
Optimize calls to BlockLiteral.SetupBlock to inject the block signature. (#3391) * [linker] Optimize calls to BlockLiteral.SetupBlock to inject the block signature. Optimize calls to BlockLiteral.SetupBlock[Unsafe] to calculate the block signature at build time, and inject it into the call site. This makes block invocations 10-15x faster (I've added tests that asserts at least an 8x increase). It's also required in order to be able to remove the dynamic registrar code in the future (since calculating the block signature at runtime requires the dynamic registrar). * [mtouch/mmp] Add support for reporting errors/warnings that point to the code line causing the error/warning. Add support for reporting errors/warnings that point to the code line causing the error/warning by adding ErrorHelper overloads that take the exact instruction to report (previously we defaulted to the first line/instruction in a method). * [tests] Add support for asserting filename/linenumber in warning messages. * Make all methods that manually create BlockLiterals optimizable. * [tests] Create a BaseOptimizeGeneratedCodeTest test that's included in both XI's and XM's link all test. * [tests] Add link all test (for both XI and XM) to test the BlockLiteral.SetupBlock optimization. * [tests] Add mtouch/mmp tests for the BlockLiteral.SetupBlock optimization. * [tests][linker] Make the base test class abstract, so tests in the base class aren't executed twice. * [tests][linker] Don't execute linkall-only tests in linksdk. The optimization tests only apply when the test assembly is linked, and that only happens in linkall, so exclude those tests in linksdk. * [tests][mmptest] Update test according to mmp changes. Fixes these test failures: 1) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("inline-runtime-arch") The warning 'MM0132: Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' 2) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("foo") The warning 'MM0132: Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' * [tests][linker] Fix typo. Fixes this test failure: 1) SetupBlock_CustomDelegate (Linker.Shared.BaseOptimizeGeneratedCodeTest.SetupBlock_CustomDelegate) Counter Expected: 1 But was: 2 * [registrar] Minor adjustment to error message to match previous (and better) behavior. Fixes this test failure: 1) Failed : Xamarin.Registrar.GenericType_WithInvalidParameterTypes The error 'MT4136: The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' was not found in the output: Message #1 did not match: actual: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<Foundation.NSObject>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' expected: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' * [docs] mmp shows MM errors/warnings. * [docs] Improve according to reviews. * [tests] Fix merge failure causing test duplication.
2018-02-06 09:08:15 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) along with a complete build log with verbosity enabled (i.e. `-v -v -v -v` in the **Additional mtouch arguments**).
[mtouch/mmp] Add support for inlining calls to Runtime.DynamicRegistrarSupported and removal of the dynamic registrar.
2018-02-12 18:59:39 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT2104" />
[documentation] Update according to review.
2018-02-15 18:12:15 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MM2104: Unable to link assembly '{0}' as it is mixed-mode.
[documentation] Update according to review.
2018-02-15 18:12:15 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
Mixed-mode assemblies can not be processed by the linker.
[mtouch/mmp] Add support for inlining calls to Runtime.DynamicRegistrarSupported and removal of the dynamic registrar.
2018-02-12 18:59:39 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
See https://msdn.microsoft.com/en-us/library/x0w2664k.aspx for more information on mixed-mode assemblies.
[mmp] Add stripping of 32-bit dylibs to work with new App Store restrictions (#3387) (#3633) - https://github.com/xamarin/xamarin-macios/issues/3367 - App Store will now fail builds if you add in a 32-bit dylib - If you are a 32-bit app you don't need the 64-bit part of your fat dylib anyway - Add --optimize=-trim-architectures to allow customization of behavior, as not everyone uses app store In addition, while writing tests for this is was noticed that mmp tests did not "really" run Release configuration correctly in most cases. Fixing this turned out to be a bit of a pain, but necessary to correctly test this (and other things). - Turns out that /p:configuration:debug is not sufficient to tell mmp to do the right thing - That, in most projects, sets the DebugSymbols property, which really is what is checked. - However, two of our projects did not have that, so we always did release mmp work. - Removed configuration property for tests and added real "Release" configuration option
2018-03-02 16:33:27 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT3xxx: AOT error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT3xxx AOT
MT30xx AOT (general) errors
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT3001" />
### MT3001: Could not AOT the assembly '*'
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This generally indicates a bug in the AOT compiler. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with a project that can be used to reproduce the error.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[mtouch-errors] Suggest disabling incremental builds to work around MT3001. (#872)
2016-09-22 11:37:02 +03:00
Sometimes it's possible to work around this by disabling incremental builds in the project's iOS Build option (but it's still a bug, so please report it anyways).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT3002" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT3002: AOT restriction: Method '*' must be static since it is decorated with [MonoPInvokeCallback]. See [https://developer.xamarin.com/guides/ios/advanced_topics/limitations/#Reverse_Callbacks](https://developer.xamarin.com/guides/ios/advanced_topics/limitations/#Reverse_Callbacks)
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This error message comes from the AOT compiler.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT3003" />
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT3003: Conflicting --debug and --llvm options. Soft-debugging is disabled.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Debugging is not supported when LLVM is enabled. If you need to debug the app, disable LLVM first.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT3004" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT3004: Could not AOT the assembly '*' because it doesn't exist.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT3005" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT3005: The dependency '\*' of the assembly '\*' was not found. Please review the project's references.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
This typically occurs when an assembly references another version of a platform assembly (usually the .NET 4 version of mscorlib.dll).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This is not supported, and may not build or execute properly (the assembly may use API from the .NET 4 version of mscorlib.dll that the Xamarin.iOS version does not have).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT3006" />
### MT3006: Could not compute a complete dependency map for the project. This will result in slower build times because Xamarin.iOS can't properly detect what needs to be rebuilt (and what does not need to be rebuilt). Please review previous warnings for more details.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
build or execute properly (the assembly may use API from the .NET 4 version of mscorlib.dll that the Xamarin.iOS version does not have).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT3007" />
### MT3007: Debug info files (*.mdb) will not be loaded when llvm is enabled.
<a name="MT3008" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT3008: Bitcode support requires the use of the LLVM AOT backend (--llvm)
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Bitcode support requires the use of the LLVM AOT backend (--llvm).
Either disable Bitcode support or enable LLVM.
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!--- 3009 used by mmp -->
<!--- 3010 used by mmp -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT4xxx: Code generation error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT40xx: Main
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT4xxx code generation
MT40xx main.m
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4001" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4001: The main template could not be expanded to `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
An error occurred when generating `main.m`. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[mtouch] Fix incremental builds when generating P/Invoke wrappers. Fixes #44048. (#788) We need to compile the generated P/Invoke wrappers to a dylib, and link the dylib for the product assembly (Xamarin.WatchOS.dll) with the generated P/Invoke wrappers. Since there might be P/Invokes in any assembly, just link in the P/Invoke wrapper dylib for every assembly. https://bugzilla.xamarin.com/show_bug.cgi?id=44048
2016-09-07 18:22:34 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4002" />
### MT4002: Failed to compile the generated code for P/Invoke methods. Please file a bug report at http://bugzilla.xamarin.com
Failed to compile the generated code for P/Invoke methods. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[mtouch] Fix incremental builds when generating P/Invoke wrappers. Fixes #44048. (#788) We need to compile the generated P/Invoke wrappers to a dylib, and link the dylib for the product assembly (Xamarin.WatchOS.dll) with the generated P/Invoke wrappers. Since there might be P/Invokes in any assembly, just link in the P/Invoke wrapper dylib for every assembly. https://bugzilla.xamarin.com/show_bug.cgi?id=44048
2016-09-07 18:22:34 +03:00
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT41xx: Registrar
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT41xx registrar.m
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4101" />
### MT4101: The registrar cannot build a signature for type `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A type was found in exported API that the runtime doesn't know how to marshal to/from Objective-C.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
If you believe Xamarin.iOS should support the type in question, please file an enhancement request on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT4102" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4102: The registrar found an invalid type `*` in signature for method `*`. Use `*` instead.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This currently only happens with one type: System.DateTime. Use the Objective-C equivalent (NSDate) instead.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4103" />
### MT4103: The registrar found an invalid type `*` in signature for method `*`: The type implements INativeObject, but does not have a constructor that takes two (IntPtr, bool) arguments
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This occurs when the registrar encounter a type in a signature with the mentioned characteristics. The registrar might need to create new instances of the type, and in this case it requires a constructor with the (IntPtr, bool) signature - the first argument (IntPtr) specifies the managed handle, while the second if the caller hands over ownership of the native handle (if this value is false 'retain' will be called on the object).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4104" />
### MT4104: The registrar cannot marshal the return value for type `*` in signature for method `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A type was found in exported API that the runtime doesn't know how to marshal to/from Objective-C.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
If you believe Xamarin.iOS should support the type in question, please file an enhancement request on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT4105" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4105: The registrar cannot marshal the parameter of type `*` in signature for method `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
If you believe Xamarin.iOS should support the type in question, please file an enhancement request on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4106" />
### MT4106: The registrar cannot marshal the return value for structure `*` in signature for method `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A type was found in exported API that the runtime doesn't know how to marshal to/from Objective-C.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
If you believe Xamarin.iOS should support the type in question, please file an enhancement request on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT4107" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4107: The registrar cannot marshal the parameter of type `*` in signature for method `+`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A type was found in exported API that the runtime doesn't know how to marshal to/from Objective-C.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
If you believe Xamarin.iOS should support the type in question, please file an enhancement request on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4108" />
### MT4108: The registrar cannot get the ObjectiveC type for managed type `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A type was found in exported API that the runtime doesn't know how to marshal to/from Objective-C.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
If you believe Xamarin.iOS should support the type in question, please file an enhancement request on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT4109" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4109: Failed to compile the generated registrar code. Please file a bug report at http://bugzilla.xamarin.com
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Failed to compile the generated code for the registrar. The build log will contain the output from the native compiler, explaining why the code isn't compiling.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This is always a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new) with your project or a test case.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4110" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4110: The registrar cannot marshal the out parameter of type `*` in signature for method `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4111" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4111: The registrar cannot build a signature for type `*` in method `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4112" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4112: The registrar found an invalid type `*`. Registering generic types with Objective-C is not supported, and may lead to random behavior and/or crashes (for backwards compatibility with older versions of Xamarin.iOS it is possible to ignore this error by passing `--unsupported--enable-generics-in-registrar` as an additional mtouch argument in the project's iOS Build options page. See [developer.xamarin.com/guides/ios/advanced_topics/registrar](https://developer.xamarin.com/guides/ios/advanced_topics/registrar) for more information).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4113" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4113: The registrar found a generic method: '\*.\*'. Exporting generic methods is not supported, and will lead to random behavior and/or crashes.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4114" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4114: Unexpected error in the registrar for the method '\*.\*' - Please file a bug report at http://bugzilla.xamarin.com
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4116" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4116: Could not register the assembly '*': *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4117" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4117: The registrar found a signature mismatch in the method '*.*' - the selector indicates the method takes * parameters, while the managed method has * parameters.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4118" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4118: Cannot register two managed types ('\*' and '\*') with the same native name ('*').
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4119" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4119: Could not register the selector '\*' of the member '\*.*' because the selector is already registered on a different member.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4120" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4120: The registrar found an unknown field type '\*' in field '\*.*'. Please file a bug report at http://bugzilla.xamarin.com
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This error indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4121" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4121: Cannot use GCC/G++ to compile the generated code from the static registrar when using the Accounts framework (the header files provided by Apple used during the compilation require Clang). Either use Clang (--compiler:clang) or the dynamic registrar (--registrar:dynamic).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4122" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4122: Cannot use the Clang compiler provided in the *.* SDK to compile the generated code from the static registrar when non-ASCII type names ('*') are present in the application. Either use GCC/G++ (--compiler:gcc|g++), the dynamic registrar (--registrar:dynamic) or a newer SDK.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4123" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4123: The type of the variadic parameter in the variadic function '*' must be System.IntPtr.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4124" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4124: Invalid * found on '*'. Please file a bug report at http://bugzilla.xamarin.com
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This error indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4125" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4125: The registrar found an invalid type '\*' in signature for method '\*': The interface must have a Protocol attribute specifying its wrapper type.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4126" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4126: Cannot register two managed protocols ('\*' and '\*') with the same native name ('*').
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4127" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4127: Cannot register more than one interface method for the method '\*' (which is implementing '\*').
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4128" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4128: The registrar found an invalid generic parameter type '\*' in the method '\*'. The generic parameter must have an 'NSObject' constraint.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4129" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4129: The registrar found an invalid generic return type '\*' in the method '\*'. The generic return type must have an 'NSObject' constraint.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4130" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4130: The registrar cannot export static methods in generic classes ('*').
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4131" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4131: The registrar cannot export static properties in generic classes ('\*.\*').
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4132" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4132: The registrar found an invalid generic return type '\*' in the property '\*'. The return type must have an 'NSObject' constraint.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4133" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4133: Cannot construct an instance of the type '*' from Objective-C because the type is generic. [Runtime exception]
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4134" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4134: Your application is using the '*' framework, which isn't included in the iOS SDK you're using to build your app (this framework was introduced in iOS *, while you're building with the iOS * SDK.) Please select a newer SDK in your app's iOS Build options.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4135" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4135: The member '\*.\*' has an Export attribute that doesn't specify a selector. A selector is required.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4136" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4136: The registrar cannot marshal the parameter type '\*' of the parameter '\*' in the method '\*.*'
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<!-- MT4137 is unused -->
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4138" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4138: The registrar cannot marshal the property type '\*' of the property '\*.*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4139" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4139: The registrar cannot marshal the property type '\*' of the property '\*.*'. Properties with the [Connect] attribute must have a property type of NSObject (or a subclass of NSObject).
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4140" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4140: The registrar found a signature mismatch in the method '*.*' - the selector indicates the variadic method takes * parameters, while the managed method has * parameters.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4141" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4141: Cannot register the selector '\*' on the member '\*' because Xamarin.iOS implicitly registers this selector.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This occurs when subclassing a framework type, and trying to implement a 'retain', 'release' or 'dealloc' method:
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
```csharp
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
class MyNSObject : NSObject
{
[Export ("retain")]
new void Retain () {}
[Export ("release")]
new void Release () {}
[Export ("dealloc")]
new void Dealloc () {}
}
```
It is however possible to override these methods if the class isn't the first subclass of the framework type:
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
```csharp
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
class MyNSObject : NSObject
{
}
class MyCustomNSObject : MyNSObject
{
[Export ("retain")]
new void Retain () {}
[Export ("release")]
new void Release () {}
[Export ("dealloc")]
new void Dealloc () {}
}
```
In this case Xamarin.iOS will override `retain`, `release` and `dealloc` on the `MyNSObject` class, and there is no conflict.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4142" />
### MT4142: Failed to register the type '*'.
<a name="MT4143" />
### MT4143: The ObjectiveC class '*' could not be registered, it does not seem to derive from any known ObjectiveC class (including NSObject).
<a name="MT4144" />
[docs] Show bugzilla links (and to the right product) whenever it makes sense. (#1048)
2016-10-28 15:37:16 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4144: Cannot register the method '*' since it does not have an associated trampoline. Please file a bug report at http://bugzilla.xamarin.com.
[docs] Show bugzilla links (and to the right product) whenever it makes sense. (#1048)
2016-10-28 15:37:16 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT4145" />
### MT4145: Invalid enum '*': enums with the [Native] attribute must have a underlying enum type of either 'long' or 'ulong'.
<a name="MT4146" />
### MT4146: The Name parameter of the Registrar attribute on the class '\*' ('\*') contains an invalid character: '\*' (\*).
[mtouch] Add docs and improve MT4146 to be an error if we can detect the generated code won't compile. Fixes #52530. (#1712) https://bugzilla.xamarin.com/show_bug.cgi?id=52530
2017-02-17 18:00:53 +03:00
The name of an Objectice-C class can't contain whitespace, which means that the `Register` attribute on the corresponding managed class can't have a `Name` parameter can't contain whitespace either.
Please verify that the `Register` attribute on the managed class mentioned in the error message does not contain any whitespace.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4147" />
### MT4147: Detected a protocol inheriting from the JSExport protocol while using the dynamic registrar. It is not possible to export protocols to JavaScriptCore dynamically; the static registrar must be used (add '--registrar:static to the additional mtouch arguments in the project's iOS Build options to select the static registrar).
<a name="MT4148" />
### MT4148: The registrar found a generic protocol: '*'. Exporting generic protocols is not supported.
<a name="MT4149" />
### MT4149: Cannot register the method '\*.\*' because the type of the first parameter ('\*') does not match the category type ('\*').
<a name="MT4150" />
### MT4150: Cannot register the type '\*' because the Type property ('\*') in its Category attribute does not inherit from NSObject.
<a name="MT4151" />
### MT4151: Cannot register the type '*' because the Type property in its Category attribute isn't set.
<a name="MT4152" />
### MT4152: Cannot register the type '*' as a category because it implements INativeObject or subclasses NSObject.
<a name="MT4153" />
### MT4153: Cannot register the type '\*' as a category because it's generic.
<a name="MT4154" />
### MT4154: Cannot register the method '\*' as a category method because it's generic.
<a name="MT4155" />
### MT4155: Cannot register the method '\*' with the selector '\*' as a category method on '*' because the Objective-C already has an implementation for this selector.
<a name="MT4156" />
### MT4156: Cannot register two categories ('\*' and '\*') with the same native name ('*').
<a name="MT4157" />
### MT4157: Cannot register the category method '\*' because at least one parameter is required (and its type must match the category type '\*')
<a name="MT4158" />
### MT4158: Cannot register the constructor * in the category * because constructors in categories are not supported.
<a name="MT4159" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4159: Cannot register the method '*' as a category method because category methods must be static.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4160" />
### MT4160: Invalid character '\*' (\*) found in selector '\*' for '\*'.
<a name="MT4161" />
### MT4161: The registrar found an unsupported structure '\*': All fields in a structure must also be structures (field '\*' with type '{2}' is not a structure).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The registrar found a structure with unsupported fields.
All fields in a structure that is exposed to Objective-C must also be structures (not classes).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4162" />
### MT4162: The type '\*' (used as * {2}) is not available in * * (it was introduced in * *)\* Please build with a newer * SDK (usually done by using the most recent version of Xcode.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The registrar found a type which is not included in the current SDK.
Please upgrade Xcode.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4163" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4163: Internal error in the registrar (*). Please file a bug report at http://bugzilla.xamarin.com
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This error indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT4164" />
### MT4164: Cannot export the property '\*' because its selector '\*' is an Objective-C keyword. Please use a different name.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The selector for the property in question is not a valid Objective-C identifer.
Please use a valid Objective-C identifier as selectors.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4165" />
### MT4165: The registrar couldn't find the type 'System.Void' in any of the referenced assemblies.
[registrar] Improve an error message. (#1047)
2016-10-28 15:38:38 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This error most likely indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[registrar] Improve an error message. (#1047)
2016-10-28 15:38:38 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4166" />
[static registrar] Fix registration of generic types. Fixes #44926. (#1063) https://bugzilla.xamarin.com/show_bug.cgi?id=44926
2016-10-28 19:42:45 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4166: Cannot register the method '\*' because the signature contains a type (\*) that isn't a reference type.
[static registrar] Fix registration of generic types. Fixes #44926. (#1063) https://bugzilla.xamarin.com/show_bug.cgi?id=44926
2016-10-28 19:42:45 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[static registrar] Fix registration of generic types. Fixes #44926. (#1063) https://bugzilla.xamarin.com/show_bug.cgi?id=44926
2016-10-28 19:42:45 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4167" />
[static registrar] Fix registration of generic types. Fixes #44926. (#1063) https://bugzilla.xamarin.com/show_bug.cgi?id=44926
2016-10-28 19:42:45 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT4167: Cannot register the method '\*' because the signature contains a generic type (\*) with a generic argument type that isn't an NSObject subclass (*).
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT4168" />
### MT4168: Cannot register the type '{managed\_name}' because its Objective-C name '{exported\_name}' is an Objective-C keyword. Please use a different name.
[mtouch] Show a nice error (MT4168) if the user registers a managed class with an Objective-C keyword. Fixes #51776. (#2150) Previously: obj/iPhone/Ad-Hoc/mtouch-cache/64/registrar.m:4402:12: error: expected identifier @interface register : UITableViewController { ^ obj/iPhone/Ad-Hoc/mtouch-cache/64/registrar.m:4402:21: error: expected unqualified-id @interface register : UITableViewController { error : Failed to compile the generated registrar code. Please file a bug report at http://bugzilla.xamarin.com Now: error MT4168: Cannot register the type 'register' because its Objective-C name 'register' is an Objective-C keyword. Please use a different name. https://bugzilla.xamarin.com/show_bug.cgi?id=51776
2017-05-31 20:07:02 +03:00
The Objective-C name for the type in question is not a valid Objective-C identifier.
Please use a valid Objective-C identifier.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4169" />
### MT4169: Failed to generate a P/Invoke wrapper for {method}: {message}
[mtouch] Report better error (MT4169) when we can't generate a P/Invoke wrapper for a P/Invoke. (#2349)
2017-07-20 16:34:42 +03:00
Xamarin.iOS failed to generate a P/Invoke wrapper function for the mentioned.
Please check the reported error message for the underlying cause.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4170" />
### MT4170: The registrar can't convert from '{managed type}' to '{native type}' for the return value in the method {method}.
Merge remote-tracking branch 'origin/master' into bindas-registrar-support
2017-09-22 11:23:37 +03:00
See the description of error <a href="#MT4172">MT4172</a>.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4171" />
### MT4171: The BindAs attribute on the member {member} is invalid: the BindAs type {type} is different from the property type {type}.
Merge remote-tracking branch 'origin/master' into bindas-registrar-support
2017-09-22 11:23:37 +03:00
Please make sure the type in the BindAs attribute matches the type of the member it's attached to.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT4172" />
### MT4172: The registrar can't convert from '{native type}' to '{managed type}' for the parameter '{parameter name}' in the method {method}.
[registrar] Add support for the BindAs attribute.
2017-07-03 20:18:02 +03:00
[docs] Add MT4171, and describe MT4169/4170.
2017-07-07 18:13:14 +03:00
The registrar does not support converting between the mentioned types.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This is a bug in Xamarin.iOS if the API in question is provided by Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Add MT4171, and describe MT4169/4170.
2017-07-07 18:13:14 +03:00
If you run into this while developing a binding project for a native library,
we're open to adding support for new combinations of types. If this is the
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
case, please file an enhancement request on [github](https://github.com/xamarin/xamarin-macios/issues/new)
[docs] Add MT4171, and describe MT4169/4170.
2017-07-07 18:13:14 +03:00
with a test case and we'll evaluate it.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT5xxx: GCC and toolchain error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT51xx: Compilation
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT5xxx GCC and toolchain
MT51xx compilation
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5101" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5101: Missing '*' compiler. Please install Xcode 'Command-Line Tools' component
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5102" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5102: Failed to assemble the file '*'. Please file a bug report at http://bugzilla.xamarin.com
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5103" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5103: Failed to compile the file '*'. Please file a bug report at http://bugzilla.xamarin.com
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5104" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5104: Could not find neither the '\*' nor the '\*' compiler. Please install Xcode 'Command-Line Tools' component
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!-- 5105 is used by mmp -->
[mtouch] Fix the error message for 'CompileTask'. The AOT-compilation occurs in the AOT-task now, and then we compile the result using CompileTask. This means that the error message in CompileTask was slightly incorrect, so rectify it.
2017-01-25 17:29:54 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5106" />
### MT5106: Could not compile the file(s) '*'. Please file a bug report at http://bugzilla.xamarin.com
[mtouch] Fix the error message for 'CompileTask'. The AOT-compilation occurs in the AOT-task now, and then we compile the result using CompileTask. This means that the error message in CompileTask was slightly incorrect, so rectify it.
2017-01-25 17:29:54 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS; please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[mtouch] Fix the error message for 'CompileTask'. The AOT-compilation occurs in the AOT-task now, and then we compile the result using CompileTask. This means that the error message in CompileTask was slightly incorrect, so rectify it.
2017-01-25 17:29:54 +03:00
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT52xx: Linking
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT52xx linking
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5201" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5201: Native linking failed. Please review the build log and the user flags provided to gcc: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5202" />
### MT5202: Native linking failed. Please review the build log.
<a name="MT5203" />
### MT5203: Native linking warning: *
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--- 5204-5208 are not used -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5209" />
### MT5209: Native linking error: *
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5210" />
### MT5210: Native linking failed, undefined symbol: *. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
This happens when the native linker cannot find a symbol that is referenced somewhere. There are several reasons this may happen:
* A third-party binding requires a framework, but the binding does not specify this in its `[LinkWith]` attribute. Solutions:
- If you're the author of the third-party binding, or have access to its source, modify the binding's `[LinkWith]` attribute to include the framework it needs:
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
[LinkWith ("mylib.a", Frameworks = "SystemConfiguration")]
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
- If you can't modify the third-party binding, you can manually link with the required framework by passing `-gcc_flags '-framework SystemFramework'` to `mtouch` (this is done by modifying the additional mtouch arguments in the project's iOS Build options page. Remember that this must be done for every project configuration).
* In some cases a managed binding is composed of several native libraries, and all must be included in the bindings. It is possible to have more than one native library in each binding project, so the solution is to just add all the required native libraries to the binding project.</li>
* A managed binding refers to native symbols that don't exist in the native library.
This usually happens when a binding has existed for some time, and the native
code has been modified during that time so that a particular native class has
either been removed or renamed, while the binding has not been updated.
* A P/Invoke refers to a native symbol that does not exist. Starting with Xamarin.iOS 7.4 an <a href="#MT5214">MT5214</a> error will be reported for this case (see MT5214 for more information).
* A third-party binding / library was built using C++, but the binding does not specify this in its `[LinkWith]` attribute. This is usually fairly easy to recognize, because the symbols have are mangled C++ symbols (one common example is `__ZNKSt9exception4whatEv`).
- If you're the author of the third-party binding, or have access to its source, modify the binding's `[LinkWith]` attribute to set the `IsCxx` flag:
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
[LinkWith ("mylib.a", IsCxx = true)]
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
- If you can't modify the third-party binding, or you're linking manually with a third-party library, you can set the equivalent flag by passing <code>-cxx</code> to mtouch (this is done by modifying the additional mtouch arguments in the project's iOS Build options page. Remember that this must be done for every project configuration).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5211" />
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5211: Native linking failed, undefined Objective-C class: \*. The symbol '\*' could not be found in any of the libraries or frameworks linked with your application.
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
This happens when the native linker cannot find an Objective-C class that is referenced somewhere. There are several reasons this may happen: the same as for [MT5210](#MT5210) and in addition:
* A third-party binding bound an Objective-C protocol, but did not annotate it with the <code>[Protocol]</code> attribute in its api definition. Solutions:
- Add the missing `[Protocol]` attribute:
[BaseType (typeof (NSObject))]
[Protocol] // Add this
public interface MyProtocol
{
}
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5212" />
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5212: Native linking failed, duplicate symbol: *.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This happens when the native linker encounters duplicated symbols between all the native libraries. Following this error there may be one or more [MT5213](#MT5213) errors with the location for each occurrence of the symbol. Possible reasons for this error:
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
* The same native library is included twice.
* Two distinct native libraries happen to define the same symbols.
* A native library is not correctly built, and contains the same symbol more than once.
You can confirm this by using the following set of commands from a terminal (replace i386 with x86_64/armv7/armv7s/arm64 according to which architecture you're building for):
# Native libraries are usually fat libraries, containing binary code for
# several architectures in the same file. First we extract the binary
# code for the architecture we're interested in.
lipo libNative.a -thin i386 -output libNative.i386.a
# Now query the native library for the duplicated symbol.
nm libNative.i386.a | fgrep 'SYMBOL'
# You can also list the object files inside the native library.
# In most cases this will reveal duplicated object files.
ar -t libNative.i386.a
There are a few possible ways to fix this:
- Request that the provider of the native library fix it and provide the updated version.
- Fix it yourself by removing the extra object files (this only works if the problem is in fact duplicated object files)
# Find out if the library is a fat library, and which
# architectures it contains.
lipo -info libNative.a
# Extract each architecture (i386/x86_64/armv7/armv7s/arm64) to a separate file
lipo libNative.a -thin ARCH -output libNative.ARCH.a
# Extract the object files for the offending architecture
# This will remove the duplicates by overwriting them
# (since they have the same filename)
mkdir -p ARCH
cd ARCH
ar -x ../libNative.ARCH.a
# Reassemble the object files in an .a
ar -r ../libNative.ARCH.a *.o
cd ..
# Reassemble the fat library
lipo *.a -create -output libNative.a
- Ask the linker to remove unused code. Xamarin.iOS will do this automatically if all of the following conditions are met:
- All third-party bindings' `[LinkWith]` attributes have enabled SmartLink:
[assembly: LinkWith ("libNative.a", SmartLink = true)]
- No `-gcc_flags` is passed to mtouch (in the additional mtouch arguments field of the project's iOS Build options).
- It's also possible to ask the linker directly to remove unused code by adding `-gcc_flags -dead_strip` to the additional mtouch arguments in the project's iOS Build options.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5213" />
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5213: Duplicate symbol in: * (Location related to previous error)
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This error is reported only together with [MT5212](#MT5212). Please see [MT5212](#MT5212) for more information.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5214" />
### MT5214: Native linking failed, undefined symbol: *. This symbol was referenced the managed member *. Please verify that all the necessary frameworks have been referenced and native libraries linked.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This error is reported when the managed code contains a P/Invoke to a native method that does not exist. For example:
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
```csharp
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
using System.Runtime.InteropServices;
class MyImports {
[DllImport ("__Internal")]
public static extern void MyInexistentFunc ();
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
}
```
There are a few possible solutions:
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
- Remove the P/Invokes in question from the source code.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
- Enable the managed linker for all assemblies (this is done in the project's iOS Build options, by setting "Linker Behavior" to "All assemblies"). This will effectively remove all the P/Invokes you don't use from the app (automatically, instead of manually like the previous point). The downside is that this will make your simulator builds somewhat slower, and it may break your app if it's using reflection - more information about the linker can be found [here](~/ios/deploy-test/linker.md) )
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
- Create a second native library which contains the missing native symbols. Note that this is merely a workaround (if you happen to try to call those functions, your app will crash).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5215" />
### MT5215: References to '*' might require additional -framework=XXX or -lXXX instructions to the native linker
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
This is a warning, indicating that a P/Invoke was detected to reference the library in question, but the app is not linking with it.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5216" />
### MT5216: Native linking failed for *. Please file a bug report at http://bugzilla.xamarin.com
[mtouch] Add target-specific error messages. This removes a little bit of duplicated code, and gives us slightly better error messages.
2017-01-25 16:59:13 +03:00
This error is reported when linking the output from the AOT compiler.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This error most likely indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT5217" />
[mtouch] Add target-specific error messages. This removes a little bit of duplicated code, and gives us slightly better error messages.
2017-01-25 16:59:13 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5217: Native linking possibly failed because the linker command line was too long (* characters).
[mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. (#2162) * [mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. * Refactor required symbol collection to store more information about each symbol (field, function, Objective-C class), and in general make the code more straight forward. * Implement support for generating source code that references these symbols, and do this whenever we can't ask the native linker to keep these symbols (when using bitcode). Additionally make it possible to do this manually, so that the source code can be generated for non-bitcode platforms too (which is useful if the number of symbols is enormous, in which case we might surpass the maximum command-line length). * Also make it possible to completely ignore native symbols, or ignore them on a per-symbol basis. This provides a fallback for users if we get something right and we try to preserve something that shouldn't be preserved (for instance if it doesn't exist), and the user ends up with unfixable linker errors. * Don't collect Objective-C classes unless they're in an assembly with LinkWith attributes. We don't need to preserve Objective-C classes in any other circumstances. * Implement everything for both Xamarin.iOS and Xamarin.Mac, and share the code between them. * Remove previous workaround for bug #51710, since it's no longer needed. * Add tests. https://bugzilla.xamarin.com/show_bug.cgi?id=54417 https://bugzilla.xamarin.com/show_bug.cgi?id=51710 * [mtouch] Make sure to only keep symbols from the current app when code sharing. This fixes a build problem with the interdependent-binding-projects test when testing in Today Extension mode.
2017-06-02 19:29:19 +03:00
Native linking failed, and it's possible this occured because the linker
command was too long.
Xamarin.iOS projects will often reference native symbols dynamically, which
means that the native linker might remove such native symbols during the
native linking process, because the native linker does not see that these
symbols are used.
Usually Xamarin.iOS will ask the native linker to keep such symbols using the
`-u symbol` linker flag, but if there are many such symbols, the entire
command-line might exceed the maximum command-line length as specified by the
operating system.
There are a few possible sources for such dynamic symbols:
* P/Invokes to methods in statically linked libraries (where the dll name is
`__Internal` in the DllImport attribute `[DllImport ("__Internal")]`).
* Field references to memory locations in statically linked libraries from
binding projects (`[Field]` attributes).
* Objective-C classes referenced in statically linked libraries from binding
projects (when using incremental builds or when not using the static
registrar).
Possible solutions:
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
[mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. (#2162) * [mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. * Refactor required symbol collection to store more information about each symbol (field, function, Objective-C class), and in general make the code more straight forward. * Implement support for generating source code that references these symbols, and do this whenever we can't ask the native linker to keep these symbols (when using bitcode). Additionally make it possible to do this manually, so that the source code can be generated for non-bitcode platforms too (which is useful if the number of symbols is enormous, in which case we might surpass the maximum command-line length). * Also make it possible to completely ignore native symbols, or ignore them on a per-symbol basis. This provides a fallback for users if we get something right and we try to preserve something that shouldn't be preserved (for instance if it doesn't exist), and the user ends up with unfixable linker errors. * Don't collect Objective-C classes unless they're in an assembly with LinkWith attributes. We don't need to preserve Objective-C classes in any other circumstances. * Implement everything for both Xamarin.iOS and Xamarin.Mac, and share the code between them. * Remove previous workaround for bug #51710, since it's no longer needed. * Add tests. https://bugzilla.xamarin.com/show_bug.cgi?id=54417 https://bugzilla.xamarin.com/show_bug.cgi?id=51710 * [mtouch] Make sure to only keep symbols from the current app when code sharing. This fixes a build problem with the interdependent-binding-projects test when testing in Today Extension mode.
2017-06-02 19:29:19 +03:00
* Enable the managed linker (if possible for all assemblies instead of only
SDK assemblies). This might remove enough of the sources for dynamic symbols
so that the linker's command-line doesn't exceeded the maximum.
* Reduce the number of P/Invokes, field references and/or Objective-C classes.
* Rewrite the dynamic symbols to have shorter names.
* Pass `-dlsym:false` as an additional mtouch argument in the project's iOS
Build options. With this option, Xamarin.iOS will generate a native
reference in the AOT-compiled code, and won't need to ask the linker to keep
this symbol. However, this only works for device builds, and it will cause
linker errors if there are P/Invokes to functions that don't exist in the
static library.
* Pass `--dynamic-symbol-mode=code` as an additional mtouch arguments in
the project's iOS Build options. With this option, Xamarin.iOS will generate
additional native code that references these symbols instead of asking the
native linker to keep these symbols using command-line arguments. The
downside to this approach is that it will increase the size of the
executable somewhat.
* Enable the static registrar by passing `--registrar:static` as an additional
mtouch argument in the project's iOS Build options (for simulator builds,
since the static registrar is already the default for device builds). The
static registrar will generate code that references Objective-C classes
statically, so there is no need to ask the native linker to keep such
classes.
* Disable incremental builds (for device builds). When incremental builds are
enabled, the code generated by the static registrar won't be considered by
the native linker, which means that Xamarin.iOS must still ask the linker to
keep referenced Objective-C classes. Thus disabling incremental builds will
prevent this need.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5218" />
### MT5218: Can't ignore the dynamic symbol {symbol} (--ignore-dynamic-symbol={symbol}) because it was not detected as a dynamic symbol.
[mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. (#2162) * [mtouch] Improve how we make sure native symbols aren't stripped away. Fixes #51710 and #54417. * Refactor required symbol collection to store more information about each symbol (field, function, Objective-C class), and in general make the code more straight forward. * Implement support for generating source code that references these symbols, and do this whenever we can't ask the native linker to keep these symbols (when using bitcode). Additionally make it possible to do this manually, so that the source code can be generated for non-bitcode platforms too (which is useful if the number of symbols is enormous, in which case we might surpass the maximum command-line length). * Also make it possible to completely ignore native symbols, or ignore them on a per-symbol basis. This provides a fallback for users if we get something right and we try to preserve something that shouldn't be preserved (for instance if it doesn't exist), and the user ends up with unfixable linker errors. * Don't collect Objective-C classes unless they're in an assembly with LinkWith attributes. We don't need to preserve Objective-C classes in any other circumstances. * Implement everything for both Xamarin.iOS and Xamarin.Mac, and share the code between them. * Remove previous workaround for bug #51710, since it's no longer needed. * Add tests. https://bugzilla.xamarin.com/show_bug.cgi?id=54417 https://bugzilla.xamarin.com/show_bug.cgi?id=51710 * [mtouch] Make sure to only keep symbols from the current app when code sharing. This fixes a build problem with the interdependent-binding-projects test when testing in Today Extension mode.
2017-06-02 19:29:19 +03:00
The command-line argument `--ignore-dynamic-symbol=symbol` was passed, but
this symbol is not a symbol that was recognized as a dynamic symbol that must
be manually preserved.
There are two main reasons for this:
* The symbol name is incorrect.
* Don't prepend an underscore to the symbol name.
* The symbol for Objective-C classes is `OBJC_CLASS_$_<classname>`.
* The symbol is correct, but it's a symbol that's already preserved by normal
means (some build options causes the exact list of dynamic symbols to vary).
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT53xx: Other tools
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT53xx other tools
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5301" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5301: Missing 'strip' tool. Please install Xcode 'Command-Line Tools' component
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5302" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5302: Missing 'dsymutil' tool. Please install Xcode 'Command-Line Tools' component
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5303" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5303: Failed to generate the debug symbols (dSYM directory). Please review the build log.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when running dsymutil on the final .app directory to create the debug symbols. Please review the build log to see dsymutil's output and see how it can be fixed.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5304" />
### MT5304: Failed to strip the final binary. Please review the build log.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when running the 'strip' tool to remove debugging information from the application.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5305" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5305: Missing 'lipo' tool. Please install Xcode 'Command-Line Tools' component
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5306" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT5306: Failed to create the a fat library. Please review the build log.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when running the 'lipo' tool. Please review the build log to see the error reported by 'lipo'.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT5307" />
### MT5307: Failed to sign the executable. Please review the build log.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when signing the application. Please review the build log to see the error reported by 'codesign'.
<!-- 5308 is used by mmp -->
<!-- 5309 is used by mmp -->
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!-- 5310 is used by mmp -->
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT6xxx: mtouch internal tools error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
### MT600x: Stripper
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT6xxx mtouch internal tools
MT600x Stripper
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT6001" />
### MT6001: Running version of Cecil doesn't support assembly stripping
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT6002" />
### MT6002: Could not strip assembly `*`.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
An error occurred when stripping managed code(removing the IL code) from the assemblies in the application.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT6003" />
### MT6003: [UnauthorizedAccessException message]
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
A security error ocurred while stripping debugging symbols from the application.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT7xxx: MSBuild error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
MT7xxx msbuild errors
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7001" />
### MT7001: Could not resolve host IPs for WiFi debugger settings.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: DetectDebugNetworkConfigurationTaskBase*
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Troubleshooting steps:
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
- try to run `csharp -e 'System.Net.Dns.GetHostEntry (System.Net.Dns.GetHostName ()).AddressList'` (that should give you an IP address and not an error obviously).
- try to run "ping \`hostname\`" which might give you more information, like: `cannot resolve MyHost.local: Unknown host`
In some cases, it's a "local network" issue and it can be addressed by adding the unknown host `127.0.0.1 MyHost.local` in `/etc/hosts`.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7002" />
### MT7002: This machine does not have any network adapters. This is required when debugging or profiling on device over WiFi.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: DetectDebugNetworkConfigurationTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7003" />
### MT7003: The App Extension '*' does not contain an Info.plist.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7004" />
### MT7004: The App Extension '*' does not specify a CFBundleIdentifier.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7005" />
### MT7005: The App Extension '*' does not specify a CFBundleExecutable.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7006" />
### MT7006: The App Extension '\*' has an invalid CFBundleIdentifier (\*), it does not begin with the main app bundle's CFBundleIdentifier (*).
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7007" />
### MT7007: The App Extension '\*' has a CFBundleIdentifier (\*) that ends with the illegal suffix ".key".
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7008" />
### MT7008: The App Extension '*' does not specify a CFBundleShortVersionString.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7009" />
### MT7009: The App Extension '*' has an invalid Info.plist: it does not contain an NSExtension dictionary.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7010" />
### MT7010: The App Extension '*' has an invalid Info.plist: the NSExtension dictionary does not contain an NSExtensionPointIdentifier value.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7011" />
### MT7011: The WatchKit Extension '*' has an invalid Info.plist: the NSExtension dictionary does not contain an NSExtensionAttributes dictionary.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7012" />
### MT7012: The WatchKit Extension '*' does not have exactly one watch app.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7013" />
### MT7013: The WatchKit Extension '*' has an invalid Info.plist: UIRequiredDeviceCapabilities must contain the 'watch-companion' capability.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7014" />
### MT7014: The Watch App '*' does not contain an Info.plist.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7015" />
### MT7015: The Watch App '*' does not specify a CFBundleIdentifier.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7016" />
### MT7016: The Watch App '\*' has an invalid CFBundleIdentifier (\*), it does not begin with the main app bundle's CFBundleIdentifier (*).
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7017" />
### MT7017: The Watch App '\*' does not have a valid UIDeviceFamily value. Expected 'Watch (4)' but found '\* (*)'.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7018" />
### MT7018: The Watch App '*' does not specify a CFBundleExecutable
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7019" />
### MT7019: The Watch App '\*' has an invalid WKCompanionAppBundleIdentifier value ('\*'), it does not match the main app bundle's CFBundleIdentifier ('*').
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7020" />
### MT7020: The Watch App '*' has an invalid Info.plist: the WKWatchKitApp key must be present and have a value of 'true'.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7021" />
### MT7021: The Watch App '*' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7022" />
### MT7022: The Watch App '*' does not contain a Watch Extension.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7023" />
### MT7023: The Watch Extension '*' does not contain an Info.plist.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7024" />
### MT7024: The Watch Extension '*' does not specify a CFBundleIdentifier.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7025" />
### MT7025: The Watch Extension '*' does not specify a CFBundleExecutable.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7026" />
### MT7026: The Watch Extension '\*' has an invalid CFBundleIdentifier (\*), it does not begin with the main app bundle's CFBundleIdentifier (*).
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7027" />
### MT7027: The Watch Extension '\*' has a CFBundleIdentifier (\*) that ends with the illegal suffix ".key".
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7028" />
### MT7028: The Watch Extension '*' has an invalid Info.plist: it does not contain an NSExtension dictionary.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7029" />
### MT7029: The Watch Extension '*' has an invalid Info.plist: the NSExtensionPointIdentifier must be "com.apple.watchkit".
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7030" />
### MT7030: The Watch Extension '*' has an invalid Info.plist: the NSExtension dictionary must contain NSExtensionAttributes.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7031" />
### MT7031: The Watch Extension '*' has an invalid Info.plist: the NSExtensionAttributes dictionary must contain a WKAppBundleIdentifier.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7032" />
### MT7032: The WatchKit Extension '*' has an invalid Info.plist: UIRequiredDeviceCapabilities should not contain the 'watch-companion' capability.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7033" />
### MT7033: The Watch App '*' does not contain an Info.plist.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7034" />
### MT7034: The Watch App '*' does not specify a CFBundleIdentifier.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7035" />
### MT7035: The Watch App '\*' does not have a valid UIDeviceFamily value. Expected '\*' but found '\* (\*)'.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7036" />
### MT7036: The Watch App '*' does not specify a CFBundleExecutable.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7037" />
### MT7037: The WatchKit Extension '{extensionName}' has an invalid WKAppBundleIdentifier value ('\*'), it does not match the Watch App's CFBundleIdentifier ('\*').
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7038" />
### MT7038: The Watch App '*' has an invalid Info.plist: the WKCompanionAppBundleIdentifier must exist and must match the main app bundle's CFBundleIdentifier.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7039" />
### MT7039: The Watch App '*' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7040" />
### MT7040: The app bundle {AppBundlePath} does not contain an Info.plist.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7041" />
### MT7041: Main Info.plist path does not specify a CFBundleIdentifier.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7042" />
### MT7042: Main Info.plist path does not specify a CFBundleExecutable.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7043" />
### MT7043: Main Info.plist path does not specify a CFBundleSupportedPlatforms.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7044" />
### MT7044: Main Info.plist path does not specify a UIDeviceFamily.
[msbuild] Add msbuild error code logic - `LoggingExtensions` has a new `MTError` extension method that helps generate an msbuild error with the proper MTxxx format. - Added error codes for 44 msbuild errors. - Updated `docs/website/mtouch-errors.md` and `tools/mtouch/error.cs` accordingly. - MT7001 contains some extra documentation (troubleshooting steps).
2016-11-24 17:21:46 +03:00
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: ValidateAppBundleTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7045" />
### MT7045: Unrecognized Format: *.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
[docs] xamarin now requires markdown+yaml (#2258) * markdown, yaml, api links, accessibility (for images) ensure iOS docs conform to xamarin docpub standards * markdown formatting fixes
2017-07-13 04:29:47 +03:00
Where * can be:
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
- string
- array
- dict
- bool
- real
- integer
- date
- data
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7046" />
### MT7046: Add: Entry, *, Incorrectly Specified.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7047" />
### MT7047: Add: Entry, *, Contains Invalid Array Index.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7048" />
### MT7048: Add: * Entry Already Exists.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7049" />
### MT7049: Add: Can't Add Entry, *, to Parent.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7050" />
### MT7050: Delete: Can't Delete Entry, *, from Parent.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7051" />
### MT7051: Delete: Entry, *, Contains Invalid Array Index.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7052" />
### MT7052: Delete: Entry, *, Does Not Exist.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7053" />
### MT7053: Import: Entry, *, Incorrectly Specified.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7054" />
### MT7054: Import: Entry, *, Contains Invalid Array Index.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7055" />
### MT7055: Import: Error Reading File: *.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7056" />
### MT7056: Import: Can't Add Entry, *, to Parent.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7057" />
### MT7057: Merge: Can't Add array Entries to dict.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7058" />
### MT7058: Merge: Specified Entry Must Be a Container.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7059" />
### MT7059: Merge: Entry, *, Contains Invalid Array Index.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7060" />
### MT7060: Merge: Entry, *, Does Not Exist.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7061" />
### MT7061: Merge: Error Reading File: *.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7062" />
### MT7062: Set: Entry, *, Incorrectly Specified.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7063" />
### MT7063: Set: Entry, *, Contains Invalid Array Index.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7064" />
### MT7064: Set: Entry, *, Does Not Exist.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7065" />
### MT7065: Unknown PropertyList editor action: *.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7066" />
### MT7066: Error loading '*': *.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT7067" />
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT7067: Error saving '*': *.
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
*MSBuild task: PropertyListEditorTaskBase*
[msbuild] Add error codes for PropertyListEditorTaskBase (#1325) * [msbuild] Add error codes for PropertyListEditorTaskBase * [msbuild] Add task names in all errors' descriptions
2016-12-12 12:30:42 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
## MT8xxx: Runtime error messages
[xi-errors] Add headers for error code ranges
2016-12-08 00:33:34 +03:00
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
<!--
MT8xxx runtime
MT800x misc
-->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8001" />
### MT8001: Version mismatch between the native Xamarin.iOS runtime and monotouch.dll. Please reinstall Xamarin.iOS.
<a name="MT8002" />
### MT8002: Could not find the method '\*' in the type '\*'.
<a name="MT8003" />
### MT8003: Failed to find the closed generic method '\*' on the type '\*'.
<a name="MT8004" />
### MT8004: Cannot create an instance of * for the native object 0x* (of type '*'), because another instance already exists for this native object (of type *).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8005" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8005: Wrapper type '\*' is missing its native ObjectiveC class '\*'.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8006" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8006: Failed to find the selector '\*' on the type '\*'
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8007" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8007: Cannot get the method descriptor for the selector '\*' on the type '\*', because the selector does not correspond to a method
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8008" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8008: The loaded version of Xamarin.iOS.dll was compiled for * bits, while the process is * bits. Please file a bug at http://bugzilla.xamarin.com.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates something is wrong in the build process. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8009" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8009: Unable to locate the block to delegate conversion method for the method *.*'s parameter #*. Please file a bug at http://bugzilla.xamarin.com.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates an API wasn't bound correctly. If this is an API exposed by Xamarin, please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new)., if it's a third-party binding, please contact the vendor.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8010" />
### MT8010: Native type size mismatch between Xamarin.[iOS|Mac].dll and the executing architecture. Xamarin.[iOS|Mac].dll was built for *-bit, while the current process is *-bit.
This indicates something is wrong in the build process. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT8011" />
### MT8011: Unable to locate the delegate to block conversion attribute ([DelegateProxy]) for the return value for the method *.*. Please file a bug at http://bugzilla.xamarin.com.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Xamarin.iOS was unable to locate a required method at runtime (to convert a delegate to a block).
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8012" />
### MT8012: Invalid DelegateProxyAttribute for the return value for the method *.*: DelegateType is null. Please file a bug at http://bugzilla.xamarin.com.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The DelegateProxy attribute for the method in question is invalid.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8013" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8013: Invalid DelegateProxyAttribute for the return value for the method *.*: DelegateType ({2}) specifies a type without a 'Handler' field. Please file a bug at http://bugzilla.xamarin.com.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
The `[DelegateProxy]` attribute for the method in question is invalid.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8014" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8014: Invalid DelegateProxyAttribute for the return value for the method *.*: The DelegateType's ({2}) 'Handler' field is null. Please file a bug at http://bugzilla.xamarin.com.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
The `[DelegateProxy]` attribute for the method in question is invalid.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8015" />
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8015: Invalid DelegateProxyAttribute for the return value for the method *.*: The DelegateType's ({2}) 'Handler' field is not a delegate, it's a *. Please file a bug at http://bugzilla.xamarin.com.
[docs] Ease tracking updates to code that requires change to the web site documentation (#573) This makes it possible to have a single PR with both the feature and the documentation changes.
2016-08-09 00:07:59 +03:00
The DelegateProxy attribute for the method in question is invalid.
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
<a name="MT8016" />
### MT8016: Unable to convert delegate to block for the return value for the method *.*, because the input isn't a delegate, it's a *. Please file a bug at http://bugzilla.xamarin.com.
The `[DelegateProxy]` attribute for the method in question is invalid.
This usually indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
Unify stret detection between the generator and platform assemblies, and fix stret detection on watchOS. Fixes #44709. Unify the code to determine whether a particular return type requires a stret signature or not between the generator and platform assemblies. Also fix the stret detection for armv7k, whose calling convention is not identical to armv7(s): there's the concept of homogeneous structures, which contains multiple elements of only one type, and which is sometimes passed in registers on armv7k. https://bugzilla.xamarin.com/show_bug.cgi?id=44709
2016-10-11 20:24:23 +03:00
[docs] Document mmp errors and remove duplicated information about mtouch errors. (#2056)
2017-05-01 21:02:54 +03:00
<!-- 8017 is used by mmp -->
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8018" />
### MT8018: Internal consistency error. Please file a bug report at http://bugzilla.xamarin.com.
Unify stret detection between the generator and platform assemblies, and fix stret detection on watchOS. Fixes #44709. Unify the code to determine whether a particular return type requires a stret signature or not between the generator and platform assemblies. Also fix the stret detection for armv7k, whose calling convention is not identical to armv7(s): there's the concept of homogeneous structures, which contains multiple elements of only one type, and which is sometimes passed in registers on armv7k. https://bugzilla.xamarin.com/show_bug.cgi?id=44709
2016-10-11 20:24:23 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
Unify stret detection between the generator and platform assemblies, and fix stret detection on watchOS. Fixes #44709. Unify the code to determine whether a particular return type requires a stret signature or not between the generator and platform assemblies. Also fix the stret detection for armv7k, whose calling convention is not identical to armv7(s): there's the concept of homogeneous structures, which contains multiple elements of only one type, and which is sometimes passed in registers on armv7k. https://bugzilla.xamarin.com/show_bug.cgi?id=44709
2016-10-11 20:24:23 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8019" />
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8019: Could not find the assembly * in the loaded assemblies.
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8020" />
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8020: Could not find the module with MetadataToken * in the assembly *.
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8021" />
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8021: Unknown implicit token type: *.
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[registrar] Use metadata tokens instead of strings to find types and methods. (#1085) Use metadata tokens instead of strings to find types and methods. This makes the code to find methods more compact (a lot less strings in the executable, and additionally in most cases a compact representation (32-bit integer) of the corresponding metadata token and additional information can be used, which results in less executable code (fewer parameters to methods, etc)), resulting in smaller executables. Size savings are around 200kb for dont link apps, and 20-60kb for linked apps (this obviously varies a lot depending on how much has to registered by the registrar). | | Before | After | Diff | |----------------|--------------:|--------------:|------------------:| | dontlink/32bit | 102.810.144 | 102.609.456 | -200.688 = -0,20% | | dontlink/64bit | 107.420.576 | 107.221.792 | -198.784 = -0,19% | | linksdk/32bit | 40.957.296 | 40.936.864 | -20.432 = -0,05% | | linksdk/64bit | 43.113.136 | 43.093.936 | -19.200 = -0,04% | | linkall/32bit | 38.410.032 | 38.348.288 |  -61.744 = -0,16% | | linkall/64bit | 40.315.200 | 40.267.344 | -47.856 = -0,12% | Additionally I've removed the `lazy_map` dictionary, which we populated at startup and was used to map between Class instances and the corresponding managed type's FullName, and instead iterate over a native array of Class -> metadata token mappings whenever we need to look up the managed type for a certain Class instance. This is slightly slower for each type we need to look up (for a non-linked app there might be a 2000-3000 entries in the native array, which would be iterated instead of using a hashtable lookup), but it's only done once per type and there's a significant startup memory improvement. For a non-linked test app I get the following using the Xamarin profiler: | | Before | After | Diff | |-------------------|--------:|--------:|----------------:| | Memory allocated | 2,8 MB | 2,4 MB | -0,4 MB = -14 % | | Objects allocated | 43678 | 38463 | -5215 = -12 % | | Private bytes | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% | | Working set | 26,6 MB | 24,4 MB | -2,2 MB = -8,3% |
2016-11-01 21:34:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8022" />
[registrar] Add support for the BindAs attribute.
2017-07-03 20:18:02 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8022: Expected the token reference * to be a *, but it's a *. Please file a bug report at http://bugzilla.xamarin.com.
[registrar] Add support for the BindAs attribute.
2017-07-03 20:18:02 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[registrar] Add support for the BindAs attribute.
2017-07-03 20:18:02 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8023" />
[mtouch/mmp] Generate table of protocols and their corresponding wrapper type in the static registrar. Generate table of protocols and their corresponding wrapper type in the static registrar, so that we don't have to look for this information using the dynamic registrar at runtime.
2018-02-10 03:23:56 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8023: An instance object is required to construct a closed generic method for the open generic method: * (token reference: *). Please file a bug report at http://bugzilla.xamarin.com.
[docs] Update according to review.
2018-02-14 03:37:47 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).
[ObjCRuntime] Add a DynamicRegistrarSupported property, and use it in a few places that require the dynamic registrar.
2018-02-02 20:19:13 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
<a name="MT8024" />
[ObjCRuntime] Add a DynamicRegistrarSupported property, and use it in a few places that require the dynamic registrar.
2018-02-02 20:19:13 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
### MT8024: Could not find a valid extension type for the smart enum '{smart_type}'. Please file a bug at https://bugzilla.xamarin.com.
[ObjCRuntime] Add a DynamicRegistrarSupported property, and use it in a few places that require the dynamic registrar.
2018-02-02 20:19:13 +03:00
Synchronize back docs moved to https://docs.microsoft.com (#3771)
2018-04-17 16:02:42 +03:00
This indicates a bug in Xamarin.iOS. Please file a new issue on [github](https://github.com/xamarin/xamarin-macios/issues/new).