diff --git a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.hu.resx b/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.hu.resx deleted file mode 100644 index 8e9b41a60730..000000000000 --- a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.hu.resx +++ /dev/null @@ -1,1017 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - Tool {0} execution started with arguments: {1} - - - - Tool {0} execution finished (exit code = {1}). - - - - Error executing tool '{0}': {1} - - - - Failed to codesign '{0}': {1} - - - - Failed to codesign '{0}' - - - - '{0}' not found. - - - - hu. - - - - Invalid iTunesArtwork dimensions ({0}x{1}) for '{2}'. - - - - Multiple iTunesArtwork files with the same dimensions detected ({0}x{1}) for '{2}'. - - - - Error loading '{0}': {1} - - - - Could not parse MinimumOSVersion value '{0}' - - - - Could not parse TargetArchitectures '{0}' - - - - The {0} SDK for '{1}' is not installed. - - - - The executable (CFBundleExecutable) name ({0}) cannot end with '.app', because iOS may fail to launch the app. - - - - Can only fake the watchOS 4.3 SDK when building for watchOS. - - - - All http loads are already allowed. - - - - Allowed arbitrary HTTP loads to support debugging. - - - - Supported iPhone orientations have not been set - - - - Supported iPhone orientations are not matched pairs - - The iPhone orientation settings do not match iPad, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Supported iPad orientations have not been set - - - - Supported iPad orientations are not matched pairs - - The iPad orientation settings do not match iPhone, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Cannot have more than 1 iTunesMetadata.plist. - - - - Error loading Settings plist file '{0}/Settings.bundle/Root.plist': {1}. - - - - Could not parse the SDK version '{0}' - - - - - - - - - - Could not locate SDK bin directory - - - - - - - - - - - - - - - Could not find a valid Xcode app bundle at '{0}'. Please update your Apple SDK location in Visual Studio's preferences {1}. - - The following are literal names and should not be translated: Xcode, Apple SDK, Visual Studio -{0} - The selected Xcode / Apple SDK directory. - - - Could not find valid a usable Xcode developer path - - - - Could not find '{0}' - - - - Searching for '{0}' in '{1}' - - - - Unknown SDK platform: {0} - - - - Could not locate the provisioning profile with a Name or UUID of {0}. - - - - Unknown search option: {0} - - - - Unknown native reference type for '{0}'. - - - - Dynamic native references are not supported: '{0}' - - - - Target architecture ARMv6 is no longer supported in Xamarin.iOS. Please select a supported architecture. - - - - Failed to create response file '{0}': {1} - - - - Could not load Info.plist: {0} - - - - Invalid architectures: '{0}'. - - - - Failed to parse the target device information. - - - - No target device found. - - - - No device architecture information found. - - - - Invalid target architecture: '{0}' - - - - No device operating system information found. - - - - No device model information found. - - - - No iOS version information found. - - - - Resources rules file '{0}' not found. - - - - Failed to parse SdkVersion '{0}'. - - - - Xcode 10 does not support watchOS 1 apps. Either upgrade to watchOS 2 apps, or use an older version of Xcode. - - - An installation of Xcode >= 6.2 is required to build WatchKit applications. - - - - iOS {0} does not support WatchKit. - - - - Failed to locate the WatchKit launcher in the Xcode app bundle. - - - - The App Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The App Extension '{0}' does not specify a CFBundleVersion - - - - The App Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The App Extension '{0}' has an unrecognized NSExtensionPointIdentifier value ('{1}'). - - - - The Watch App '{0}' does not specify a CFBundleShortVersionString - - - - The Watch App '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch App '{0}' does not specify a CFBundleVersion - - - - The Watch App '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleShortVersionString) - - - - The Watch Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleVersion - - - - The Watch Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - - Could not locate the {0} '{1}' SDK at path '{}' - - - - Could not locate the {0} '{1}' SDK usr path at '{2}' - - The provided SDK path is missing a 'usr' directory. The following are literal names and should not be translated: SDK, usr -{0} - The platform name, such as 'iOS'. -{1} - The version number of the SDK. -{2} - The file path of the SDK. - - - Could not find a valid Xcode developer path - - - - - - Unrecognized platform: {0} - - - - Asset not part of an asset catalog: {0} - - - - File not found: {0} - - - - Invalid json: {0} - - - - Partial Info.plist file was not generated: {0} - - - - Failed to load {0} log file `{1}`: {2} - - A general failure message if a log file wasn't able to be loaded. -{0} - The command-line tool that generated the log. -{1} - The file path to the log. -{2} - Further detail about the failure. - - - Failed to parse altool output: {0}. - Output: {1} - - - - - No API definition file specified. - - - - {0} failed. - - A general error message that a command-line tool failed. -{0} - The file path to the command-line tool. - - - Bundle Resource '{0}' not found on disk (should be at '{1}') - - - - The path '{0}' would result in a file outside of the app bundle and cannot be used. - - - - Info.plist files should have a Build Action of 'None'. - - - - The name '{0}' is reserved and cannot be used. - - - - Found a directory within the Frameworks directory which is not a framework: {0} - - - - The framework {0} does not contain a binary named {1} - - - - No Frameworks directory found. - - - - Could not determine value for manifest key '{0}' - - - - Error loading partial Info.plist template file '{0}': {1} - - - - Cannot expand $(TeamIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - Cannot expand $(AppIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - iCloud entitlements such as '{0}' require a Provisioning Profile. - - - - The iCloud entitlement '{0}' is not supported by the Provisioning Profile. - - - - Entitlements.plist template '{0}' not found. - - - - Error loading Entitlements.plist template '{0}': {1} - - - - Error writing xcent file '{0}': {1} - - - - Error writing archived-expanded-entitlements.xcent file: {0} - - - - Tool {0} execution finished. - - - - {0} exited with code {1} - - - - Skipping `{0}' as the output file, `{1}', is newer. - - Skipping a build operation, since the destination file is newer than the source file. -{0} - The destination file. -{1} - The source file. - - - Error saving `{0}': {1} - - - - Creating binding resource package: {0} - - - - Error loading '{0}' - - - - Package creation failed. Could not parse extra arguments. - - - - The identity '{0}' doesn't match any valid certificate/private key pair in the default keychain. - - A failure to sign the iOS application, due to a missing certificate/private key. Xcode has an identical error message, see: https://developer.apple.com/library/archive/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TNTAG40-WHAT_DOES__VALID_SIGNING_IDENTITY_NOT_FOUND__MEAN_AND_HOW_DO_I_RESOLVE_IT_ -{0} - The name of the identity, such as 'iPhone Developer'. - - - Detected signing identity: - - - - The certificate '{0}' does not match any of the prefixes '{1}'. - - - - The certificate '{0}' has expired ({1}) - - - - No valid {0} code signing keys found in keychain. You need to request a codesigning certificate from https://developer.apple.com. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. - - - The certificate '{0}' does not match '{1}'. - - - - {0} code signing key '{1}' not found in keychain. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The name of the code signing key, such as 'Apple Development'. - - - Could not find any available provisioning profiles for {0} on {1}. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The app bundle name, such as 'YouriOSApp.app' -{1} - The platform name, such as 'iOS'. - - - '{0}' doesn't match '{1}'. - - - - No installed provisioning profiles match the installed {0} {1} signing identities. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The app bundle name, such as 'YouriOSApp.app' - - - Finding matching provisioning profiles with compatible AppID, keeping only those with the longest matching (wildcard) IDs. - - - - AppID: {0} was ruled out because we found a better match: {1}. - - - - AppID: {0} was ruled out because we already found better matches: {1}. - - - - No installed provisioning profiles match the bundle identifier. - - - - Multiple provisioning profiles match the bundle identifier; using the first match. - - - - {0} does not define CFBundleIdentifier - - - - The specified {0} provisioning profile '{1}' could not be found - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The provisioning profile ID. A string such as: 'f35b0040-2be5-4b1c-a1d6-59ae85047fad' - - - Project bundle identifier '{0}' does not match specified provisioning profile '{1}' - - - - Multiple signing identities match '{0}'; using the first match. - - - - Multiple signing identities found; using the first identity. - - - - The specified {0} provisioning profile '{1}' could not be found - - - - No {0} signing identities match the specified provisioning profile '{1}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile. - - - - {0} found at: {1} - - A file was found at a location. -{0} - The '%(LogicalName)' of the file, or a relative path. -{1} - The location the file was found. - - - AssemblyPath cannot be null or empty - - - - Generated bundle name: {0} - - - - No property specified. - - - - The dictionary at '{0}' did not contain the key: {1} - - - - Could not parse array index: {0} - - - - Array index out of range for item '{0}' - - - - {0} values do not support child properties. - - The type of value in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), such as a number or string cannot contain child values. -{0} - The value type, such as 'NSString'. - - - Getting {0} values is not supported. - - - - The file '{0}' does not exist. - - - - The file '{0}' conflicts with '{1}'. - - - - Watch apps/extensions require Xcode 6.2 or later. The current Xcode version is {0} - - - - Items must have logical names computed. - - - - Duplicate Entry Was Skipped: {0} - - - - File Doesn't Exist, Will Create: {0} - - - - Creating directory '{0}' - - - - Copying file from '{0}' to '{1}' - - - - You must specify a DestinationFolder or the DestinationFiles, but not both. - - - - The number of DestinationFiles must match the number of SourceFiles. - - - - Skipping framework assembly: {0} - - - - Unknown target framework identifier: {0}. - - - - Could not find {0} in {1}. - - - - The {0} SDK is not installed. - - - - The {0} SDK version '{1}' is not installed, and no newer version was found. - - - - The {0} SDK version '{1}' is not installed. Using newer version '{2}' instead'. - - - - {0} has an incorrect or unknown format and cannot be processed. - - - - No matching framework found inside '{0}'. - - - - Conflicting '{0}' and '{1}' options. '{1}' will be ignored. - - - - Can't get an ISshCommands instance. Please check that a valid connection to the Mac is established. - - - An error occurred while trying to copy Archive '{0}' to '{1}'. Details: {2} - - - There is no available connection to the Mac. Task '{0}' will not be executed - - - Could not deserialize DataSet {0} - - - The file {0} does not have ImageAsset as build action. - - - Could not resolve UTI for {0} in catalog {1} - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS - - - The project was built with a version of Xcode ({0}) that is not compatible which may result in unexpected warnings or errors. Please install Xcode '{1}' or visit the documentation to learn more. - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS. Details: {0} - - - - The provided Archive Path is not from a valid archive file (.xcarchive). Archive Path: '{0}' - - - Could not map the macOS version {0} to a corresponding iOS version - - - Could not resolve host IPs for WiFi debugger settings. - - - - This machine does not have any network adapters. This is required when debugging or profiling on device over WiFi. - - - - The App Extension '{0}' does not contain an Info.plist. - - - - The App Extension '{0}' does not specify a CFBundleIdentifier. - - - - The App Extension '{0}' does not specify a CFBundleExecutable. - - - - The App Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The App Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The App Extension '{0}' does not specify a CFBundleShortVersionString. - - - - The App Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The App Extension '{0}' has an invalid Info.plist: the NSExtension dictionary does not contain an NSExtensionPointIdentifier value. - - - - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected 'Watch (4)' but found '{1} ({2})'. - - - - The Watch App '{name}' does not specify a CFBundleExecutable - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKWatchKitApp key must be present and have a value of 'true'. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The Watch App '{0}' does not contain any Watch Extensions. - - - - The Watch App '{0}' does not contain a Watch Extension. - - The watchOS Application does not contain a watchOS extension, see: https://developer.apple.com/documentation/watchkit -{0} - The app bundle name, such as 'YourWatchOSApp.app' - - - The Watch Extension '{0}' does not contain an Info.plist. - - - - The Watch Extension '{0}' does not specify a CFBundleIdentifier. - - - - The Watch Extension '{0}' does not specify a CFBundleExecutable. - - - - The Watch Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The Watch Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionPointIdentifier must be "com.apple.watchkit". - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain an NSExtensionPointIdentifier. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain NSExtensionAttributes. - - - - The Watch Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the parent Watch App bundle's CFBundleIdentifier ('{2}'). - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionAttributes dictionary must contain a WKAppBundleIdentifier. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities dictionary should not contain the 'watch-companion' capability. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities array should not contain the 'watch-companion' capability. - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected '{1}' but found '{2} ({3})'. - - - - The Watch App '{0}' does not specify a CFBundleExecutable. - - - - The WatchKit Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the Watch App's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKCompanionAppBundleIdentifier must exist and must match the main app bundle's CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The app bundle {0} does not contain an Info.plist. - - - - {0} does not specify a CFBundleIdentifier. - - - - {0} does not specify a CFBundleExecutable. - - - - {0} does not specify a CFBundleSupportedPlatforms. - - - - {0} does not specify a UIDeviceFamily. - - - - {0} is invalid: the UIDeviceFamily key must contain a value for '{1}'. - - - - Unrecognized Type: {Type} - - - - Add: Entry, "{0}", Incorrectly Specified - - - - Add: Entry, "{0}", Contains Invalid Array Index - - - - Add: "{0}" Entry Already Exists - - - - Add: Can't Add Entry, "{0}", to Parent - - - - Delete: Can't Delete Entry, "{0}", from Parent - - - - Delete: Entry, "{0}", Contains Invalid Array Index - - - - Delete: Entry, "{0}", Does Not Exist - - - - Import: Entry, "{0}", Incorrectly Specified - - - - Import: Entry, "{0}", Contains Invalid Array Index - - - - Import: Error Reading File: {0} - - - - Import: Can't Add Entry, "{0}", to Parent - - - - Merge: Can't Add array Entries to dict - - Array entries in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), cannot be added to a dictionary. - - - Merge: Specified Entry Must Be a Container - - - - Merge: Entry, "{0}", Contains Invalid Array Index - - - - Merge: Entry, "{0}", Does Not Exist - - - - Merge: Error Reading File: {0} - - - - Set: Entry, "{0}", Incorrectly Specified - - - - Set: Entry, "{0}", Contains Invalid Array Index - - - - Set: Entry, "{0}", Does Not Exist - - - - Can't create a binding resource package unless there are native references in the binding project. - - - - Xamarin.iOS 14+ does not support watchOS 1 apps. Please migrate your project to watchOS 2+. - - - Invalid architecture ({0}): can't link more than one architecture at a time. - - - Unable to parse the AOT compiler arguments: {0} ({1}) - - AOT: Ahead-of-Time - {0}: The arguments that failed to parse - {1}: A more detailed description about the failure - - - - Invalid framework: {0} - - - Invalid platform: {0} - - - Package product requirement file contains architectures ({0}) which mismatches with target architectures ({1}) - - \ No newline at end of file diff --git a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.nl.resx b/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.nl.resx deleted file mode 100644 index c8764337c68b..000000000000 --- a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.nl.resx +++ /dev/null @@ -1,1017 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - Tool {0} execution started with arguments: {1} - - - - Tool {0} execution finished (exit code = {1}). - - - - Error executing tool '{0}': {1} - - - - Failed to codesign '{0}': {1} - - - - Failed to codesign '{0}' - - - - '{0}' not found. - - - - nl. - - - - Invalid iTunesArtwork dimensions ({0}x{1}) for '{2}'. - - - - Multiple iTunesArtwork files with the same dimensions detected ({0}x{1}) for '{2}'. - - - - Error loading '{0}': {1} - - - - Could not parse MinimumOSVersion value '{0}' - - - - Could not parse TargetArchitectures '{0}' - - - - The {0} SDK for '{1}' is not installed. - - - - The executable (CFBundleExecutable) name ({0}) cannot end with '.app', because iOS may fail to launch the app. - - - - Can only fake the watchOS 4.3 SDK when building for watchOS. - - - - All http loads are already allowed. - - - - Allowed arbitrary HTTP loads to support debugging. - - - - Supported iPhone orientations have not been set - - - - Supported iPhone orientations are not matched pairs - - The iPhone orientation settings do not match iPad, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Supported iPad orientations have not been set - - - - Supported iPad orientations are not matched pairs - - The iPad orientation settings do not match iPhone, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Cannot have more than 1 iTunesMetadata.plist. - - - - Error loading Settings plist file '{0}/Settings.bundle/Root.plist': {1}. - - - - Could not parse the SDK version '{0}' - - - - - - - - - - Could not locate SDK bin directory - - - - - - - - - - - - - - - Could not find a valid Xcode app bundle at '{0}'. Please update your Apple SDK location in Visual Studio's preferences {1}. - - The following are literal names and should not be translated: Xcode, Apple SDK, Visual Studio -{0} - The selected Xcode / Apple SDK directory. - - - Could not find valid a usable Xcode developer path - - - - Could not find '{0}' - - - - Searching for '{0}' in '{1}' - - - - Unknown SDK platform: {0} - - - - Could not locate the provisioning profile with a Name or UUID of {0}. - - - - Unknown search option: {0} - - - - Unknown native reference type for '{0}'. - - - - Dynamic native references are not supported: '{0}' - - - - Target architecture ARMv6 is no longer supported in Xamarin.iOS. Please select a supported architecture. - - - - Failed to create response file '{0}': {1} - - - - Could not load Info.plist: {0} - - - - Invalid architectures: '{0}'. - - - - Failed to parse the target device information. - - - - No target device found. - - - - No device architecture information found. - - - - Invalid target architecture: '{0}' - - - - No device operating system information found. - - - - No device model information found. - - - - No iOS version information found. - - - - Resources rules file '{0}' not found. - - - - Failed to parse SdkVersion '{0}'. - - - - Xcode 10 does not support watchOS 1 apps. Either upgrade to watchOS 2 apps, or use an older version of Xcode. - - - An installation of Xcode >= 6.2 is required to build WatchKit applications. - - - - iOS {0} does not support WatchKit. - - - - Failed to locate the WatchKit launcher in the Xcode app bundle. - - - - The App Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The App Extension '{0}' does not specify a CFBundleVersion - - - - The App Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The App Extension '{0}' has an unrecognized NSExtensionPointIdentifier value ('{1}'). - - - - The Watch App '{0}' does not specify a CFBundleShortVersionString - - - - The Watch App '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch App '{0}' does not specify a CFBundleVersion - - - - The Watch App '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleShortVersionString) - - - - The Watch Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleVersion - - - - The Watch Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - - Could not locate the {0} '{1}' SDK at path '{}' - - - - Could not locate the {0} '{1}' SDK usr path at '{2}' - - The provided SDK path is missing a 'usr' directory. The following are literal names and should not be translated: SDK, usr -{0} - The platform name, such as 'iOS'. -{1} - The version number of the SDK. -{2} - The file path of the SDK. - - - Could not find a valid Xcode developer path - - - - - - Unrecognized platform: {0} - - - - Asset not part of an asset catalog: {0} - - - - File not found: {0} - - - - Invalid json: {0} - - - - Partial Info.plist file was not generated: {0} - - - - Failed to load {0} log file `{1}`: {2} - - A general failure message if a log file wasn't able to be loaded. -{0} - The command-line tool that generated the log. -{1} - The file path to the log. -{2} - Further detail about the failure. - - - Failed to parse altool output: {0}. - Output: {1} - - - - - No API definition file specified. - - - - {0} failed. - - A general error message that a command-line tool failed. -{0} - The file path to the command-line tool. - - - Bundle Resource '{0}' not found on disk (should be at '{1}') - - - - The path '{0}' would result in a file outside of the app bundle and cannot be used. - - - - Info.plist files should have a Build Action of 'None'. - - - - The name '{0}' is reserved and cannot be used. - - - - Found a directory within the Frameworks directory which is not a framework: {0} - - - - The framework {0} does not contain a binary named {1} - - - - No Frameworks directory found. - - - - Could not determine value for manifest key '{0}' - - - - Error loading partial Info.plist template file '{0}': {1} - - - - Cannot expand $(TeamIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - Cannot expand $(AppIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - iCloud entitlements such as '{0}' require a Provisioning Profile. - - - - The iCloud entitlement '{0}' is not supported by the Provisioning Profile. - - - - Entitlements.plist template '{0}' not found. - - - - Error loading Entitlements.plist template '{0}': {1} - - - - Error writing xcent file '{0}': {1} - - - - Error writing archived-expanded-entitlements.xcent file: {0} - - - - Tool {0} execution finished. - - - - {0} exited with code {1} - - - - Skipping `{0}' as the output file, `{1}', is newer. - - Skipping a build operation, since the destination file is newer than the source file. -{0} - The destination file. -{1} - The source file. - - - Error saving `{0}': {1} - - - - Creating binding resource package: {0} - - - - Error loading '{0}' - - - - Package creation failed. Could not parse extra arguments. - - - - The identity '{0}' doesn't match any valid certificate/private key pair in the default keychain. - - A failure to sign the iOS application, due to a missing certificate/private key. Xcode has an identical error message, see: https://developer.apple.com/library/archive/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TNTAG40-WHAT_DOES__VALID_SIGNING_IDENTITY_NOT_FOUND__MEAN_AND_HOW_DO_I_RESOLVE_IT_ -{0} - The name of the identity, such as 'iPhone Developer'. - - - Detected signing identity: - - - - The certificate '{0}' does not match any of the prefixes '{1}'. - - - - The certificate '{0}' has expired ({1}) - - - - No valid {0} code signing keys found in keychain. You need to request a codesigning certificate from https://developer.apple.com. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. - - - The certificate '{0}' does not match '{1}'. - - - - {0} code signing key '{1}' not found in keychain. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The name of the code signing key, such as 'Apple Development'. - - - Could not find any available provisioning profiles for {0} on {1}. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The app bundle name, such as 'YouriOSApp.app' -{1} - The platform name, such as 'iOS'. - - - '{0}' doesn't match '{1}'. - - - - No installed provisioning profiles match the installed {0} {1} signing identities. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The app bundle name, such as 'YouriOSApp.app' - - - Finding matching provisioning profiles with compatible AppID, keeping only those with the longest matching (wildcard) IDs. - - - - AppID: {0} was ruled out because we found a better match: {1}. - - - - AppID: {0} was ruled out because we already found better matches: {1}. - - - - No installed provisioning profiles match the bundle identifier. - - - - Multiple provisioning profiles match the bundle identifier; using the first match. - - - - {0} does not define CFBundleIdentifier - - - - The specified {0} provisioning profile '{1}' could not be found - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The provisioning profile ID. A string such as: 'f35b0040-2be5-4b1c-a1d6-59ae85047fad' - - - Project bundle identifier '{0}' does not match specified provisioning profile '{1}' - - - - Multiple signing identities match '{0}'; using the first match. - - - - Multiple signing identities found; using the first identity. - - - - The specified {0} provisioning profile '{1}' could not be found - - - - No {0} signing identities match the specified provisioning profile '{1}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile. - - - - {0} found at: {1} - - A file was found at a location. -{0} - The '%(LogicalName)' of the file, or a relative path. -{1} - The location the file was found. - - - AssemblyPath cannot be null or empty - - - - Generated bundle name: {0} - - - - No property specified. - - - - The dictionary at '{0}' did not contain the key: {1} - - - - Could not parse array index: {0} - - - - Array index out of range for item '{0}' - - - - {0} values do not support child properties. - - The type of value in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), such as a number or string cannot contain child values. -{0} - The value type, such as 'NSString'. - - - Getting {0} values is not supported. - - - - The file '{0}' does not exist. - - - - The file '{0}' conflicts with '{1}'. - - - - Watch apps/extensions require Xcode 6.2 or later. The current Xcode version is {0} - - - - Items must have logical names computed. - - - - Duplicate Entry Was Skipped: {0} - - - - File Doesn't Exist, Will Create: {0} - - - - Creating directory '{0}' - - - - Copying file from '{0}' to '{1}' - - - - You must specify a DestinationFolder or the DestinationFiles, but not both. - - - - The number of DestinationFiles must match the number of SourceFiles. - - - - Skipping framework assembly: {0} - - - - Unknown target framework identifier: {0}. - - - - Could not find {0} in {1}. - - - - The {0} SDK is not installed. - - - - The {0} SDK version '{1}' is not installed, and no newer version was found. - - - - The {0} SDK version '{1}' is not installed. Using newer version '{2}' instead'. - - - - {0} has an incorrect or unknown format and cannot be processed. - - - - No matching framework found inside '{0}'. - - - - Conflicting '{0}' and '{1}' options. '{1}' will be ignored. - - - - Can't get an ISshCommands instance. Please check that a valid connection to the Mac is established. - - - An error occurred while trying to copy Archive '{0}' to '{1}'. Details: {2} - - - There is no available connection to the Mac. Task '{0}' will not be executed - - - Could not deserialize DataSet {0} - - - The file {0} does not have ImageAsset as build action. - - - Could not resolve UTI for {0} in catalog {1} - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS - - - The project was built with a version of Xcode ({0}) that is not compatible which may result in unexpected warnings or errors. Please install Xcode '{1}' or visit the documentation to learn more. - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS. Details: {0} - - - - The provided Archive Path is not from a valid archive file (.xcarchive). Archive Path: '{0}' - - - Could not map the macOS version {0} to a corresponding iOS version - - - Could not resolve host IPs for WiFi debugger settings. - - - - This machine does not have any network adapters. This is required when debugging or profiling on device over WiFi. - - - - The App Extension '{0}' does not contain an Info.plist. - - - - The App Extension '{0}' does not specify a CFBundleIdentifier. - - - - The App Extension '{0}' does not specify a CFBundleExecutable. - - - - The App Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The App Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The App Extension '{0}' does not specify a CFBundleShortVersionString. - - - - The App Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The App Extension '{0}' has an invalid Info.plist: the NSExtension dictionary does not contain an NSExtensionPointIdentifier value. - - - - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected 'Watch (4)' but found '{1} ({2})'. - - - - The Watch App '{name}' does not specify a CFBundleExecutable - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKWatchKitApp key must be present and have a value of 'true'. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The Watch App '{0}' does not contain any Watch Extensions. - - - - The Watch App '{0}' does not contain a Watch Extension. - - The watchOS Application does not contain a watchOS extension, see: https://developer.apple.com/documentation/watchkit -{0} - The app bundle name, such as 'YourWatchOSApp.app' - - - The Watch Extension '{0}' does not contain an Info.plist. - - - - The Watch Extension '{0}' does not specify a CFBundleIdentifier. - - - - The Watch Extension '{0}' does not specify a CFBundleExecutable. - - - - The Watch Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The Watch Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionPointIdentifier must be "com.apple.watchkit". - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain an NSExtensionPointIdentifier. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain NSExtensionAttributes. - - - - The Watch Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the parent Watch App bundle's CFBundleIdentifier ('{2}'). - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionAttributes dictionary must contain a WKAppBundleIdentifier. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities dictionary should not contain the 'watch-companion' capability. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities array should not contain the 'watch-companion' capability. - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected '{1}' but found '{2} ({3})'. - - - - The Watch App '{0}' does not specify a CFBundleExecutable. - - - - The WatchKit Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the Watch App's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKCompanionAppBundleIdentifier must exist and must match the main app bundle's CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The app bundle {0} does not contain an Info.plist. - - - - {0} does not specify a CFBundleIdentifier. - - - - {0} does not specify a CFBundleExecutable. - - - - {0} does not specify a CFBundleSupportedPlatforms. - - - - {0} does not specify a UIDeviceFamily. - - - - {0} is invalid: the UIDeviceFamily key must contain a value for '{1}'. - - - - Unrecognized Type: {Type} - - - - Add: Entry, "{0}", Incorrectly Specified - - - - Add: Entry, "{0}", Contains Invalid Array Index - - - - Add: "{0}" Entry Already Exists - - - - Add: Can't Add Entry, "{0}", to Parent - - - - Delete: Can't Delete Entry, "{0}", from Parent - - - - Delete: Entry, "{0}", Contains Invalid Array Index - - - - Delete: Entry, "{0}", Does Not Exist - - - - Import: Entry, "{0}", Incorrectly Specified - - - - Import: Entry, "{0}", Contains Invalid Array Index - - - - Import: Error Reading File: {0} - - - - Import: Can't Add Entry, "{0}", to Parent - - - - Merge: Can't Add array Entries to dict - - Array entries in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), cannot be added to a dictionary. - - - Merge: Specified Entry Must Be a Container - - - - Merge: Entry, "{0}", Contains Invalid Array Index - - - - Merge: Entry, "{0}", Does Not Exist - - - - Merge: Error Reading File: {0} - - - - Set: Entry, "{0}", Incorrectly Specified - - - - Set: Entry, "{0}", Contains Invalid Array Index - - - - Set: Entry, "{0}", Does Not Exist - - - - Can't create a binding resource package unless there are native references in the binding project. - - - - Xamarin.iOS 14+ does not support watchOS 1 apps. Please migrate your project to watchOS 2+. - - - Invalid architecture ({0}): can't link more than one architecture at a time. - - - Unable to parse the AOT compiler arguments: {0} ({1}) - - AOT: Ahead-of-Time - {0}: The arguments that failed to parse - {1}: A more detailed description about the failure - - - - Invalid framework: {0} - - - Invalid platform: {0} - - - Package product requirement file contains architectures ({0}) which mismatches with target architectures ({1}) - - \ No newline at end of file diff --git a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.pt-PT.resx b/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.pt-PT.resx deleted file mode 100644 index 109ec8972247..000000000000 --- a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.pt-PT.resx +++ /dev/null @@ -1,1017 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - Tool {0} execution started with arguments: {1} - - - - Tool {0} execution finished (exit code = {1}). - - - - Error executing tool '{0}': {1} - - - - Failed to codesign '{0}': {1} - - - - Failed to codesign '{0}' - - - - '{0}' not found. - - - - pt-PT. - - - - Invalid iTunesArtwork dimensions ({0}x{1}) for '{2}'. - - - - Multiple iTunesArtwork files with the same dimensions detected ({0}x{1}) for '{2}'. - - - - Error loading '{0}': {1} - - - - Could not parse MinimumOSVersion value '{0}' - - - - Could not parse TargetArchitectures '{0}' - - - - The {0} SDK for '{1}' is not installed. - - - - The executable (CFBundleExecutable) name ({0}) cannot end with '.app', because iOS may fail to launch the app. - - - - Can only fake the watchOS 4.3 SDK when building for watchOS. - - - - All http loads are already allowed. - - - - Allowed arbitrary HTTP loads to support debugging. - - - - Supported iPhone orientations have not been set - - - - Supported iPhone orientations are not matched pairs - - The iPhone orientation settings do not match iPad, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Supported iPad orientations have not been set - - - - Supported iPad orientations are not matched pairs - - The iPad orientation settings do not match iPhone, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Cannot have more than 1 iTunesMetadata.plist. - - - - Error loading Settings plist file '{0}/Settings.bundle/Root.plist': {1}. - - - - Could not parse the SDK version '{0}' - - - - - - - - - - Could not locate SDK bin directory - - - - - - - - - - - - - - - Could not find a valid Xcode app bundle at '{0}'. Please update your Apple SDK location in Visual Studio's preferences {1}. - - The following are literal names and should not be translated: Xcode, Apple SDK, Visual Studio -{0} - The selected Xcode / Apple SDK directory. - - - Could not find valid a usable Xcode developer path - - - - Could not find '{0}' - - - - Searching for '{0}' in '{1}' - - - - Unknown SDK platform: {0} - - - - Could not locate the provisioning profile with a Name or UUID of {0}. - - - - Unknown search option: {0} - - - - Unknown native reference type for '{0}'. - - - - Dynamic native references are not supported: '{0}' - - - - Target architecture ARMv6 is no longer supported in Xamarin.iOS. Please select a supported architecture. - - - - Failed to create response file '{0}': {1} - - - - Could not load Info.plist: {0} - - - - Invalid architectures: '{0}'. - - - - Failed to parse the target device information. - - - - No target device found. - - - - No device architecture information found. - - - - Invalid target architecture: '{0}' - - - - No device operating system information found. - - - - No device model information found. - - - - No iOS version information found. - - - - Resources rules file '{0}' not found. - - - - Failed to parse SdkVersion '{0}'. - - - - Xcode 10 does not support watchOS 1 apps. Either upgrade to watchOS 2 apps, or use an older version of Xcode. - - - An installation of Xcode >= 6.2 is required to build WatchKit applications. - - - - iOS {0} does not support WatchKit. - - - - Failed to locate the WatchKit launcher in the Xcode app bundle. - - - - The App Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The App Extension '{0}' does not specify a CFBundleVersion - - - - The App Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The App Extension '{0}' has an unrecognized NSExtensionPointIdentifier value ('{1}'). - - - - The Watch App '{0}' does not specify a CFBundleShortVersionString - - - - The Watch App '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch App '{0}' does not specify a CFBundleVersion - - - - The Watch App '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleShortVersionString) - - - - The Watch Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleVersion - - - - The Watch Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - - Could not locate the {0} '{1}' SDK at path '{}' - - - - Could not locate the {0} '{1}' SDK usr path at '{2}' - - The provided SDK path is missing a 'usr' directory. The following are literal names and should not be translated: SDK, usr -{0} - The platform name, such as 'iOS'. -{1} - The version number of the SDK. -{2} - The file path of the SDK. - - - Could not find a valid Xcode developer path - - - - - - Unrecognized platform: {0} - - - - Asset not part of an asset catalog: {0} - - - - File not found: {0} - - - - Invalid json: {0} - - - - Partial Info.plist file was not generated: {0} - - - - Failed to load {0} log file `{1}`: {2} - - A general failure message if a log file wasn't able to be loaded. -{0} - The command-line tool that generated the log. -{1} - The file path to the log. -{2} - Further detail about the failure. - - - Failed to parse altool output: {0}. - Output: {1} - - - - - No API definition file specified. - - - - {0} failed. - - A general error message that a command-line tool failed. -{0} - The file path to the command-line tool. - - - Bundle Resource '{0}' not found on disk (should be at '{1}') - - - - The path '{0}' would result in a file outside of the app bundle and cannot be used. - - - - Info.plist files should have a Build Action of 'None'. - - - - The name '{0}' is reserved and cannot be used. - - - - Found a directory within the Frameworks directory which is not a framework: {0} - - - - The framework {0} does not contain a binary named {1} - - - - No Frameworks directory found. - - - - Could not determine value for manifest key '{0}' - - - - Error loading partial Info.plist template file '{0}': {1} - - - - Cannot expand $(TeamIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - Cannot expand $(AppIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - iCloud entitlements such as '{0}' require a Provisioning Profile. - - - - The iCloud entitlement '{0}' is not supported by the Provisioning Profile. - - - - Entitlements.plist template '{0}' not found. - - - - Error loading Entitlements.plist template '{0}': {1} - - - - Error writing xcent file '{0}': {1} - - - - Error writing archived-expanded-entitlements.xcent file: {0} - - - - Tool {0} execution finished. - - - - {0} exited with code {1} - - - - Skipping `{0}' as the output file, `{1}', is newer. - - Skipping a build operation, since the destination file is newer than the source file. -{0} - The destination file. -{1} - The source file. - - - Error saving `{0}': {1} - - - - Creating binding resource package: {0} - - - - Error loading '{0}' - - - - Package creation failed. Could not parse extra arguments. - - - - The identity '{0}' doesn't match any valid certificate/private key pair in the default keychain. - - A failure to sign the iOS application, due to a missing certificate/private key. Xcode has an identical error message, see: https://developer.apple.com/library/archive/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TNTAG40-WHAT_DOES__VALID_SIGNING_IDENTITY_NOT_FOUND__MEAN_AND_HOW_DO_I_RESOLVE_IT_ -{0} - The name of the identity, such as 'iPhone Developer'. - - - Detected signing identity: - - - - The certificate '{0}' does not match any of the prefixes '{1}'. - - - - The certificate '{0}' has expired ({1}) - - - - No valid {0} code signing keys found in keychain. You need to request a codesigning certificate from https://developer.apple.com. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. - - - The certificate '{0}' does not match '{1}'. - - - - {0} code signing key '{1}' not found in keychain. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The name of the code signing key, such as 'Apple Development'. - - - Could not find any available provisioning profiles for {0} on {1}. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The app bundle name, such as 'YouriOSApp.app' -{1} - The platform name, such as 'iOS'. - - - '{0}' doesn't match '{1}'. - - - - No installed provisioning profiles match the installed {0} {1} signing identities. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The app bundle name, such as 'YouriOSApp.app' - - - Finding matching provisioning profiles with compatible AppID, keeping only those with the longest matching (wildcard) IDs. - - - - AppID: {0} was ruled out because we found a better match: {1}. - - - - AppID: {0} was ruled out because we already found better matches: {1}. - - - - No installed provisioning profiles match the bundle identifier. - - - - Multiple provisioning profiles match the bundle identifier; using the first match. - - - - {0} does not define CFBundleIdentifier - - - - The specified {0} provisioning profile '{1}' could not be found - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The provisioning profile ID. A string such as: 'f35b0040-2be5-4b1c-a1d6-59ae85047fad' - - - Project bundle identifier '{0}' does not match specified provisioning profile '{1}' - - - - Multiple signing identities match '{0}'; using the first match. - - - - Multiple signing identities found; using the first identity. - - - - The specified {0} provisioning profile '{1}' could not be found - - - - No {0} signing identities match the specified provisioning profile '{1}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile. - - - - {0} found at: {1} - - A file was found at a location. -{0} - The '%(LogicalName)' of the file, or a relative path. -{1} - The location the file was found. - - - AssemblyPath cannot be null or empty - - - - Generated bundle name: {0} - - - - No property specified. - - - - The dictionary at '{0}' did not contain the key: {1} - - - - Could not parse array index: {0} - - - - Array index out of range for item '{0}' - - - - {0} values do not support child properties. - - The type of value in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), such as a number or string cannot contain child values. -{0} - The value type, such as 'NSString'. - - - Getting {0} values is not supported. - - - - The file '{0}' does not exist. - - - - The file '{0}' conflicts with '{1}'. - - - - Watch apps/extensions require Xcode 6.2 or later. The current Xcode version is {0} - - - - Items must have logical names computed. - - - - Duplicate Entry Was Skipped: {0} - - - - File Doesn't Exist, Will Create: {0} - - - - Creating directory '{0}' - - - - Copying file from '{0}' to '{1}' - - - - You must specify a DestinationFolder or the DestinationFiles, but not both. - - - - The number of DestinationFiles must match the number of SourceFiles. - - - - Skipping framework assembly: {0} - - - - Unknown target framework identifier: {0}. - - - - Could not find {0} in {1}. - - - - The {0} SDK is not installed. - - - - The {0} SDK version '{1}' is not installed, and no newer version was found. - - - - The {0} SDK version '{1}' is not installed. Using newer version '{2}' instead'. - - - - {0} has an incorrect or unknown format and cannot be processed. - - - - No matching framework found inside '{0}'. - - - - Conflicting '{0}' and '{1}' options. '{1}' will be ignored. - - - - Can't get an ISshCommands instance. Please check that a valid connection to the Mac is established. - - - An error occurred while trying to copy Archive '{0}' to '{1}'. Details: {2} - - - There is no available connection to the Mac. Task '{0}' will not be executed - - - Could not deserialize DataSet {0} - - - The file {0} does not have ImageAsset as build action. - - - Could not resolve UTI for {0} in catalog {1} - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS - - - The project was built with a version of Xcode ({0}) that is not compatible which may result in unexpected warnings or errors. Please install Xcode '{1}' or visit the documentation to learn more. - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS. Details: {0} - - - - The provided Archive Path is not from a valid archive file (.xcarchive). Archive Path: '{0}' - - - Could not map the macOS version {0} to a corresponding iOS version - - - Could not resolve host IPs for WiFi debugger settings. - - - - This machine does not have any network adapters. This is required when debugging or profiling on device over WiFi. - - - - The App Extension '{0}' does not contain an Info.plist. - - - - The App Extension '{0}' does not specify a CFBundleIdentifier. - - - - The App Extension '{0}' does not specify a CFBundleExecutable. - - - - The App Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The App Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The App Extension '{0}' does not specify a CFBundleShortVersionString. - - - - The App Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The App Extension '{0}' has an invalid Info.plist: the NSExtension dictionary does not contain an NSExtensionPointIdentifier value. - - - - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected 'Watch (4)' but found '{1} ({2})'. - - - - The Watch App '{name}' does not specify a CFBundleExecutable - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKWatchKitApp key must be present and have a value of 'true'. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The Watch App '{0}' does not contain any Watch Extensions. - - - - The Watch App '{0}' does not contain a Watch Extension. - - The watchOS Application does not contain a watchOS extension, see: https://developer.apple.com/documentation/watchkit -{0} - The app bundle name, such as 'YourWatchOSApp.app' - - - The Watch Extension '{0}' does not contain an Info.plist. - - - - The Watch Extension '{0}' does not specify a CFBundleIdentifier. - - - - The Watch Extension '{0}' does not specify a CFBundleExecutable. - - - - The Watch Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The Watch Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionPointIdentifier must be "com.apple.watchkit". - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain an NSExtensionPointIdentifier. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain NSExtensionAttributes. - - - - The Watch Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the parent Watch App bundle's CFBundleIdentifier ('{2}'). - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionAttributes dictionary must contain a WKAppBundleIdentifier. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities dictionary should not contain the 'watch-companion' capability. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities array should not contain the 'watch-companion' capability. - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected '{1}' but found '{2} ({3})'. - - - - The Watch App '{0}' does not specify a CFBundleExecutable. - - - - The WatchKit Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the Watch App's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKCompanionAppBundleIdentifier must exist and must match the main app bundle's CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The app bundle {0} does not contain an Info.plist. - - - - {0} does not specify a CFBundleIdentifier. - - - - {0} does not specify a CFBundleExecutable. - - - - {0} does not specify a CFBundleSupportedPlatforms. - - - - {0} does not specify a UIDeviceFamily. - - - - {0} is invalid: the UIDeviceFamily key must contain a value for '{1}'. - - - - Unrecognized Type: {Type} - - - - Add: Entry, "{0}", Incorrectly Specified - - - - Add: Entry, "{0}", Contains Invalid Array Index - - - - Add: "{0}" Entry Already Exists - - - - Add: Can't Add Entry, "{0}", to Parent - - - - Delete: Can't Delete Entry, "{0}", from Parent - - - - Delete: Entry, "{0}", Contains Invalid Array Index - - - - Delete: Entry, "{0}", Does Not Exist - - - - Import: Entry, "{0}", Incorrectly Specified - - - - Import: Entry, "{0}", Contains Invalid Array Index - - - - Import: Error Reading File: {0} - - - - Import: Can't Add Entry, "{0}", to Parent - - - - Merge: Can't Add array Entries to dict - - Array entries in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), cannot be added to a dictionary. - - - Merge: Specified Entry Must Be a Container - - - - Merge: Entry, "{0}", Contains Invalid Array Index - - - - Merge: Entry, "{0}", Does Not Exist - - - - Merge: Error Reading File: {0} - - - - Set: Entry, "{0}", Incorrectly Specified - - - - Set: Entry, "{0}", Contains Invalid Array Index - - - - Set: Entry, "{0}", Does Not Exist - - - - Can't create a binding resource package unless there are native references in the binding project. - - - - Xamarin.iOS 14+ does not support watchOS 1 apps. Please migrate your project to watchOS 2+. - - - Invalid architecture ({0}): can't link more than one architecture at a time. - - - Unable to parse the AOT compiler arguments: {0} ({1}) - - AOT: Ahead-of-Time - {0}: The arguments that failed to parse - {1}: A more detailed description about the failure - - - - Invalid framework: {0} - - - Invalid platform: {0} - - - Package product requirement file contains architectures ({0}) which mismatches with target architectures ({1}) - - \ No newline at end of file diff --git a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.sv.resx b/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.sv.resx deleted file mode 100644 index b07263043fbc..000000000000 --- a/msbuild/Xamarin.Localization.MSBuild/TranslatedAssemblies/MSBStrings.sv.resx +++ /dev/null @@ -1,1017 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - Tool {0} execution started with arguments: {1} - - - - Tool {0} execution finished (exit code = {1}). - - - - Error executing tool '{0}': {1} - - - - Failed to codesign '{0}': {1} - - - - Failed to codesign '{0}' - - - - '{0}' not found. - - - - sv. - - - - Invalid iTunesArtwork dimensions ({0}x{1}) for '{2}'. - - - - Multiple iTunesArtwork files with the same dimensions detected ({0}x{1}) for '{2}'. - - - - Error loading '{0}': {1} - - - - Could not parse MinimumOSVersion value '{0}' - - - - Could not parse TargetArchitectures '{0}' - - - - The {0} SDK for '{1}' is not installed. - - - - The executable (CFBundleExecutable) name ({0}) cannot end with '.app', because iOS may fail to launch the app. - - - - Can only fake the watchOS 4.3 SDK when building for watchOS. - - - - All http loads are already allowed. - - - - Allowed arbitrary HTTP loads to support debugging. - - - - Supported iPhone orientations have not been set - - - - Supported iPhone orientations are not matched pairs - - The iPhone orientation settings do not match iPad, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Supported iPad orientations have not been set - - - - Supported iPad orientations are not matched pairs - - The iPad orientation settings do not match iPhone, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html - - - Cannot have more than 1 iTunesMetadata.plist. - - - - Error loading Settings plist file '{0}/Settings.bundle/Root.plist': {1}. - - - - Could not parse the SDK version '{0}' - - - - - - - - - - Could not locate SDK bin directory - - - - - - - - - - - - - - - Could not find a valid Xcode app bundle at '{0}'. Please update your Apple SDK location in Visual Studio's preferences {1}. - - The following are literal names and should not be translated: Xcode, Apple SDK, Visual Studio -{0} - The selected Xcode / Apple SDK directory. - - - Could not find valid a usable Xcode developer path - - - - Could not find '{0}' - - - - Searching for '{0}' in '{1}' - - - - Unknown SDK platform: {0} - - - - Could not locate the provisioning profile with a Name or UUID of {0}. - - - - Unknown search option: {0} - - - - Unknown native reference type for '{0}'. - - - - Dynamic native references are not supported: '{0}' - - - - Target architecture ARMv6 is no longer supported in Xamarin.iOS. Please select a supported architecture. - - - - Failed to create response file '{0}': {1} - - - - Could not load Info.plist: {0} - - - - Invalid architectures: '{0}'. - - - - Failed to parse the target device information. - - - - No target device found. - - - - No device architecture information found. - - - - Invalid target architecture: '{0}' - - - - No device operating system information found. - - - - No device model information found. - - - - No iOS version information found. - - - - Resources rules file '{0}' not found. - - - - Failed to parse SdkVersion '{0}'. - - - - Xcode 10 does not support watchOS 1 apps. Either upgrade to watchOS 2 apps, or use an older version of Xcode. - - - An installation of Xcode >= 6.2 is required to build WatchKit applications. - - - - iOS {0} does not support WatchKit. - - - - Failed to locate the WatchKit launcher in the Xcode app bundle. - - - - The App Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The App Extension '{0}' does not specify a CFBundleVersion - - - - The App Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The App Extension '{0}' has an unrecognized NSExtensionPointIdentifier value ('{1}'). - - - - The Watch App '{0}' does not specify a CFBundleShortVersionString - - - - The Watch App '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch App '{0}' does not specify a CFBundleVersion - - - - The Watch App '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleShortVersionString) - - - - The Watch Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2}) - - - - The Watch Extension '{0}' does not specify a CFBundleVersion - - - - The Watch Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2}) - - - - - Could not locate the {0} '{1}' SDK at path '{}' - - - - Could not locate the {0} '{1}' SDK usr path at '{2}' - - The provided SDK path is missing a 'usr' directory. The following are literal names and should not be translated: SDK, usr -{0} - The platform name, such as 'iOS'. -{1} - The version number of the SDK. -{2} - The file path of the SDK. - - - Could not find a valid Xcode developer path - - - - - - Unrecognized platform: {0} - - - - Asset not part of an asset catalog: {0} - - - - File not found: {0} - - - - Invalid json: {0} - - - - Partial Info.plist file was not generated: {0} - - - - Failed to load {0} log file `{1}`: {2} - - A general failure message if a log file wasn't able to be loaded. -{0} - The command-line tool that generated the log. -{1} - The file path to the log. -{2} - Further detail about the failure. - - - Failed to parse altool output: {0}. - Output: {1} - - - - - No API definition file specified. - - - - {0} failed. - - A general error message that a command-line tool failed. -{0} - The file path to the command-line tool. - - - Bundle Resource '{0}' not found on disk (should be at '{1}') - - - - The path '{0}' would result in a file outside of the app bundle and cannot be used. - - - - Info.plist files should have a Build Action of 'None'. - - - - The name '{0}' is reserved and cannot be used. - - - - Found a directory within the Frameworks directory which is not a framework: {0} - - - - The framework {0} does not contain a binary named {1} - - - - No Frameworks directory found. - - - - Could not determine value for manifest key '{0}' - - - - Error loading partial Info.plist template file '{0}': {1} - - - - Cannot expand $(TeamIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - Cannot expand $(AppIdentifierPrefix) in Entitlements.plist without a provisioning profile. - - - - iCloud entitlements such as '{0}' require a Provisioning Profile. - - - - The iCloud entitlement '{0}' is not supported by the Provisioning Profile. - - - - Entitlements.plist template '{0}' not found. - - - - Error loading Entitlements.plist template '{0}': {1} - - - - Error writing xcent file '{0}': {1} - - - - Error writing archived-expanded-entitlements.xcent file: {0} - - - - Tool {0} execution finished. - - - - {0} exited with code {1} - - - - Skipping `{0}' as the output file, `{1}', is newer. - - Skipping a build operation, since the destination file is newer than the source file. -{0} - The destination file. -{1} - The source file. - - - Error saving `{0}': {1} - - - - Creating binding resource package: {0} - - - - Error loading '{0}' - - - - Package creation failed. Could not parse extra arguments. - - - - The identity '{0}' doesn't match any valid certificate/private key pair in the default keychain. - - A failure to sign the iOS application, due to a missing certificate/private key. Xcode has an identical error message, see: https://developer.apple.com/library/archive/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TNTAG40-WHAT_DOES__VALID_SIGNING_IDENTITY_NOT_FOUND__MEAN_AND_HOW_DO_I_RESOLVE_IT_ -{0} - The name of the identity, such as 'iPhone Developer'. - - - Detected signing identity: - - - - The certificate '{0}' does not match any of the prefixes '{1}'. - - - - The certificate '{0}' has expired ({1}) - - - - No valid {0} code signing keys found in keychain. You need to request a codesigning certificate from https://developer.apple.com. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. - - - The certificate '{0}' does not match '{1}'. - - - - {0} code signing key '{1}' not found in keychain. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The name of the code signing key, such as 'Apple Development'. - - - Could not find any available provisioning profiles for {0} on {1}. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The app bundle name, such as 'YouriOSApp.app' -{1} - The platform name, such as 'iOS'. - - - '{0}' doesn't match '{1}'. - - - - No installed provisioning profiles match the installed {0} {1} signing identities. - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The app bundle name, such as 'YouriOSApp.app' - - - Finding matching provisioning profiles with compatible AppID, keeping only those with the longest matching (wildcard) IDs. - - - - AppID: {0} was ruled out because we found a better match: {1}. - - - - AppID: {0} was ruled out because we already found better matches: {1}. - - - - No installed provisioning profiles match the bundle identifier. - - - - Multiple provisioning profiles match the bundle identifier; using the first match. - - - - {0} does not define CFBundleIdentifier - - - - The specified {0} provisioning profile '{1}' could not be found - - A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys -{0} - The platform name, such as 'iOS'. -{1} - The provisioning profile ID. A string such as: 'f35b0040-2be5-4b1c-a1d6-59ae85047fad' - - - Project bundle identifier '{0}' does not match specified provisioning profile '{1}' - - - - Multiple signing identities match '{0}'; using the first match. - - - - Multiple signing identities found; using the first identity. - - - - The specified {0} provisioning profile '{1}' could not be found - - - - No {0} signing identities match the specified provisioning profile '{1}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'. - - - - Bundle identifier '{0}' does not match any installed provisioning profile. - - - - {0} found at: {1} - - A file was found at a location. -{0} - The '%(LogicalName)' of the file, or a relative path. -{1} - The location the file was found. - - - AssemblyPath cannot be null or empty - - - - Generated bundle name: {0} - - - - No property specified. - - - - The dictionary at '{0}' did not contain the key: {1} - - - - Could not parse array index: {0} - - - - Array index out of range for item '{0}' - - - - {0} values do not support child properties. - - The type of value in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), such as a number or string cannot contain child values. -{0} - The value type, such as 'NSString'. - - - Getting {0} values is not supported. - - - - The file '{0}' does not exist. - - - - The file '{0}' conflicts with '{1}'. - - - - Watch apps/extensions require Xcode 6.2 or later. The current Xcode version is {0} - - - - Items must have logical names computed. - - - - Duplicate Entry Was Skipped: {0} - - - - File Doesn't Exist, Will Create: {0} - - - - Creating directory '{0}' - - - - Copying file from '{0}' to '{1}' - - - - You must specify a DestinationFolder or the DestinationFiles, but not both. - - - - The number of DestinationFiles must match the number of SourceFiles. - - - - Skipping framework assembly: {0} - - - - Unknown target framework identifier: {0}. - - - - Could not find {0} in {1}. - - - - The {0} SDK is not installed. - - - - The {0} SDK version '{1}' is not installed, and no newer version was found. - - - - The {0} SDK version '{1}' is not installed. Using newer version '{2}' instead'. - - - - {0} has an incorrect or unknown format and cannot be processed. - - - - No matching framework found inside '{0}'. - - - - Conflicting '{0}' and '{1}' options. '{1}' will be ignored. - - - - Can't get an ISshCommands instance. Please check that a valid connection to the Mac is established. - - - An error occurred while trying to copy Archive '{0}' to '{1}'. Details: {2} - - - There is no available connection to the Mac. Task '{0}' will not be executed - - - Could not deserialize DataSet {0} - - - The file {0} does not have ImageAsset as build action. - - - Could not resolve UTI for {0} in catalog {1} - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS - - - The project was built with a version of Xcode ({0}) that is not compatible which may result in unexpected warnings or errors. Please install Xcode '{1}' or visit the documentation to learn more. - - - An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS. Details: {0} - - - - The provided Archive Path is not from a valid archive file (.xcarchive). Archive Path: '{0}' - - - Could not map the macOS version {0} to a corresponding iOS version - - - Could not resolve host IPs for WiFi debugger settings. - - - - This machine does not have any network adapters. This is required when debugging or profiling on device over WiFi. - - - - The App Extension '{0}' does not contain an Info.plist. - - - - The App Extension '{0}' does not specify a CFBundleIdentifier. - - - - The App Extension '{0}' does not specify a CFBundleExecutable. - - - - The App Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The App Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The App Extension '{0}' does not specify a CFBundleShortVersionString. - - - - The App Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The App Extension '{0}' has an invalid Info.plist: the NSExtension dictionary does not contain an NSExtensionPointIdentifier value. - - - - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected 'Watch (4)' but found '{1} ({2})'. - - - - The Watch App '{name}' does not specify a CFBundleExecutable - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKWatchKitApp key must be present and have a value of 'true'. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The Watch App '{0}' does not contain any Watch Extensions. - - - - The Watch App '{0}' does not contain a Watch Extension. - - The watchOS Application does not contain a watchOS extension, see: https://developer.apple.com/documentation/watchkit -{0} - The app bundle name, such as 'YourWatchOSApp.app' - - - The Watch Extension '{0}' does not contain an Info.plist. - - - - The Watch Extension '{0}' does not specify a CFBundleIdentifier. - - - - The Watch Extension '{0}' does not specify a CFBundleExecutable. - - - - The Watch Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}). - - - - The Watch Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key". - - - - The Watch Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionPointIdentifier must be "com.apple.watchkit". - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain an NSExtensionPointIdentifier. - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain NSExtensionAttributes. - - - - The Watch Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the parent Watch App bundle's CFBundleIdentifier ('{2}'). - - - - The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionAttributes dictionary must contain a WKAppBundleIdentifier. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities dictionary should not contain the 'watch-companion' capability. - - - - The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities array should not contain the 'watch-companion' capability. - - - - The Watch App '{0}' does not contain an Info.plist. - - - - The Watch App '{0}' does not specify a CFBundleIdentifier. - - - - The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected '{1}' but found '{2} ({3})'. - - - - The Watch App '{0}' does not specify a CFBundleExecutable. - - - - The WatchKit Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the Watch App's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}'). - - - - The Watch App '{0}' has an invalid Info.plist: the WKCompanionAppBundleIdentifier must exist and must match the main app bundle's CFBundleIdentifier. - - - - The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present. - - - - The app bundle {0} does not contain an Info.plist. - - - - {0} does not specify a CFBundleIdentifier. - - - - {0} does not specify a CFBundleExecutable. - - - - {0} does not specify a CFBundleSupportedPlatforms. - - - - {0} does not specify a UIDeviceFamily. - - - - {0} is invalid: the UIDeviceFamily key must contain a value for '{1}'. - - - - Unrecognized Type: {Type} - - - - Add: Entry, "{0}", Incorrectly Specified - - - - Add: Entry, "{0}", Contains Invalid Array Index - - - - Add: "{0}" Entry Already Exists - - - - Add: Can't Add Entry, "{0}", to Parent - - - - Delete: Can't Delete Entry, "{0}", from Parent - - - - Delete: Entry, "{0}", Contains Invalid Array Index - - - - Delete: Entry, "{0}", Does Not Exist - - - - Import: Entry, "{0}", Incorrectly Specified - - - - Import: Entry, "{0}", Contains Invalid Array Index - - - - Import: Error Reading File: {0} - - - - Import: Can't Add Entry, "{0}", to Parent - - - - Merge: Can't Add array Entries to dict - - Array entries in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), cannot be added to a dictionary. - - - Merge: Specified Entry Must Be a Container - - - - Merge: Entry, "{0}", Contains Invalid Array Index - - - - Merge: Entry, "{0}", Does Not Exist - - - - Merge: Error Reading File: {0} - - - - Set: Entry, "{0}", Incorrectly Specified - - - - Set: Entry, "{0}", Contains Invalid Array Index - - - - Set: Entry, "{0}", Does Not Exist - - - - Can't create a binding resource package unless there are native references in the binding project. - - - - Xamarin.iOS 14+ does not support watchOS 1 apps. Please migrate your project to watchOS 2+. - - - Invalid architecture ({0}): can't link more than one architecture at a time. - - - Unable to parse the AOT compiler arguments: {0} ({1}) - - AOT: Ahead-of-Time - {0}: The arguments that failed to parse - {1}: A more detailed description about the failure - - - - Invalid framework: {0} - - - Invalid platform: {0} - - - Package product requirement file contains architectures ({0}) which mismatches with target architectures ({1}) - - \ No newline at end of file diff --git a/msbuild/Xamarin.Localization.MSBuild/Xamarin.Localization.MSBuild.csproj b/msbuild/Xamarin.Localization.MSBuild/Xamarin.Localization.MSBuild.csproj index 31e55089793e..64b40c487db8 100644 --- a/msbuild/Xamarin.Localization.MSBuild/Xamarin.Localization.MSBuild.csproj +++ b/msbuild/Xamarin.Localization.MSBuild/Xamarin.Localization.MSBuild.csproj @@ -32,9 +32,6 @@ MSBStrings.fr.resx - - MSBStrings.hu.resx - MSBStrings.it.resx @@ -44,24 +41,15 @@ MSBStrings.ko.resx - - MSBStrings.nl.resx - MSBStrings.pl.resx MSBStrings.pt-BR.resx - - MSBStrings.pt-PT.resx - MSBStrings.ru.resx - - MSBStrings.sv.resx - MSBStrings.tr.resx diff --git a/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationIgnore/common-Translations.ignore b/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationIgnore/common-Translations.ignore index d1c65132be12..bc54b06ba3e2 100644 --- a/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationIgnore/common-Translations.ignore +++ b/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationIgnore/common-Translations.ignore @@ -1,5 +1,6 @@ # Insert Error codes that are waiting on translations below (one per line) -E0067 +E0174 +E0175 E0177 E0178 E0179 @@ -8,6 +9,7 @@ E0181 E0182 E0183 E0184 +E0185 E0186 E0187 E7069 @@ -16,3 +18,4 @@ E7071 InvalidFramework InvalidPlatform E7072 +W0176 diff --git a/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationStringTest.cs b/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationStringTest.cs index e3a88920a246..fb1af4786d5e 100644 --- a/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationStringTest.cs +++ b/tests/msbuild/Xamarin.MacDev.Tasks.Tests/TaskTests/LocalizationStringTest.cs @@ -19,16 +19,12 @@ public class LocalizationStringTest : TestBase { [TestCase ("en-US", "Unknown image format.")] [TestCase ("es-ES", "formato de imagen desconocido.")] [TestCase ("fr-FR", "format d'image inconnu.")] - [TestCase ("hu", "hu")] [TestCase ("it-IT", "Formato immagine sconosciuto.")] [TestCase ("ja-JP", "の読み込みでエラーが発生しました: 画像の形式が不明です。")] [TestCase ("ko-KR", "을(를) 로드하는 동안 오류 발생: 알 수 없는 이미지 형식입니다.")] - [TestCase ("nl", "nl")] [TestCase ("pl-PL", "nieznany format obrazu.")] [TestCase ("pt-BR", "formato de imagem desconhecido.")] - [TestCase ("pt-PT", "pt-PT")] [TestCase ("ru-RU", "неизвестный формат изображения.")] - [TestCase ("sv", "sv")] [TestCase ("tr-TR", "yüklenirken hata oluştu: Görüntü biçimi bilinmiyor.")] [TestCase ("zh-CN", "时出错: 未知图像格式")] [TestCase ("zh-TW", "時發生錯誤: 未知的映像格式。")] @@ -57,16 +53,12 @@ public void AllSupportedTranslations (string culture, string errorMessage) [TestCase ("de-DE")] [TestCase ("es-ES")] [TestCase ("fr-FR")] - [TestCase ("hu")] [TestCase ("it-IT")] [TestCase ("ja-JP")] [TestCase ("ko-KR")] - [TestCase ("nl")] [TestCase ("pl-PL")] [TestCase ("pt-BR")] - [TestCase ("pt-PT")] [TestCase ("ru-RU")] - [TestCase ("sv")] [TestCase ("tr-TR")] [TestCase ("zh-CN")] [TestCase ("zh-TW")] @@ -112,20 +104,15 @@ public void SetUp () [TestCase ("de-DE")] [TestCase ("es-ES")] [TestCase ("fr-FR")] - [TestCase ("hu")] [TestCase ("it-IT")] [TestCase ("ja-JP")] [TestCase ("ko-KR")] - [TestCase ("nl")] [TestCase ("pl-PL")] - [TestCase ("pt-PT")] [TestCase ("pt-BR")] [TestCase ("ru-RU")] - [TestCase ("sv")] [TestCase ("tr-TR")] [TestCase ("zh-CN")] [TestCase ("zh-TW")] - [Ignore ("OneLocBuild will return proper translated resx files.")] public void AllErrorTranslation (string culture) { StringBuilder errorList = new StringBuilder (string.Empty); diff --git a/tests/mtouch/LocalizationTests.cs b/tests/mtouch/LocalizationTests.cs index d7a83f2aa78e..eaf10af74521 100644 --- a/tests/mtouch/LocalizationTests.cs +++ b/tests/mtouch/LocalizationTests.cs @@ -16,16 +16,12 @@ public class LocalizationTests [TestCase ("de-DE")] [TestCase ("es-ES")] [TestCase ("fr-FR")] - [TestCase ("hu")] [TestCase ("it-IT")] [TestCase ("ja-JP")] [TestCase ("ko-KR")] - [TestCase ("nl")] - [TestCase ("pl")] + [TestCase ("pl-PL")] [TestCase ("pt-BR")] - [TestCase ("pt-PT")] [TestCase ("ru-RU")] - [TestCase ("sv")] [TestCase ("tr-TR")] [TestCase ("zh-CN")] [TestCase ("zh-TW")] @@ -72,16 +68,12 @@ private string TranslateError (string culture, string errorCode) [TestCase ("de-DE")] [TestCase ("es-ES")] [TestCase ("fr-FR")] - [TestCase ("hu")] [TestCase ("it-IT")] [TestCase ("ja-JP")] [TestCase ("ko-KR")] - [TestCase ("nl")] - [TestCase ("pl")] + [TestCase ("pl-PL")] [TestCase ("pt-BR")] - [TestCase ("pt-PT")] [TestCase ("ru-RU")] - [TestCase ("sv")] [TestCase ("tr-TR")] [TestCase ("zh-CN")] [TestCase ("zh-TW")] diff --git a/tools/devops/LocProject.json.in b/tools/devops/LocProject.json.in index a6afada924ef..d835e662d6b1 100644 --- a/tools/devops/LocProject.json.in +++ b/tools/devops/LocProject.json.in @@ -1,7 +1,7 @@ { "Projects": [ { - "LanguageSet": "Azure_Languages", + "LanguageSet": "VS_Main_Languages", "LocItems": [ { "SourceFile": "@WORKING_DIRECTORY@/../../msbuild/Xamarin.Localization.MSBuild/MSBStrings.resx", diff --git a/tools/dotnet-linker/dotnet-linker.csproj b/tools/dotnet-linker/dotnet-linker.csproj index 1f29704a0966..e1fb81a5e5b4 100644 --- a/tools/dotnet-linker/dotnet-linker.csproj +++ b/tools/dotnet-linker/dotnet-linker.csproj @@ -224,10 +224,6 @@ tools\mtouch\Errors.fr.resx Errors.mtouch.fr - - tools\mtouch\Errors.hu.resx - Errors.mtouch.hu - tools\mtouch\Errors.it.resx Errors.mtouch.it @@ -240,10 +236,6 @@ tools\mtouch\Errors.ko.resx Errors.mtouch.ko - - tools\mtouch\Errors.nl.resx - Errors.mtouch.nl - tools\mtouch\Errors.pl.resx Errors.mtouch.pl @@ -252,18 +244,10 @@ tools\mtouch\Errors.pt-BR.resx Errors.mtouch.pt-BR - - tools\mtouch\Errors.pt-PT.resx - Errors.mtouch.pt-PT - tools\mtouch\Errors.ru.resx Errors.mtouch.ru - - tools\mtouch\Errors.sv.resx - Errors.mtouch.sv - tools\mtouch\Errors.tr.resx Errors.mtouch.tr diff --git a/tools/mmp/mmp.csproj b/tools/mmp/mmp.csproj index 214de2cffdea..9dd4a4d19313 100644 --- a/tools/mmp/mmp.csproj +++ b/tools/mmp/mmp.csproj @@ -510,10 +510,6 @@ tools\mtouch\Errors.fr.resx Errors.mtouch.fr - - tools\mtouch\Errors.hu.resx - Errors.mtouch.hu - tools\mtouch\Errors.it.resx Errors.mtouch.it @@ -526,10 +522,6 @@ tools\mtouch\Errors.ko.resx Errors.mtouch.ko - - tools\mtouch\Errors.nl.resx - Errors.mtouch.nl - tools\mtouch\Errors.pl.resx Errors.mtouch.pl @@ -538,18 +530,10 @@ tools\mtouch\Errors.pt-BR.resx Errors.mtouch.pt-BR - - tools\mtouch\Errors.pt-PT.resx - Errors.mtouch.pt-PT - tools\mtouch\Errors.ru.resx Errors.mtouch.ru - - tools\mtouch\Errors.sv.resx - Errors.mtouch.sv - tools\mtouch\Errors.tr.resx Errors.mtouch.tr diff --git a/tools/mtouch/TranslatedAssemblies/Errors.hu.resx b/tools/mtouch/TranslatedAssemblies/Errors.hu.resx deleted file mode 100644 index d06ff4df1cf2..000000000000 --- a/tools/mtouch/TranslatedAssemblies/Errors.hu.resx +++ /dev/null @@ -1,1700 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - The error message for code {0} could not be found. Please report this missing message on GitHub at https://github.com/xamarin/xamarin-macios/issues/new - - This is the default message when an error code can not be found. - - - - Unexpected error - Please fill a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - '-devname' was provided without any device-specific action - - - - This version of Xamarin.Mac requires Mono {0} (the current Mono version is {1}). Please update the Mono.framework from http://mono-project.com/Downloads - - - - Could not parse the environment variable '{0}' - - - - Application name '{0}.exe' conflicts with an SDK or product assembly (.dll) name. - - - - New refcounting logic requires SGen to be enabled too. - - - - The output directory * does not exist. - - - - There is no devel platform at {0}, use --platform=PLAT to specify the SDK. - - - - The root assembly '{0}' does not exist - - - - You should provide one root assembly only, found {0} assemblies: '{1}' - - - - Error while loading assemblies: {0}. - - - - Could not parse the command line arguments: {0} - - - - {0} was built against a more recent runtime ({1}) than Xamarin.iOS supports. - - - - Incomplete data is provided to complete *. - - - - Profiling support requires sgen to be enabled too. - - - - The iOS {0} SDK does not support building applications targeting {1}. - - - - This is the hu MT0015 error message. - - - - The option '{0}' has been deprecated. - - - - You should provide a root assembly. - - - - Unknown command line argument: '{0}' - - - - Only one --[log|install|kill|launch]dev or --[launch|debug]sim option can be used. - - - - The valid options for '{0}' are '{1}'. - - - - 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). - - - - The options '--unsupported--enable-generics-in-registrar' and '--registrar' are not compatible. - - - - The root assembly {0} conflicts with another assembly ({1}). - - - - Application name '{0}.exe' conflicts with another user assembly. - - - - Could not find required file '{0}'. - - - - No SDK version was provided. Please add --sdk=X.Y to specify which {0} SDK should be used to build your application. - - - - Could not parse the command line argument '-{0}': {1} - - - - The options '\*' and '\*' are not compatible. - - - - 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 - - - - REPL (--enable-repl) is only supported in the simulator (--sim). - - - - The executable name ({0}) and the app name ({1}) are different, this may prevent crash logs from getting symbolicated properly. - - - - The command line arguments '--enable-background-fetch' and '--launch-for-background-fetch' require '--launchsim' too. - - - - The option '--debugtrack' is ignored unless '--debug' is also specified. - - - - A Xamarin.iOS project must reference either monotouch.dll or Xamarin.iOS.dll - - - - Cannot reference '{0}.dll' in a {1} project - it is implicitly referenced by '{2}'. - - - - Cannot launch a * simulator for a * app. Please enable the correct architecture(s) in your project's iOS Build options (Advanced page). - - - - 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). - - - - The old registrars (--registrar:oldstatic|olddynamic) are not supported when referencing Xamarin.iOS.dll. - - - - Applications targeting ARMv6 cannot reference Xamarin.iOS.dll. - - - - Could not find the assembly '\*', referenced by '\*'. - - - - Cannot reference '{0}' in a {1} app. - - - - No reference to either monotouch.dll or Xamarin.iOS.dll was found. A reference to monotouch.dll will be added. - - - - The Boehm garbage collector is not supported. The SGen garbage collector has been selected instead. - - - - --listsim is only supported with Xcode 6.0 or later. - - - - --extension is only supported when using the iOS 8.0 (or later) SDK. - - - - 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. - - - - {0}.framework is supported only if deployment target is 8.0 or later. {0} features might not work correctly. - - - - You cannot provide a root assembly if --no-root-assembly is passed, found {0} assemblies: '{1}' - - - - {3} {0} requires Xcode {4} or later. The current Xcode version (found in {2}) is {1}. - - - - An output directory (--output) is required if --no-root-assembly is passed. - - - - No command specified. - - - - Unable to canonicalize the path '{0}': {1} ({2}). - - - - The Xcode path '{0}' does not exist. - - - - Cannot find Xcode in the default location (/Applications/Xcode.app). Please install Xcode, or pass a custom path using --sdkroot <path>. - - - - Cannot determine the path to Xcode.app from the sdk root '{0}'. Please specify the full path to the Xcode.app bundle. - - - - The Xcode.app '{0}' is invalid (the file '{1}' does not exist). - - - - Could not find the currently selected Xcode on the system: {0} - - - - Could not find the currently selected Xcode on the system. 'xcode-select --print-path' returned '{0}', but that directory does not exist. - - - - No Xcode.app specified (using --sdkroot), using the system Xcode as reported by 'xcode-select --print-path': {0} - - - - No Xcode.app specified (using --sdkroot or 'xcode-select --print-path'), using the default Xcode instead: {0} - - - - Cannot find the executable in the extension * (no CFBundleExecutable entry in its Info.plist) - - - - Xamarin.iOS only supports embedded frameworks with Unified projects. - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 8.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 2.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Invalid build registrar assembly: * - - - - Invalid registrar: {0} - - - - Invalid value for target framework: {0}. - - - - Invalid target framework: {0}. Valid target frameworks are: {1}. - - - - Unknown platform: {0}. This usually indicates a bug in {1}; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Extensions are not supported for the platform '{0}'. - - - - {4} {0} does not support a deployment target of {1} for {3} (the minimum is {2}). Please select a newer deployment target in your project's Info.plist. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The minimum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - {4} {0} does not support a deployment target of {1} for {3} (the maximum is {2}). Please select an older deployment target in your project's Info.plist or upgrade to a newer version of {4}. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The maximum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - Invalid architecture '{0}' for {1} projects. Valid architectures are: {2} - - - - No architecture specified (using the --abi argument). An architecture is required for {0} projects. - - - - WatchOS projects must be extensions. - - - - Incremental builds are enabled with a deployment target < 8.0 (currently {0}). This is not supported (the resulting application will not launch on iOS 9), so the deployment target will be set to 8.0. - - - - The recommended Xcode version for {4} {0} is Xcode {3} or later. The current Xcode version (found in {2}) is {1}. - - - - No executable was copied into the app bundle. Please contact 'support@xamarin.com' - - - - Disabling the new refcount logic is deprecated. - - - - The command line argument --download-crash-report also requires --download-crash-report-to. - - - - REPL (--enable-repl) is only supported when linking is not used (--nolink). - - - - Asm-only bitcode is not supported on watchOS. Use either --bitcode:marker or --bitcode:full. - - - - Bitcode is not supported in the simulator. Do not pass --bitcode when building for the simulator. - - - - No reference to '{0}' was found. It will be added automatically. - - - - A target framework (--target-framework) must be specified. - - - - Incremental builds (--fastdev) is not supported with the Boehm GC. Incremental builds will be disabled. - - - - The GC must be in cooperative mode for watchOS apps. Please remove the --coop:false argument to mtouch. - - - - The option '{0}' cannot take the value '{1}' when cooperative mode is enabled for the GC. - - - - The target framework '{0}' is deprecated. Use '{1}' instead. - - - - - - Could not find 'mlaunch'. - - - - - Aot files could not be copied to the destination directory {0}: {1} - - - - Aot files could not be copied to the destination directory {0}: Could not start process. - - - - Aot files could not be copied to the destination directory {0} - - - - No reference to Xamarin.iOS.dll was found. - - - - machine.config file '{0}' can not be found. - - - - - Internal error: {0}. Please file an issue at https://github.com/xamarin/xamarin-macios/issues/new. - - - - Invalid assembly build target: '{0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly '{0}' is specified multiple times in --assembly-build-target arguments. - - - - The assemblies '{0}' and '{1}' have the same target name ('{2}'), but different targets ('{3}' and '{4}'). - - - - The static object '{0}' contains more than one assembly ('{1}'), but each static object must correspond with exactly one assembly. - - - - No assembly build target was specified for '{0}'. - - - - The assembly build target name '{0}' is invalid: the character '{1}' is not allowed. - - - - The assemblies '{0}' have different custom LLVM optimizations ('{1}'), which is not allowed when they are all compiled to a single binary. - - - - The assembly build target '{0}' did not match any assemblies. - - - - The assembly '{0}' was loaded from a different path than the provided path (provided path: {1}, actual path: {2}). - - - - 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. - - - - Bitcode has been enabled because this version of Xamarin.iOS does not support building watchOS projects using LLVM without enabling bitcode. - - - - Native code sharing has been disabled because {0} - - - - the container app's deployment target is earlier than iOS 8.0 (it's {0}). - - - - the container app includes I18N assemblies ({0}). - - - - the container app has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - Native code sharing has been disabled for the extension '{0}' because {1} - - - - the bitcode options differ between the container app ({0}) and the extension ({1}). - - - - the --assembly-build-target options are different between the container app ({0}) and the extension ({1}). - - - - the I18N assemblies are different between the container app ({0}) and the extension ({1}). - - - - the arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - the other arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - LLVM is not enabled or disabled in both the container app ({0}) and the extension ({1}). - - - - the managed linker settings are different between the container app ({0}) and the extension ({1}). - - - - the skipped assemblies for the managed linker are different between the container app ({0}) and the extension ({1}). - - - - the extension has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - the interpreter settings are different between the container app ({0}) and the extension ({1}). - - - - the interpreted assemblies are different between the container app ({0}) and the extension ({1}). - - - - the container app does not build for the ABI {0} (while the extension is building for this ABI). - - - - the container app is building for the ABI {0}, which is not compatible with the extension's ABI ({1}). - - - - the remove-dynamic-registrar optimization differ between the container app ({0}) and the extension ({1}). - - - - the container app is referencing the assembly '{0}' from '{1}', while the extension references a different version from '{2}'. - - - - Hybrid AOT compilation requires all assemblies to be AOT compiled - - - - It is recommended to reference dynamic symbols using code (--dynamic-symbol-mode=code) when bitcode is enabled. - - - - Invalid architecture: {0}. 32-bit architectures are not supported when deployment target is 11 or later. - - - - Can't launch a 32-bit app on a simulator that only supports 64-bit. - - - - The directory {0} containing the mono symbols could not be found. - - - - The executable assembly {0} does not reference {1}.dll. - - - - Could not set the current language to '{0}' (according to LANG={1}): {2} - - - - The --assembly-build-target command-line argument is ignored in the simulator. - - - - Incremental builds have been disabled because incremental builds are not supported in the simulator. - - - - 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. - - - - Could not touch the file '{0}': {1} - - - - Debugging symbol file for '{0}' does not match the assembly and is ignored. - - - - No root assemblies found. You should provide at least one root assembly. - - - - Product assembly '{0}' not found in assembly list: '{1}' - - - - Unknown optimization: '{0}'. Valid optimizations are: {1}. - - - - Found more than 1 assembly matching '{0}' choosing first:{1}{2} - - - - 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. - - - - Cannot find the assembly '{0}' referenced from '{1}'. - - - - Cannot find the assembly '{0}', referenced by a {2} attribute in '{1}'. - - - - File '{0}' is not a valid framework. - - - - The interpreter is not supported in the simulator. Switching to REPL which provide the same extra features on the simulator. - - - - Cannot find the assembly '{0}', passed as an argument to --interpreter. - - - - Projects using the Classic API are not supported anymore. Please migrate the project to the Unified API. - - - - Building 32-bit apps is not supported anymore. Please change the architecture in the project's Mac Build options to 'x86_64'. - - - - Please use device specific builds on WatchOS when building for Debug. - - - - ARM64_32 Debug mode requires --interpreter[=all], forcing it. - - - - Unable to parse the cflags '{0} from pkg-config: {1} - - - - Unable to parse the linker flags '{0}' from the LinkWith attribute for the library '{1}' in {2} : {3} - - - - Internal error: The interpreter is currently only available for 64 bits. - - - - Internal error: byref array is neither string, NSObject or INativeObject. - - - - Internal error: can't convert from '{0}' to '{1}' in {2}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the smart enum {0} doesn't seem to be a smart enum after all. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: unsupported tokentype ({0}) for {1}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the static registrar should not execute unless the linker also executed (or was disabled). A potential workaround is to pass '-f' as an additional {0} argument to force a full build. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: symbol without a name (type: {0}). Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: 'can't convert frameworks to frameworks: {0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly {0} was referenced by another assembly, but at the same time linked out by the linker. - - - - The linker output contains more than one assemblies named '{0}':\n\t{1} - - - - Not all assemblies for {0} have link tasks - - - - Link tasks for {0} aren't all the same - - - - The assembly '{0}' was resolved from the system's GAC: {1}. This could potentially be a problem in the future; to avoid such problems, please make sure to not use assemblies only available in the system's GAC. - - - - Unknown platform: {0}. This usually indicates a bug; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - Debugging symbol file for '{0}' is not valid and was ignored. - - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or use the dynamic registrar or set the managed linker behaviour to Link Platform or Link Framework SDKs Only in your project's Mac Build Options > Linker Behavior (to try to avoid the new APIs). - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or set the managed linker behaviour to Link Framework SDKs Only in your project's iOS Build Options > Linker Behavior (to try to avoid the new APIs). - - - Not linking with the framework {0} (used by the type {1}) because it's not available on the current platform ({2}). - - - Not linking with the framework {0} (referenced by a module reference in {1}) because it's not available on the current platform ({2}). - - - Could not map the iOS version {0} to a macOS version for Mac Catalyst - - - Could not map the macOS version {0} to a corresponding iOS version for Mac Catalyst - - - Could not copy the assembly '{0}' to '{1}': {2} - - - - Could not load the assembly '{0}': {1} - - - - Dependency tracking error: no files to compare. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Failed to re-use cached version of '{0}': {1}. - - - - Failed to create the executable '{0}': {1} - - - - Could not copy the directory '{0}' to '{1}': {2} - - - - Could not create symlink '{0}' -> '{1}': error {2} - - - - Cannot include different versions of the framework '{0}' - - - - Framework '{0}' included from: {1} (Related to previous error) - - - - Unsupported bitcode platform: {0}. - - - - Unsupported TvOS ABI: {0}. - - - - Could not extract the native library '{0}' from '{1}'. 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'). - - - - Invalid escape sequence when converting .s to .ll, \\ as the last characted in {0}:{1}. - - - - Invalid escape sequence when converting .s to .ll, bad octal escape in {0}:{1} due to {2}. - - - - Could not decompress the native framework '{0}' from '{1}'. Please review the build log for more information from the native 'unzip' command. - - - - The binding library '{0}' contains a user framework ({0}), but embedded user frameworks require iOS 8.0 (the deployment target is {1}). Please set the deployment target in the Info.plist file to at least 8.0. - - - - The required 'Xamarin.Mac.dll' assembly is missing from the references - - - - The assembly '{0}' is not compatible with this tool or profile - - - - {0} {1} could not be found. Target framework '{2}' is unusable to package the application. - - - - Target framework '{0}' is invalid. - - - - useFullXamMacFramework must always target framework .NET 4.5, not '{0}' which is invalid. - - - - Mismatch between Xamarin.Mac reference '{0}' and target framework selected '{1}'. - - - - Can not resolve reference: {0} - - - - One or more reference(s) to type '{0}' already exists inside '{1}' before linking - - - - One or more reference(s) to type '{0}' still exists inside '{1}' after linking - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Not a Mach-O static library (unknown header '{0}', expected '!<arch>'). - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Unknown format for fat entry at position {0} in {1}. - - - - File of type {0} is not a MachO file ({1}). - - - - Invalid entry '{0}' in the static library '{1}', entry header doesn't end with 0x60 0x0A (found '0x{2} 0x{3}') - - - - Could not link assemblies. {0} - - - - Can not resolve reference: {0} - - - - Option '--optimize={0}{1}' will be ignored since the static registrar is not enabled - - - - - Option '--optimize={0}{1}' will be ignored since linking is disabled - - - - Option '--optimize={0}' will be ignored since it's only applicable to {1}. - This is a warning that is shown when the command-line option --optimize=... is not valid for a particular platform -{0} - The optimization option that is not valid for the current platform -{1} - The platforms in question, such as 'iOS'. - - - - Extra linker definitions file '{0}' could not be located. - - - - Definitions from '{0}' could not be parsed. - - - - Can not load mscorlib.dll from: '{0}'. Please reinstall Xamarin.iOS. - - - - Native library '{0}' was referenced but could not be found. - - - - Failed to resolve "{0}" reference from "{1}" - - - - Xamarin.Mac Unified API against a full .NET framework does not support linking SDK or All assemblies. Pass either the `-nolink` or `-linkplatform` flag. - - Using the linker is not supported in certain situations in Xamarin.Mac, see: https://docs.microsoft.com/xamarin/mac/deploy-test/linker. The following are literal names and should not be translated: Xamarin.Mac Unified API, .NET, SDK, All, `-nolink`, and `-linkplatform`. - - - - Referenced by {0}.{1} - - - - Unknown HttpMessageHandler `{0}`. Valid values are HttpClientHandler (default), CFNetworkHandler or NSUrlSessionHandler - - - - Only first {0} of {1} \"Referenced by\" warnings shown. - - - - Failed to resolve the reference to \"{0}\", referenced in \"{1}\". The app will not include the referenced assembly, and may fail at runtime. - - - - Unable to link assembly '{0}' as it is mixed-mode. - - - - Invalid HttpMessageHandler `{0}` for watchOS. The only valid value is NSUrlSessionHandler. - - - - Could not process XML description: {0} - - - - The assembly '{0}' is referenced from two different locations: '{1}' and '{2}'. - - - - Can not load the root assembly '{0}'. - - - - - The linker step '{0}' failed processing `{1}`. - This is a message when processing an assembly/type/field/method/property/event fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly/type/field/method/property/event that failed processing. - - - - - - - - - - - - Can't resolve the reference '{0}', referenced from the method '{1}' in '{2}'. - - - - Error processing the method '{0}' in the assembly '{1}': {2} - - - - Error processing the method '{0}' in the assembly '{1}' - - - - Error processing assembly '{0}': {1} - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect fields. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect properties. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a '{1}' parameter type (expected 'ObjCRuntime.BindingImplOptions). - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a {1} parameters (expected 1 parameters). - - - - The property {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This property will throw an exception if called. - - - - The method {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This method will throw an exception if called. - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because the previous instruction was unexpected ({3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because could not determine the type of the delegate type of the first argument (instruction: {3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} because the type of the value passed as the first argument (the trampoline) is {1}, which makes it impossible to compute the block signature. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1} because no [UserDelegateType] attribute could be found on {2}. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1}: {2}. - - - - It's not safe to remove the dynamic registrar, because {0} references '{1}.{2} ({3})'. - - - - {0} was stripped of architectures except {1} to comply with App Store restrictions. This could break existing codesigning signatures. Consider stripping the library with lipo or disabling with --optimize=-trim-architectures - - - - Xamarin.Mac 'Partial Static' registrar does not support linking. Disable linking or use another registrar mode. - - - - Can not find the corlib assembly '{0}' in the list of loaded assemblies. - - - - - - - - - - - The linker step '{0}' failed during processing: {1} - This is a message when processing fails in the linker. - {0} - The name of the step that fails. - {1} - A string describing what failed. - - - - The linker step '{0}' failed while processing {1}: {2} - This is a message when processing an assembly fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly that failed processing. - {1} - A string describing what failed - - - - - - - - - - - Could not {0} the assembly '{1}' - - - - Debugging is not supported when building with LLVM. Debugging has been disabled. - - - - Could not AOT the assembly '{0}' because it doesn't exist. - - - - The dependency '{0}' of the assembly '{1}' was not found. Please review the project's references. - - - - 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. - - - - Debug info files (*.mdb / *.pdb) will not be loaded when llvm is enabled. - - - - Bitcode support requires the use of LLVM (--abi=arm64+llvm etc.) - - - - AOT of '{0}' was requested but was not found - - - - Exclusion of AOT of '{0}' was requested but was not found - - - - The main template could not be expanded to `{0}`. - - - - Failed to compile the generated code for P/Invoke methods. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot build a signature for type `{0}`. - - - - The registrar found an invalid type `{0}` in signature for method `{2}`. Use `{1}` instead. - - - - The registrar found an invalid type `{0}` in signature for method `{1}`: The type implements INativeObject, but does not have a constructor that takes two (IntPtr, bool) arguments. - - - - The registrar cannot marshal the return value for type `{0}` in signature for method `{1}`. - - - - The registrar cannot marshal the return value of type `{0}` in the method `{1}.{2}`. - - - - The registrar cannot marshal the parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot get the ObjectiveC type for managed type `{0}`. - - - - Failed to compile the generated registrar code. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot marshal the out parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot build a signature for type `{0}' in method `{1}`. - - - - The registrar found a generic method: '{0}'. Exporting generic methods is not supported, and will lead to random behavior and/or crashes - - - - Unexpected error in the registrar for the method '{0}.{1}' - Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not register the assembly '{0}': {1} - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register two managed types ('{0}' and '{1}') with the same native name ('{2}'). - - - - Could not register the selector '{0}' of the member '{1}.{2}' because the selector is already registered on the member '{3}'. - - - - The registrar found an unknown field type '{0}' in field '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - 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). - - - - The type of the variadic parameter in the variadic function '{0}' must be System.IntPtr. - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid RegisterAttribute property {1} found on '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid AdoptsAttribute found on '{0}': expected 1 constructor arguments, got {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}.{1}': unknown field {2}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid {0} found on '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': should have 1 constructor arguments, found {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': could not find the underlying enum type of {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found an invalid type '{0}' in signature for method '{1}': The interface must have a Protocol attribute specifying its wrapper type. - - - - Cannot register two managed protocols ('{0}' and '{1}') with the same native name ('{2}'). - - - - Cannot register more than one interface method for the method '{0}.{1}'. - - - - The registrar found an invalid generic parameter type '{0}' in the parameter {2} of the method '{1}'. The generic parameter must have an 'NSObject' constraint. - - - - The registrar found an invalid generic return type '{0}' in the method '{1}'. The generic return type must have an 'NSObject' constraint. - - - - The registrar cannot export static methods in generic classes ('{0}'). - - - - The registrar cannot export static properties in generic classes ('{0}.{1}'). - - - - The registrar found an invalid generic return type '{0}' in the property '{1}.{2}'. The return type must have an 'NSObject' constraint. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) Please select a newer SDK in your app's {3} Build options. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) This configuration is not supported with the static registrar (pass --registrar:dynamic as an additional mmp argument in your project's Mac Build option to select). Alternatively select a newer SDK in your app's Mac Build options. - - - - The member '{0}' has an Export attribute without a selector. A selector is required. - - - - The registrar cannot marshal the parameter type '{0}' of the parameter '{1}' in the method '{2}.{3}' - - - - The method '{0}.{1}' is implementing '{2}.{3}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. Properties with the [Connect] attribute must have a property type of NSObject (or a subclass of NSObject). - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the variadic method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register the selector '{0}' on the member '{1}.{2}' because Xamarin.iOS implicitly registers this selector. - - - - Invalid enum '{0}': enums with the [Native] attribute must have a underlying enum type of either 'long' or 'ulong'. - - The following are literal names and should not be translated: enum, [Native], long, ulong. -{0} - The full name of the C# enum. - - - - The Name parameter of the Registrar attribute on the class '{0}' ('{3}') contains an invalid character: '{1}' (0x{2}). - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found a generic protocol: '{0}'. Exporting generic protocols is not supported. - - - - Cannot register the extension method '{0}.{1}' because the type of the first parameter ('{2}') does not match the category type ('{3}'). - - - - Cannot register the type '{0}' because the category type '{1}' in its Category attribute does not inherit from NSObject. - - - - Cannot register the type '{0}' because the Type property in its Category attribute isn't set. - - - - Cannot register the type '{0}' as a category because it implements INativeObject or subclasses NSObject. - - - - Cannot register the type '{0}' as a category because it's generic. - - - - Cannot register the method '{0}.{1}' as a category method because it's generic. - - - - Cannot register two categories ('{0}' and '{1}') with the same native name ('{2}') - - - - Cannot register the category method '{0}.{1}' because at least one parameter is required for extension methods (and its type must match the category type '{2}'). - - - - Cannot register the constructor {0}.{1} in the category {0} because constructors in categories are not supported. - - - - Cannot register the method '{0}.{1}' as a category method because category methods must be static. - - - - Invalid character '{0}' (0x{1}) found in selector '{2}' for '{3}.{4}' - - - - The registrar found an unsupported structure '{0}': All fields in a structure must also be structures (field '{1}' with type '{2}' is not a structure). - - - - - The type '{0}' is not available in {3} {4} (it was introduced in {3} {5}){6} Please build with a newer {3} SDK (usually done by using the most recent version of Xcode). - - - - The type '{0}' (used as a base type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the base type. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a parameter in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as the property type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the property. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a return type in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - Internal error in the registrar ({0} ctor with {1} arguments). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (Unknown availability kind: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Cannot export the property '{0}' because its selector '{1}' is an Objective-C keyword. Please use a different name. - - - - The registrar couldn't find the type 'System.Void' in any of the referenced assemblies. - - - - Cannot register the method '{0}' because the signature contains a type ({1}) that isn't a reference type. - - - - Cannot register the method '{0}' because the signature contains a generic type ({1}) with a generic argument type that doesn't implement INativeObject ({2}). - - - - Cannot register the type '{0}' because its Objective-C name '{1}' is an Objective-C keyword. Please use a different name. - - - - Failed to generate a P/Invoke wrapper for {0}: {1} - - - - The registrar can't convert from '{0}' to '{1}' for the return value in the method {2}. - - - - The BindAs attribute on the return value of the method {0} is invalid: the BindAs type {1} is different from the return type {2}. - - - - The BindAs attribute on the parameter #{0} is invalid: the BindAs type {1} is different from the parameter type {2}. - - - - The BindAs attribute on the property {0}.{1} is invalid: the BindAs type {2} is different from the property type {1}. - - - - The registrar can't convert from '{0}' to '{1}' for the parameter '{2}' in the method {3}. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because {0} doesn't have a specific signature. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the delegate to block conversion type for the return value of the method {0}. - - - - The 'ProtocolType' parameter of the 'Adopts' attribute used in class '{0}' contains an invalid character. Value used: '{1}' Invalid Char: '{2}' - - - - The class '{0}' will not be registered because the WatchKit framework has been removed from the iOS SDK. - - - - The registrar found the abstract type '{0}' in the signature for '{1}'. Abstract types should not be used in the signature for a member exported to Objective-C. - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Missing '{0}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Could not find neither the '{0}' nor the '{1}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Failed to compile. Error code - {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Failed to compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The assembly '{0}' can't be AOT-compiled for 32-bit architectures because the native code is too big for the 32-bit ARM architecture. - - - - The compiler output is too long, it's been limited to 1000 lines. - - - - Native linking failed with error code 1. Check build log for details. - - - - Native linking failed. Please review the build log and the user flags provided to gcc: {0} - - - - Native linking failed. Please review the build log. - - - - Mono.framework MDK is missing. Please install the MDK for your Mono.framework version from https://www.mono-project.com/download/ - - - - Native linking warning: {0} - - - - Can't find {0}, likely because of a corrupted Xamarin.Mac installation. Please reinstall Xamarin.Mac. - - - - Native linking failed. Please review the build log. - - - - Invalid architecture '{0}'. The only valid architectures is x86_64. - - - - Native linking error: {0} - - - - Native linking failed, undefined symbol: {0}. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. - - - - Native linking failed, undefined Objective-C class: {0}. The symbol '{1}' could not be found in any of the libraries or frameworks linked with your application. - - - - Native linking failed, duplicate symbol: '{0}'. - - - - Duplicate symbol in: {0} (Location related to previous error) - - - - Native linking failed, undefined symbol: {0}. This symbol was referenced by the managed member {1}.{2}. Please verify that all the necessary frameworks have been referenced and native libraries linked. - - - - References to '{0}' might require additional -framework=XXX or -lXXX instructions to the native linker - - - - Native linking failed for '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Native linking failed because the linker command line was too long ({0} characters). - - - - Can't ignore the dynamic symbol {0} (--ignore-dynamic-symbol={0}) because it was not detected as a dynamic symbol. - - - - Not linking with WatchKit because it has been removed from iOS. - - - - Skipping framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - Linking against framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - The native linker failed to execute: {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Did not link with the framework '{0}', because the current {1} SDK does not contain support for this framework in the simulator. - This is a warning explaining why a native framework won't be referenced from the app when building for the simulator. The following are literal names and should not be translated: SDK - {0}: The name of the native framework - {1}: The current platform (will be either iOS, tvOS, watchOS or macOS). - - - - Missing 'strip' tool. Please install Xcode 'Command-Line Tools' component - - - - Missing 'dsymutil' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to generate the debug symbols (dSYM directory). Please review the build log. - - - - Failed to strip the final binary. Please review the build log. - - - - Missing 'lipo' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to create the a fat library. Please review the build log. - - - - Missing '{0}' tool. Please install Xcode 'Command-Line Tools' component - - - - Xcode license agreement may not have been accepted. Please launch Xcode. - - - - Failed to execute the tool '{0}', it failed with an error code '{1}'. Please check the build log for details. - - - - install_name_tool failed with an error code '{0}'. Check build log for details. - - - - lipo failed with an error code '{0}'. Check build log for details. - - - - pkg-config failed with an error code '{0}'. Check build log for details. - - - - Could not find {0}. Please install the Mono.framework from https://mono-project.com/Downloads - - - - Failed to execute pkg-config: '{0}'. Check build log for details. - - - - The tool xcrun failed to find result when looking for the tool '{0}' (the file '{1}' does not exist). Check build log for details. - - - - Internal consistency error. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new. - - - \ No newline at end of file diff --git a/tools/mtouch/TranslatedAssemblies/Errors.nl.resx b/tools/mtouch/TranslatedAssemblies/Errors.nl.resx deleted file mode 100644 index 689a08447c98..000000000000 --- a/tools/mtouch/TranslatedAssemblies/Errors.nl.resx +++ /dev/null @@ -1,1700 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - The error message for code {0} could not be found. Please report this missing message on GitHub at https://github.com/xamarin/xamarin-macios/issues/new - - This is the default message when an error code can not be found. - - - - Unexpected error - Please fill a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - '-devname' was provided without any device-specific action - - - - This version of Xamarin.Mac requires Mono {0} (the current Mono version is {1}). Please update the Mono.framework from http://mono-project.com/Downloads - - - - Could not parse the environment variable '{0}' - - - - Application name '{0}.exe' conflicts with an SDK or product assembly (.dll) name. - - - - New refcounting logic requires SGen to be enabled too. - - - - The output directory * does not exist. - - - - There is no devel platform at {0}, use --platform=PLAT to specify the SDK. - - - - The root assembly '{0}' does not exist - - - - You should provide one root assembly only, found {0} assemblies: '{1}' - - - - Error while loading assemblies: {0}. - - - - Could not parse the command line arguments: {0} - - - - {0} was built against a more recent runtime ({1}) than Xamarin.iOS supports. - - - - Incomplete data is provided to complete *. - - - - Profiling support requires sgen to be enabled too. - - - - The iOS {0} SDK does not support building applications targeting {1}. - - - - This is the nl MT0015 error message. - - - - The option '{0}' has been deprecated. - - - - You should provide a root assembly. - - - - Unknown command line argument: '{0}' - - - - Only one --[log|install|kill|launch]dev or --[launch|debug]sim option can be used. - - - - The valid options for '{0}' are '{1}'. - - - - 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). - - - - The options '--unsupported--enable-generics-in-registrar' and '--registrar' are not compatible. - - - - The root assembly {0} conflicts with another assembly ({1}). - - - - Application name '{0}.exe' conflicts with another user assembly. - - - - Could not find required file '{0}'. - - - - No SDK version was provided. Please add --sdk=X.Y to specify which {0} SDK should be used to build your application. - - - - Could not parse the command line argument '-{0}': {1} - - - - The options '\*' and '\*' are not compatible. - - - - 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 - - - - REPL (--enable-repl) is only supported in the simulator (--sim). - - - - The executable name ({0}) and the app name ({1}) are different, this may prevent crash logs from getting symbolicated properly. - - - - The command line arguments '--enable-background-fetch' and '--launch-for-background-fetch' require '--launchsim' too. - - - - The option '--debugtrack' is ignored unless '--debug' is also specified. - - - - A Xamarin.iOS project must reference either monotouch.dll or Xamarin.iOS.dll - - - - Cannot reference '{0}.dll' in a {1} project - it is implicitly referenced by '{2}'. - - - - Cannot launch a * simulator for a * app. Please enable the correct architecture(s) in your project's iOS Build options (Advanced page). - - - - 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). - - - - The old registrars (--registrar:oldstatic|olddynamic) are not supported when referencing Xamarin.iOS.dll. - - - - Applications targeting ARMv6 cannot reference Xamarin.iOS.dll. - - - - Could not find the assembly '\*', referenced by '\*'. - - - - Cannot reference '{0}' in a {1} app. - - - - No reference to either monotouch.dll or Xamarin.iOS.dll was found. A reference to monotouch.dll will be added. - - - - The Boehm garbage collector is not supported. The SGen garbage collector has been selected instead. - - - - --listsim is only supported with Xcode 6.0 or later. - - - - --extension is only supported when using the iOS 8.0 (or later) SDK. - - - - 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. - - - - {0}.framework is supported only if deployment target is 8.0 or later. {0} features might not work correctly. - - - - You cannot provide a root assembly if --no-root-assembly is passed, found {0} assemblies: '{1}' - - - - {3} {0} requires Xcode {4} or later. The current Xcode version (found in {2}) is {1}. - - - - An output directory (--output) is required if --no-root-assembly is passed. - - - - No command specified. - - - - Unable to canonicalize the path '{0}': {1} ({2}). - - - - The Xcode path '{0}' does not exist. - - - - Cannot find Xcode in the default location (/Applications/Xcode.app). Please install Xcode, or pass a custom path using --sdkroot <path>. - - - - Cannot determine the path to Xcode.app from the sdk root '{0}'. Please specify the full path to the Xcode.app bundle. - - - - The Xcode.app '{0}' is invalid (the file '{1}' does not exist). - - - - Could not find the currently selected Xcode on the system: {0} - - - - Could not find the currently selected Xcode on the system. 'xcode-select --print-path' returned '{0}', but that directory does not exist. - - - - No Xcode.app specified (using --sdkroot), using the system Xcode as reported by 'xcode-select --print-path': {0} - - - - No Xcode.app specified (using --sdkroot or 'xcode-select --print-path'), using the default Xcode instead: {0} - - - - Cannot find the executable in the extension * (no CFBundleExecutable entry in its Info.plist) - - - - Xamarin.iOS only supports embedded frameworks with Unified projects. - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 8.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 2.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Invalid build registrar assembly: * - - - - Invalid registrar: {0} - - - - Invalid value for target framework: {0}. - - - - Invalid target framework: {0}. Valid target frameworks are: {1}. - - - - Unknown platform: {0}. This usually indicates a bug in {1}; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Extensions are not supported for the platform '{0}'. - - - - {4} {0} does not support a deployment target of {1} for {3} (the minimum is {2}). Please select a newer deployment target in your project's Info.plist. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The minimum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - {4} {0} does not support a deployment target of {1} for {3} (the maximum is {2}). Please select an older deployment target in your project's Info.plist or upgrade to a newer version of {4}. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The maximum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - Invalid architecture '{0}' for {1} projects. Valid architectures are: {2} - - - - No architecture specified (using the --abi argument). An architecture is required for {0} projects. - - - - WatchOS projects must be extensions. - - - - Incremental builds are enabled with a deployment target < 8.0 (currently {0}). This is not supported (the resulting application will not launch on iOS 9), so the deployment target will be set to 8.0. - - - - The recommended Xcode version for {4} {0} is Xcode {3} or later. The current Xcode version (found in {2}) is {1}. - - - - No executable was copied into the app bundle. Please contact 'support@xamarin.com' - - - - Disabling the new refcount logic is deprecated. - - - - The command line argument --download-crash-report also requires --download-crash-report-to. - - - - REPL (--enable-repl) is only supported when linking is not used (--nolink). - - - - Asm-only bitcode is not supported on watchOS. Use either --bitcode:marker or --bitcode:full. - - - - Bitcode is not supported in the simulator. Do not pass --bitcode when building for the simulator. - - - - No reference to '{0}' was found. It will be added automatically. - - - - A target framework (--target-framework) must be specified. - - - - Incremental builds (--fastdev) is not supported with the Boehm GC. Incremental builds will be disabled. - - - - The GC must be in cooperative mode for watchOS apps. Please remove the --coop:false argument to mtouch. - - - - The option '{0}' cannot take the value '{1}' when cooperative mode is enabled for the GC. - - - - The target framework '{0}' is deprecated. Use '{1}' instead. - - - - - - Could not find 'mlaunch'. - - - - - Aot files could not be copied to the destination directory {0}: {1} - - - - Aot files could not be copied to the destination directory {0}: Could not start process. - - - - Aot files could not be copied to the destination directory {0} - - - - No reference to Xamarin.iOS.dll was found. - - - - machine.config file '{0}' can not be found. - - - - - Internal error: {0}. Please file an issue at https://github.com/xamarin/xamarin-macios/issues/new. - - - - Invalid assembly build target: '{0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly '{0}' is specified multiple times in --assembly-build-target arguments. - - - - The assemblies '{0}' and '{1}' have the same target name ('{2}'), but different targets ('{3}' and '{4}'). - - - - The static object '{0}' contains more than one assembly ('{1}'), but each static object must correspond with exactly one assembly. - - - - No assembly build target was specified for '{0}'. - - - - The assembly build target name '{0}' is invalid: the character '{1}' is not allowed. - - - - The assemblies '{0}' have different custom LLVM optimizations ('{1}'), which is not allowed when they are all compiled to a single binary. - - - - The assembly build target '{0}' did not match any assemblies. - - - - The assembly '{0}' was loaded from a different path than the provided path (provided path: {1}, actual path: {2}). - - - - 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. - - - - Bitcode has been enabled because this version of Xamarin.iOS does not support building watchOS projects using LLVM without enabling bitcode. - - - - Native code sharing has been disabled because {0} - - - - the container app's deployment target is earlier than iOS 8.0 (it's {0}). - - - - the container app includes I18N assemblies ({0}). - - - - the container app has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - Native code sharing has been disabled for the extension '{0}' because {1} - - - - the bitcode options differ between the container app ({0}) and the extension ({1}). - - - - the --assembly-build-target options are different between the container app ({0}) and the extension ({1}). - - - - the I18N assemblies are different between the container app ({0}) and the extension ({1}). - - - - the arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - the other arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - LLVM is not enabled or disabled in both the container app ({0}) and the extension ({1}). - - - - the managed linker settings are different between the container app ({0}) and the extension ({1}). - - - - the skipped assemblies for the managed linker are different between the container app ({0}) and the extension ({1}). - - - - the extension has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - the interpreter settings are different between the container app ({0}) and the extension ({1}). - - - - the interpreted assemblies are different between the container app ({0}) and the extension ({1}). - - - - the container app does not build for the ABI {0} (while the extension is building for this ABI). - - - - the container app is building for the ABI {0}, which is not compatible with the extension's ABI ({1}). - - - - the remove-dynamic-registrar optimization differ between the container app ({0}) and the extension ({1}). - - - - the container app is referencing the assembly '{0}' from '{1}', while the extension references a different version from '{2}'. - - - - Hybrid AOT compilation requires all assemblies to be AOT compiled - - - - It is recommended to reference dynamic symbols using code (--dynamic-symbol-mode=code) when bitcode is enabled. - - - - Invalid architecture: {0}. 32-bit architectures are not supported when deployment target is 11 or later. - - - - Can't launch a 32-bit app on a simulator that only supports 64-bit. - - - - The directory {0} containing the mono symbols could not be found. - - - - The executable assembly {0} does not reference {1}.dll. - - - - Could not set the current language to '{0}' (according to LANG={1}): {2} - - - - The --assembly-build-target command-line argument is ignored in the simulator. - - - - Incremental builds have been disabled because incremental builds are not supported in the simulator. - - - - 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. - - - - Could not touch the file '{0}': {1} - - - - Debugging symbol file for '{0}' does not match the assembly and is ignored. - - - - No root assemblies found. You should provide at least one root assembly. - - - - Product assembly '{0}' not found in assembly list: '{1}' - - - - Unknown optimization: '{0}'. Valid optimizations are: {1}. - - - - Found more than 1 assembly matching '{0}' choosing first:{1}{2} - - - - 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. - - - - Cannot find the assembly '{0}' referenced from '{1}'. - - - - Cannot find the assembly '{0}', referenced by a {2} attribute in '{1}'. - - - - File '{0}' is not a valid framework. - - - - The interpreter is not supported in the simulator. Switching to REPL which provide the same extra features on the simulator. - - - - Cannot find the assembly '{0}', passed as an argument to --interpreter. - - - - Projects using the Classic API are not supported anymore. Please migrate the project to the Unified API. - - - - Building 32-bit apps is not supported anymore. Please change the architecture in the project's Mac Build options to 'x86_64'. - - - - Please use device specific builds on WatchOS when building for Debug. - - - - ARM64_32 Debug mode requires --interpreter[=all], forcing it. - - - - Unable to parse the cflags '{0} from pkg-config: {1} - - - - Unable to parse the linker flags '{0}' from the LinkWith attribute for the library '{1}' in {2} : {3} - - - - Internal error: The interpreter is currently only available for 64 bits. - - - - Internal error: byref array is neither string, NSObject or INativeObject. - - - - Internal error: can't convert from '{0}' to '{1}' in {2}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the smart enum {0} doesn't seem to be a smart enum after all. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: unsupported tokentype ({0}) for {1}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the static registrar should not execute unless the linker also executed (or was disabled). A potential workaround is to pass '-f' as an additional {0} argument to force a full build. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: symbol without a name (type: {0}). Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: 'can't convert frameworks to frameworks: {0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly {0} was referenced by another assembly, but at the same time linked out by the linker. - - - - The linker output contains more than one assemblies named '{0}':\n\t{1} - - - - Not all assemblies for {0} have link tasks - - - - Link tasks for {0} aren't all the same - - - - The assembly '{0}' was resolved from the system's GAC: {1}. This could potentially be a problem in the future; to avoid such problems, please make sure to not use assemblies only available in the system's GAC. - - - - Unknown platform: {0}. This usually indicates a bug; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - Debugging symbol file for '{0}' is not valid and was ignored. - - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or use the dynamic registrar or set the managed linker behaviour to Link Platform or Link Framework SDKs Only in your project's Mac Build Options > Linker Behavior (to try to avoid the new APIs). - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or set the managed linker behaviour to Link Framework SDKs Only in your project's iOS Build Options > Linker Behavior (to try to avoid the new APIs). - - - Not linking with the framework {0} (used by the type {1}) because it's not available on the current platform ({2}). - - - Not linking with the framework {0} (referenced by a module reference in {1}) because it's not available on the current platform ({2}). - - - Could not map the iOS version {0} to a macOS version for Mac Catalyst - - - Could not map the macOS version {0} to a corresponding iOS version for Mac Catalyst - - - Could not copy the assembly '{0}' to '{1}': {2} - - - - Could not load the assembly '{0}': {1} - - - - Dependency tracking error: no files to compare. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Failed to re-use cached version of '{0}': {1}. - - - - Failed to create the executable '{0}': {1} - - - - Could not copy the directory '{0}' to '{1}': {2} - - - - Could not create symlink '{0}' -> '{1}': error {2} - - - - Cannot include different versions of the framework '{0}' - - - - Framework '{0}' included from: {1} (Related to previous error) - - - - Unsupported bitcode platform: {0}. - - - - Unsupported TvOS ABI: {0}. - - - - Could not extract the native library '{0}' from '{1}'. 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'). - - - - Invalid escape sequence when converting .s to .ll, \\ as the last characted in {0}:{1}. - - - - Invalid escape sequence when converting .s to .ll, bad octal escape in {0}:{1} due to {2}. - - - - Could not decompress the native framework '{0}' from '{1}'. Please review the build log for more information from the native 'unzip' command. - - - - The binding library '{0}' contains a user framework ({0}), but embedded user frameworks require iOS 8.0 (the deployment target is {1}). Please set the deployment target in the Info.plist file to at least 8.0. - - - - The required 'Xamarin.Mac.dll' assembly is missing from the references - - - - The assembly '{0}' is not compatible with this tool or profile - - - - {0} {1} could not be found. Target framework '{2}' is unusable to package the application. - - - - Target framework '{0}' is invalid. - - - - useFullXamMacFramework must always target framework .NET 4.5, not '{0}' which is invalid. - - - - Mismatch between Xamarin.Mac reference '{0}' and target framework selected '{1}'. - - - - Can not resolve reference: {0} - - - - One or more reference(s) to type '{0}' already exists inside '{1}' before linking - - - - One or more reference(s) to type '{0}' still exists inside '{1}' after linking - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Not a Mach-O static library (unknown header '{0}', expected '!<arch>'). - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Unknown format for fat entry at position {0} in {1}. - - - - File of type {0} is not a MachO file ({1}). - - - - Invalid entry '{0}' in the static library '{1}', entry header doesn't end with 0x60 0x0A (found '0x{2} 0x{3}') - - - - Could not link assemblies. {0} - - - - Can not resolve reference: {0} - - - - Option '--optimize={0}{1}' will be ignored since the static registrar is not enabled - - - - - Option '--optimize={0}{1}' will be ignored since linking is disabled - - - - Option '--optimize={0}' will be ignored since it's only applicable to {1}. - This is a warning that is shown when the command-line option --optimize=... is not valid for a particular platform -{0} - The optimization option that is not valid for the current platform -{1} - The platforms in question, such as 'iOS'. - - - - Extra linker definitions file '{0}' could not be located. - - - - Definitions from '{0}' could not be parsed. - - - - Can not load mscorlib.dll from: '{0}'. Please reinstall Xamarin.iOS. - - - - Native library '{0}' was referenced but could not be found. - - - - Failed to resolve "{0}" reference from "{1}" - - - - Xamarin.Mac Unified API against a full .NET framework does not support linking SDK or All assemblies. Pass either the `-nolink` or `-linkplatform` flag. - - Using the linker is not supported in certain situations in Xamarin.Mac, see: https://docs.microsoft.com/xamarin/mac/deploy-test/linker. The following are literal names and should not be translated: Xamarin.Mac Unified API, .NET, SDK, All, `-nolink`, and `-linkplatform`. - - - - Referenced by {0}.{1} - - - - Unknown HttpMessageHandler `{0}`. Valid values are HttpClientHandler (default), CFNetworkHandler or NSUrlSessionHandler - - - - Only first {0} of {1} \"Referenced by\" warnings shown. - - - - Failed to resolve the reference to \"{0}\", referenced in \"{1}\". The app will not include the referenced assembly, and may fail at runtime. - - - - Unable to link assembly '{0}' as it is mixed-mode. - - - - Invalid HttpMessageHandler `{0}` for watchOS. The only valid value is NSUrlSessionHandler. - - - - Could not process XML description: {0} - - - - The assembly '{0}' is referenced from two different locations: '{1}' and '{2}'. - - - - Can not load the root assembly '{0}'. - - - - - The linker step '{0}' failed processing `{1}`. - This is a message when processing an assembly/type/field/method/property/event fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly/type/field/method/property/event that failed processing. - - - - - - - - - - - - Can't resolve the reference '{0}', referenced from the method '{1}' in '{2}'. - - - - Error processing the method '{0}' in the assembly '{1}': {2} - - - - Error processing the method '{0}' in the assembly '{1}' - - - - Error processing assembly '{0}': {1} - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect fields. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect properties. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a '{1}' parameter type (expected 'ObjCRuntime.BindingImplOptions). - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a {1} parameters (expected 1 parameters). - - - - The property {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This property will throw an exception if called. - - - - The method {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This method will throw an exception if called. - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because the previous instruction was unexpected ({3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because could not determine the type of the delegate type of the first argument (instruction: {3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} because the type of the value passed as the first argument (the trampoline) is {1}, which makes it impossible to compute the block signature. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1} because no [UserDelegateType] attribute could be found on {2}. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1}: {2}. - - - - It's not safe to remove the dynamic registrar, because {0} references '{1}.{2} ({3})'. - - - - {0} was stripped of architectures except {1} to comply with App Store restrictions. This could break existing codesigning signatures. Consider stripping the library with lipo or disabling with --optimize=-trim-architectures - - - - Xamarin.Mac 'Partial Static' registrar does not support linking. Disable linking or use another registrar mode. - - - - Can not find the corlib assembly '{0}' in the list of loaded assemblies. - - - - - - - - - - - The linker step '{0}' failed during processing: {1} - This is a message when processing fails in the linker. - {0} - The name of the step that fails. - {1} - A string describing what failed. - - - - The linker step '{0}' failed while processing {1}: {2} - This is a message when processing an assembly fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly that failed processing. - {1} - A string describing what failed - - - - - - - - - - - Could not {0} the assembly '{1}' - - - - Debugging is not supported when building with LLVM. Debugging has been disabled. - - - - Could not AOT the assembly '{0}' because it doesn't exist. - - - - The dependency '{0}' of the assembly '{1}' was not found. Please review the project's references. - - - - 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. - - - - Debug info files (*.mdb / *.pdb) will not be loaded when llvm is enabled. - - - - Bitcode support requires the use of LLVM (--abi=arm64+llvm etc.) - - - - AOT of '{0}' was requested but was not found - - - - Exclusion of AOT of '{0}' was requested but was not found - - - - The main template could not be expanded to `{0}`. - - - - Failed to compile the generated code for P/Invoke methods. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot build a signature for type `{0}`. - - - - The registrar found an invalid type `{0}` in signature for method `{2}`. Use `{1}` instead. - - - - The registrar found an invalid type `{0}` in signature for method `{1}`: The type implements INativeObject, but does not have a constructor that takes two (IntPtr, bool) arguments. - - - - The registrar cannot marshal the return value for type `{0}` in signature for method `{1}`. - - - - The registrar cannot marshal the return value of type `{0}` in the method `{1}.{2}`. - - - - The registrar cannot marshal the parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot get the ObjectiveC type for managed type `{0}`. - - - - Failed to compile the generated registrar code. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot marshal the out parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot build a signature for type `{0}' in method `{1}`. - - - - The registrar found a generic method: '{0}'. Exporting generic methods is not supported, and will lead to random behavior and/or crashes - - - - Unexpected error in the registrar for the method '{0}.{1}' - Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not register the assembly '{0}': {1} - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register two managed types ('{0}' and '{1}') with the same native name ('{2}'). - - - - Could not register the selector '{0}' of the member '{1}.{2}' because the selector is already registered on the member '{3}'. - - - - The registrar found an unknown field type '{0}' in field '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - 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). - - - - The type of the variadic parameter in the variadic function '{0}' must be System.IntPtr. - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid RegisterAttribute property {1} found on '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid AdoptsAttribute found on '{0}': expected 1 constructor arguments, got {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}.{1}': unknown field {2}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid {0} found on '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': should have 1 constructor arguments, found {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': could not find the underlying enum type of {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found an invalid type '{0}' in signature for method '{1}': The interface must have a Protocol attribute specifying its wrapper type. - - - - Cannot register two managed protocols ('{0}' and '{1}') with the same native name ('{2}'). - - - - Cannot register more than one interface method for the method '{0}.{1}'. - - - - The registrar found an invalid generic parameter type '{0}' in the parameter {2} of the method '{1}'. The generic parameter must have an 'NSObject' constraint. - - - - The registrar found an invalid generic return type '{0}' in the method '{1}'. The generic return type must have an 'NSObject' constraint. - - - - The registrar cannot export static methods in generic classes ('{0}'). - - - - The registrar cannot export static properties in generic classes ('{0}.{1}'). - - - - The registrar found an invalid generic return type '{0}' in the property '{1}.{2}'. The return type must have an 'NSObject' constraint. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) Please select a newer SDK in your app's {3} Build options. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) This configuration is not supported with the static registrar (pass --registrar:dynamic as an additional mmp argument in your project's Mac Build option to select). Alternatively select a newer SDK in your app's Mac Build options. - - - - The member '{0}' has an Export attribute without a selector. A selector is required. - - - - The registrar cannot marshal the parameter type '{0}' of the parameter '{1}' in the method '{2}.{3}' - - - - The method '{0}.{1}' is implementing '{2}.{3}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. Properties with the [Connect] attribute must have a property type of NSObject (or a subclass of NSObject). - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the variadic method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register the selector '{0}' on the member '{1}.{2}' because Xamarin.iOS implicitly registers this selector. - - - - Invalid enum '{0}': enums with the [Native] attribute must have a underlying enum type of either 'long' or 'ulong'. - - The following are literal names and should not be translated: enum, [Native], long, ulong. -{0} - The full name of the C# enum. - - - - The Name parameter of the Registrar attribute on the class '{0}' ('{3}') contains an invalid character: '{1}' (0x{2}). - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found a generic protocol: '{0}'. Exporting generic protocols is not supported. - - - - Cannot register the extension method '{0}.{1}' because the type of the first parameter ('{2}') does not match the category type ('{3}'). - - - - Cannot register the type '{0}' because the category type '{1}' in its Category attribute does not inherit from NSObject. - - - - Cannot register the type '{0}' because the Type property in its Category attribute isn't set. - - - - Cannot register the type '{0}' as a category because it implements INativeObject or subclasses NSObject. - - - - Cannot register the type '{0}' as a category because it's generic. - - - - Cannot register the method '{0}.{1}' as a category method because it's generic. - - - - Cannot register two categories ('{0}' and '{1}') with the same native name ('{2}') - - - - Cannot register the category method '{0}.{1}' because at least one parameter is required for extension methods (and its type must match the category type '{2}'). - - - - Cannot register the constructor {0}.{1} in the category {0} because constructors in categories are not supported. - - - - Cannot register the method '{0}.{1}' as a category method because category methods must be static. - - - - Invalid character '{0}' (0x{1}) found in selector '{2}' for '{3}.{4}' - - - - The registrar found an unsupported structure '{0}': All fields in a structure must also be structures (field '{1}' with type '{2}' is not a structure). - - - - - The type '{0}' is not available in {3} {4} (it was introduced in {3} {5}){6} Please build with a newer {3} SDK (usually done by using the most recent version of Xcode). - - - - The type '{0}' (used as a base type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the base type. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a parameter in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as the property type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the property. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a return type in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - Internal error in the registrar ({0} ctor with {1} arguments). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (Unknown availability kind: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Cannot export the property '{0}' because its selector '{1}' is an Objective-C keyword. Please use a different name. - - - - The registrar couldn't find the type 'System.Void' in any of the referenced assemblies. - - - - Cannot register the method '{0}' because the signature contains a type ({1}) that isn't a reference type. - - - - Cannot register the method '{0}' because the signature contains a generic type ({1}) with a generic argument type that doesn't implement INativeObject ({2}). - - - - Cannot register the type '{0}' because its Objective-C name '{1}' is an Objective-C keyword. Please use a different name. - - - - Failed to generate a P/Invoke wrapper for {0}: {1} - - - - The registrar can't convert from '{0}' to '{1}' for the return value in the method {2}. - - - - The BindAs attribute on the return value of the method {0} is invalid: the BindAs type {1} is different from the return type {2}. - - - - The BindAs attribute on the parameter #{0} is invalid: the BindAs type {1} is different from the parameter type {2}. - - - - The BindAs attribute on the property {0}.{1} is invalid: the BindAs type {2} is different from the property type {1}. - - - - The registrar can't convert from '{0}' to '{1}' for the parameter '{2}' in the method {3}. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because {0} doesn't have a specific signature. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the delegate to block conversion type for the return value of the method {0}. - - - - The 'ProtocolType' parameter of the 'Adopts' attribute used in class '{0}' contains an invalid character. Value used: '{1}' Invalid Char: '{2}' - - - - The class '{0}' will not be registered because the WatchKit framework has been removed from the iOS SDK. - - - - The registrar found the abstract type '{0}' in the signature for '{1}'. Abstract types should not be used in the signature for a member exported to Objective-C. - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Missing '{0}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Could not find neither the '{0}' nor the '{1}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Failed to compile. Error code - {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Failed to compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The assembly '{0}' can't be AOT-compiled for 32-bit architectures because the native code is too big for the 32-bit ARM architecture. - - - - The compiler output is too long, it's been limited to 1000 lines. - - - - Native linking failed with error code 1. Check build log for details. - - - - Native linking failed. Please review the build log and the user flags provided to gcc: {0} - - - - Native linking failed. Please review the build log. - - - - Mono.framework MDK is missing. Please install the MDK for your Mono.framework version from https://www.mono-project.com/download/ - - - - Native linking warning: {0} - - - - Can't find {0}, likely because of a corrupted Xamarin.Mac installation. Please reinstall Xamarin.Mac. - - - - Native linking failed. Please review the build log. - - - - Invalid architecture '{0}'. The only valid architectures is x86_64. - - - - Native linking error: {0} - - - - Native linking failed, undefined symbol: {0}. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. - - - - Native linking failed, undefined Objective-C class: {0}. The symbol '{1}' could not be found in any of the libraries or frameworks linked with your application. - - - - Native linking failed, duplicate symbol: '{0}'. - - - - Duplicate symbol in: {0} (Location related to previous error) - - - - Native linking failed, undefined symbol: {0}. This symbol was referenced by the managed member {1}.{2}. Please verify that all the necessary frameworks have been referenced and native libraries linked. - - - - References to '{0}' might require additional -framework=XXX or -lXXX instructions to the native linker - - - - Native linking failed for '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Native linking failed because the linker command line was too long ({0} characters). - - - - Can't ignore the dynamic symbol {0} (--ignore-dynamic-symbol={0}) because it was not detected as a dynamic symbol. - - - - Not linking with WatchKit because it has been removed from iOS. - - - - Skipping framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - Linking against framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - The native linker failed to execute: {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Did not link with the framework '{0}', because the current {1} SDK does not contain support for this framework in the simulator. - This is a warning explaining why a native framework won't be referenced from the app when building for the simulator. The following are literal names and should not be translated: SDK - {0}: The name of the native framework - {1}: The current platform (will be either iOS, tvOS, watchOS or macOS). - - - - Missing 'strip' tool. Please install Xcode 'Command-Line Tools' component - - - - Missing 'dsymutil' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to generate the debug symbols (dSYM directory). Please review the build log. - - - - Failed to strip the final binary. Please review the build log. - - - - Missing 'lipo' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to create the a fat library. Please review the build log. - - - - Missing '{0}' tool. Please install Xcode 'Command-Line Tools' component - - - - Xcode license agreement may not have been accepted. Please launch Xcode. - - - - Failed to execute the tool '{0}', it failed with an error code '{1}'. Please check the build log for details. - - - - install_name_tool failed with an error code '{0}'. Check build log for details. - - - - lipo failed with an error code '{0}'. Check build log for details. - - - - pkg-config failed with an error code '{0}'. Check build log for details. - - - - Could not find {0}. Please install the Mono.framework from https://mono-project.com/Downloads - - - - Failed to execute pkg-config: '{0}'. Check build log for details. - - - - The tool xcrun failed to find result when looking for the tool '{0}' (the file '{1}' does not exist). Check build log for details. - - - - Internal consistency error. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new. - - - \ No newline at end of file diff --git a/tools/mtouch/TranslatedAssemblies/Errors.pt-PT.resx b/tools/mtouch/TranslatedAssemblies/Errors.pt-PT.resx deleted file mode 100644 index 1b8446a9d235..000000000000 --- a/tools/mtouch/TranslatedAssemblies/Errors.pt-PT.resx +++ /dev/null @@ -1,1700 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - The error message for code {0} could not be found. Please report this missing message on GitHub at https://github.com/xamarin/xamarin-macios/issues/new - - This is the default message when an error code can not be found. - - - - Unexpected error - Please fill a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - '-devname' was provided without any device-specific action - - - - This version of Xamarin.Mac requires Mono {0} (the current Mono version is {1}). Please update the Mono.framework from http://mono-project.com/Downloads - - - - Could not parse the environment variable '{0}' - - - - Application name '{0}.exe' conflicts with an SDK or product assembly (.dll) name. - - - - New refcounting logic requires SGen to be enabled too. - - - - The output directory * does not exist. - - - - There is no devel platform at {0}, use --platform=PLAT to specify the SDK. - - - - The root assembly '{0}' does not exist - - - - You should provide one root assembly only, found {0} assemblies: '{1}' - - - - Error while loading assemblies: {0}. - - - - Could not parse the command line arguments: {0} - - - - {0} was built against a more recent runtime ({1}) than Xamarin.iOS supports. - - - - Incomplete data is provided to complete *. - - - - Profiling support requires sgen to be enabled too. - - - - The iOS {0} SDK does not support building applications targeting {1}. - - - - This is the pt MT0015 error message. - - - - The option '{0}' has been deprecated. - - - - You should provide a root assembly. - - - - Unknown command line argument: '{0}' - - - - Only one --[log|install|kill|launch]dev or --[launch|debug]sim option can be used. - - - - The valid options for '{0}' are '{1}'. - - - - 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). - - - - The options '--unsupported--enable-generics-in-registrar' and '--registrar' are not compatible. - - - - The root assembly {0} conflicts with another assembly ({1}). - - - - Application name '{0}.exe' conflicts with another user assembly. - - - - Could not find required file '{0}'. - - - - No SDK version was provided. Please add --sdk=X.Y to specify which {0} SDK should be used to build your application. - - - - Could not parse the command line argument '-{0}': {1} - - - - The options '\*' and '\*' are not compatible. - - - - 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 - - - - REPL (--enable-repl) is only supported in the simulator (--sim). - - - - The executable name ({0}) and the app name ({1}) are different, this may prevent crash logs from getting symbolicated properly. - - - - The command line arguments '--enable-background-fetch' and '--launch-for-background-fetch' require '--launchsim' too. - - - - The option '--debugtrack' is ignored unless '--debug' is also specified. - - - - A Xamarin.iOS project must reference either monotouch.dll or Xamarin.iOS.dll - - - - Cannot reference '{0}.dll' in a {1} project - it is implicitly referenced by '{2}'. - - - - Cannot launch a * simulator for a * app. Please enable the correct architecture(s) in your project's iOS Build options (Advanced page). - - - - 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). - - - - The old registrars (--registrar:oldstatic|olddynamic) are not supported when referencing Xamarin.iOS.dll. - - - - Applications targeting ARMv6 cannot reference Xamarin.iOS.dll. - - - - Could not find the assembly '\*', referenced by '\*'. - - - - Cannot reference '{0}' in a {1} app. - - - - No reference to either monotouch.dll or Xamarin.iOS.dll was found. A reference to monotouch.dll will be added. - - - - The Boehm garbage collector is not supported. The SGen garbage collector has been selected instead. - - - - --listsim is only supported with Xcode 6.0 or later. - - - - --extension is only supported when using the iOS 8.0 (or later) SDK. - - - - 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. - - - - {0}.framework is supported only if deployment target is 8.0 or later. {0} features might not work correctly. - - - - You cannot provide a root assembly if --no-root-assembly is passed, found {0} assemblies: '{1}' - - - - {3} {0} requires Xcode {4} or later. The current Xcode version (found in {2}) is {1}. - - - - An output directory (--output) is required if --no-root-assembly is passed. - - - - No command specified. - - - - Unable to canonicalize the path '{0}': {1} ({2}). - - - - The Xcode path '{0}' does not exist. - - - - Cannot find Xcode in the default location (/Applications/Xcode.app). Please install Xcode, or pass a custom path using --sdkroot <path>. - - - - Cannot determine the path to Xcode.app from the sdk root '{0}'. Please specify the full path to the Xcode.app bundle. - - - - The Xcode.app '{0}' is invalid (the file '{1}' does not exist). - - - - Could not find the currently selected Xcode on the system: {0} - - - - Could not find the currently selected Xcode on the system. 'xcode-select --print-path' returned '{0}', but that directory does not exist. - - - - No Xcode.app specified (using --sdkroot), using the system Xcode as reported by 'xcode-select --print-path': {0} - - - - No Xcode.app specified (using --sdkroot or 'xcode-select --print-path'), using the default Xcode instead: {0} - - - - Cannot find the executable in the extension * (no CFBundleExecutable entry in its Info.plist) - - - - Xamarin.iOS only supports embedded frameworks with Unified projects. - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 8.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 2.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Invalid build registrar assembly: * - - - - Invalid registrar: {0} - - - - Invalid value for target framework: {0}. - - - - Invalid target framework: {0}. Valid target frameworks are: {1}. - - - - Unknown platform: {0}. This usually indicates a bug in {1}; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Extensions are not supported for the platform '{0}'. - - - - {4} {0} does not support a deployment target of {1} for {3} (the minimum is {2}). Please select a newer deployment target in your project's Info.plist. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The minimum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - {4} {0} does not support a deployment target of {1} for {3} (the maximum is {2}). Please select an older deployment target in your project's Info.plist or upgrade to a newer version of {4}. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The maximum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - Invalid architecture '{0}' for {1} projects. Valid architectures are: {2} - - - - No architecture specified (using the --abi argument). An architecture is required for {0} projects. - - - - WatchOS projects must be extensions. - - - - Incremental builds are enabled with a deployment target < 8.0 (currently {0}). This is not supported (the resulting application will not launch on iOS 9), so the deployment target will be set to 8.0. - - - - The recommended Xcode version for {4} {0} is Xcode {3} or later. The current Xcode version (found in {2}) is {1}. - - - - No executable was copied into the app bundle. Please contact 'support@xamarin.com' - - - - Disabling the new refcount logic is deprecated. - - - - The command line argument --download-crash-report also requires --download-crash-report-to. - - - - REPL (--enable-repl) is only supported when linking is not used (--nolink). - - - - Asm-only bitcode is not supported on watchOS. Use either --bitcode:marker or --bitcode:full. - - - - Bitcode is not supported in the simulator. Do not pass --bitcode when building for the simulator. - - - - No reference to '{0}' was found. It will be added automatically. - - - - A target framework (--target-framework) must be specified. - - - - Incremental builds (--fastdev) is not supported with the Boehm GC. Incremental builds will be disabled. - - - - The GC must be in cooperative mode for watchOS apps. Please remove the --coop:false argument to mtouch. - - - - The option '{0}' cannot take the value '{1}' when cooperative mode is enabled for the GC. - - - - The target framework '{0}' is deprecated. Use '{1}' instead. - - - - - - Could not find 'mlaunch'. - - - - - Aot files could not be copied to the destination directory {0}: {1} - - - - Aot files could not be copied to the destination directory {0}: Could not start process. - - - - Aot files could not be copied to the destination directory {0} - - - - No reference to Xamarin.iOS.dll was found. - - - - machine.config file '{0}' can not be found. - - - - - Internal error: {0}. Please file an issue at https://github.com/xamarin/xamarin-macios/issues/new. - - - - Invalid assembly build target: '{0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly '{0}' is specified multiple times in --assembly-build-target arguments. - - - - The assemblies '{0}' and '{1}' have the same target name ('{2}'), but different targets ('{3}' and '{4}'). - - - - The static object '{0}' contains more than one assembly ('{1}'), but each static object must correspond with exactly one assembly. - - - - No assembly build target was specified for '{0}'. - - - - The assembly build target name '{0}' is invalid: the character '{1}' is not allowed. - - - - The assemblies '{0}' have different custom LLVM optimizations ('{1}'), which is not allowed when they are all compiled to a single binary. - - - - The assembly build target '{0}' did not match any assemblies. - - - - The assembly '{0}' was loaded from a different path than the provided path (provided path: {1}, actual path: {2}). - - - - 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. - - - - Bitcode has been enabled because this version of Xamarin.iOS does not support building watchOS projects using LLVM without enabling bitcode. - - - - Native code sharing has been disabled because {0} - - - - the container app's deployment target is earlier than iOS 8.0 (it's {0}). - - - - the container app includes I18N assemblies ({0}). - - - - the container app has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - Native code sharing has been disabled for the extension '{0}' because {1} - - - - the bitcode options differ between the container app ({0}) and the extension ({1}). - - - - the --assembly-build-target options are different between the container app ({0}) and the extension ({1}). - - - - the I18N assemblies are different between the container app ({0}) and the extension ({1}). - - - - the arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - the other arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - LLVM is not enabled or disabled in both the container app ({0}) and the extension ({1}). - - - - the managed linker settings are different between the container app ({0}) and the extension ({1}). - - - - the skipped assemblies for the managed linker are different between the container app ({0}) and the extension ({1}). - - - - the extension has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - the interpreter settings are different between the container app ({0}) and the extension ({1}). - - - - the interpreted assemblies are different between the container app ({0}) and the extension ({1}). - - - - the container app does not build for the ABI {0} (while the extension is building for this ABI). - - - - the container app is building for the ABI {0}, which is not compatible with the extension's ABI ({1}). - - - - the remove-dynamic-registrar optimization differ between the container app ({0}) and the extension ({1}). - - - - the container app is referencing the assembly '{0}' from '{1}', while the extension references a different version from '{2}'. - - - - Hybrid AOT compilation requires all assemblies to be AOT compiled - - - - It is recommended to reference dynamic symbols using code (--dynamic-symbol-mode=code) when bitcode is enabled. - - - - Invalid architecture: {0}. 32-bit architectures are not supported when deployment target is 11 or later. - - - - Can't launch a 32-bit app on a simulator that only supports 64-bit. - - - - The directory {0} containing the mono symbols could not be found. - - - - The executable assembly {0} does not reference {1}.dll. - - - - Could not set the current language to '{0}' (according to LANG={1}): {2} - - - - The --assembly-build-target command-line argument is ignored in the simulator. - - - - Incremental builds have been disabled because incremental builds are not supported in the simulator. - - - - 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. - - - - Could not touch the file '{0}': {1} - - - - Debugging symbol file for '{0}' does not match the assembly and is ignored. - - - - No root assemblies found. You should provide at least one root assembly. - - - - Product assembly '{0}' not found in assembly list: '{1}' - - - - Unknown optimization: '{0}'. Valid optimizations are: {1}. - - - - Found more than 1 assembly matching '{0}' choosing first:{1}{2} - - - - 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. - - - - Cannot find the assembly '{0}' referenced from '{1}'. - - - - Cannot find the assembly '{0}', referenced by a {2} attribute in '{1}'. - - - - File '{0}' is not a valid framework. - - - - The interpreter is not supported in the simulator. Switching to REPL which provide the same extra features on the simulator. - - - - Cannot find the assembly '{0}', passed as an argument to --interpreter. - - - - Projects using the Classic API are not supported anymore. Please migrate the project to the Unified API. - - - - Building 32-bit apps is not supported anymore. Please change the architecture in the project's Mac Build options to 'x86_64'. - - - - Please use device specific builds on WatchOS when building for Debug. - - - - ARM64_32 Debug mode requires --interpreter[=all], forcing it. - - - - Unable to parse the cflags '{0} from pkg-config: {1} - - - - Unable to parse the linker flags '{0}' from the LinkWith attribute for the library '{1}' in {2} : {3} - - - - Internal error: The interpreter is currently only available for 64 bits. - - - - Internal error: byref array is neither string, NSObject or INativeObject. - - - - Internal error: can't convert from '{0}' to '{1}' in {2}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the smart enum {0} doesn't seem to be a smart enum after all. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: unsupported tokentype ({0}) for {1}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the static registrar should not execute unless the linker also executed (or was disabled). A potential workaround is to pass '-f' as an additional {0} argument to force a full build. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: symbol without a name (type: {0}). Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: 'can't convert frameworks to frameworks: {0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly {0} was referenced by another assembly, but at the same time linked out by the linker. - - - - The linker output contains more than one assemblies named '{0}':\n\t{1} - - - - Not all assemblies for {0} have link tasks - - - - Link tasks for {0} aren't all the same - - - - The assembly '{0}' was resolved from the system's GAC: {1}. This could potentially be a problem in the future; to avoid such problems, please make sure to not use assemblies only available in the system's GAC. - - - - Unknown platform: {0}. This usually indicates a bug; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - Debugging symbol file for '{0}' is not valid and was ignored. - - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or use the dynamic registrar or set the managed linker behaviour to Link Platform or Link Framework SDKs Only in your project's Mac Build Options > Linker Behavior (to try to avoid the new APIs). - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or set the managed linker behaviour to Link Framework SDKs Only in your project's iOS Build Options > Linker Behavior (to try to avoid the new APIs). - - - Not linking with the framework {0} (used by the type {1}) because it's not available on the current platform ({2}). - - - Not linking with the framework {0} (referenced by a module reference in {1}) because it's not available on the current platform ({2}). - - - Could not map the iOS version {0} to a macOS version for Mac Catalyst - - - Could not map the macOS version {0} to a corresponding iOS version for Mac Catalyst - - - Could not copy the assembly '{0}' to '{1}': {2} - - - - Could not load the assembly '{0}': {1} - - - - Dependency tracking error: no files to compare. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Failed to re-use cached version of '{0}': {1}. - - - - Failed to create the executable '{0}': {1} - - - - Could not copy the directory '{0}' to '{1}': {2} - - - - Could not create symlink '{0}' -> '{1}': error {2} - - - - Cannot include different versions of the framework '{0}' - - - - Framework '{0}' included from: {1} (Related to previous error) - - - - Unsupported bitcode platform: {0}. - - - - Unsupported TvOS ABI: {0}. - - - - Could not extract the native library '{0}' from '{1}'. 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'). - - - - Invalid escape sequence when converting .s to .ll, \\ as the last characted in {0}:{1}. - - - - Invalid escape sequence when converting .s to .ll, bad octal escape in {0}:{1} due to {2}. - - - - Could not decompress the native framework '{0}' from '{1}'. Please review the build log for more information from the native 'unzip' command. - - - - The binding library '{0}' contains a user framework ({0}), but embedded user frameworks require iOS 8.0 (the deployment target is {1}). Please set the deployment target in the Info.plist file to at least 8.0. - - - - The required 'Xamarin.Mac.dll' assembly is missing from the references - - - - The assembly '{0}' is not compatible with this tool or profile - - - - {0} {1} could not be found. Target framework '{2}' is unusable to package the application. - - - - Target framework '{0}' is invalid. - - - - useFullXamMacFramework must always target framework .NET 4.5, not '{0}' which is invalid. - - - - Mismatch between Xamarin.Mac reference '{0}' and target framework selected '{1}'. - - - - Can not resolve reference: {0} - - - - One or more reference(s) to type '{0}' already exists inside '{1}' before linking - - - - One or more reference(s) to type '{0}' still exists inside '{1}' after linking - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Not a Mach-O static library (unknown header '{0}', expected '!<arch>'). - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Unknown format for fat entry at position {0} in {1}. - - - - File of type {0} is not a MachO file ({1}). - - - - Invalid entry '{0}' in the static library '{1}', entry header doesn't end with 0x60 0x0A (found '0x{2} 0x{3}') - - - - Could not link assemblies. {0} - - - - Can not resolve reference: {0} - - - - Option '--optimize={0}{1}' will be ignored since the static registrar is not enabled - - - - - Option '--optimize={0}{1}' will be ignored since linking is disabled - - - - Option '--optimize={0}' will be ignored since it's only applicable to {1}. - This is a warning that is shown when the command-line option --optimize=... is not valid for a particular platform -{0} - The optimization option that is not valid for the current platform -{1} - The platforms in question, such as 'iOS'. - - - - Extra linker definitions file '{0}' could not be located. - - - - Definitions from '{0}' could not be parsed. - - - - Can not load mscorlib.dll from: '{0}'. Please reinstall Xamarin.iOS. - - - - Native library '{0}' was referenced but could not be found. - - - - Failed to resolve "{0}" reference from "{1}" - - - - Xamarin.Mac Unified API against a full .NET framework does not support linking SDK or All assemblies. Pass either the `-nolink` or `-linkplatform` flag. - - Using the linker is not supported in certain situations in Xamarin.Mac, see: https://docs.microsoft.com/xamarin/mac/deploy-test/linker. The following are literal names and should not be translated: Xamarin.Mac Unified API, .NET, SDK, All, `-nolink`, and `-linkplatform`. - - - - Referenced by {0}.{1} - - - - Unknown HttpMessageHandler `{0}`. Valid values are HttpClientHandler (default), CFNetworkHandler or NSUrlSessionHandler - - - - Only first {0} of {1} \"Referenced by\" warnings shown. - - - - Failed to resolve the reference to \"{0}\", referenced in \"{1}\". The app will not include the referenced assembly, and may fail at runtime. - - - - Unable to link assembly '{0}' as it is mixed-mode. - - - - Invalid HttpMessageHandler `{0}` for watchOS. The only valid value is NSUrlSessionHandler. - - - - Could not process XML description: {0} - - - - The assembly '{0}' is referenced from two different locations: '{1}' and '{2}'. - - - - Can not load the root assembly '{0}'. - - - - - The linker step '{0}' failed processing `{1}`. - This is a message when processing an assembly/type/field/method/property/event fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly/type/field/method/property/event that failed processing. - - - - - - - - - - - - Can't resolve the reference '{0}', referenced from the method '{1}' in '{2}'. - - - - Error processing the method '{0}' in the assembly '{1}': {2} - - - - Error processing the method '{0}' in the assembly '{1}' - - - - Error processing assembly '{0}': {1} - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect fields. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect properties. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a '{1}' parameter type (expected 'ObjCRuntime.BindingImplOptions). - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a {1} parameters (expected 1 parameters). - - - - The property {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This property will throw an exception if called. - - - - The method {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This method will throw an exception if called. - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because the previous instruction was unexpected ({3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because could not determine the type of the delegate type of the first argument (instruction: {3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} because the type of the value passed as the first argument (the trampoline) is {1}, which makes it impossible to compute the block signature. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1} because no [UserDelegateType] attribute could be found on {2}. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1}: {2}. - - - - It's not safe to remove the dynamic registrar, because {0} references '{1}.{2} ({3})'. - - - - {0} was stripped of architectures except {1} to comply with App Store restrictions. This could break existing codesigning signatures. Consider stripping the library with lipo or disabling with --optimize=-trim-architectures - - - - Xamarin.Mac 'Partial Static' registrar does not support linking. Disable linking or use another registrar mode. - - - - Can not find the corlib assembly '{0}' in the list of loaded assemblies. - - - - - - - - - - - The linker step '{0}' failed during processing: {1} - This is a message when processing fails in the linker. - {0} - The name of the step that fails. - {1} - A string describing what failed. - - - - The linker step '{0}' failed while processing {1}: {2} - This is a message when processing an assembly fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly that failed processing. - {1} - A string describing what failed - - - - - - - - - - - Could not {0} the assembly '{1}' - - - - Debugging is not supported when building with LLVM. Debugging has been disabled. - - - - Could not AOT the assembly '{0}' because it doesn't exist. - - - - The dependency '{0}' of the assembly '{1}' was not found. Please review the project's references. - - - - 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. - - - - Debug info files (*.mdb / *.pdb) will not be loaded when llvm is enabled. - - - - Bitcode support requires the use of LLVM (--abi=arm64+llvm etc.) - - - - AOT of '{0}' was requested but was not found - - - - Exclusion of AOT of '{0}' was requested but was not found - - - - The main template could not be expanded to `{0}`. - - - - Failed to compile the generated code for P/Invoke methods. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot build a signature for type `{0}`. - - - - The registrar found an invalid type `{0}` in signature for method `{2}`. Use `{1}` instead. - - - - The registrar found an invalid type `{0}` in signature for method `{1}`: The type implements INativeObject, but does not have a constructor that takes two (IntPtr, bool) arguments. - - - - The registrar cannot marshal the return value for type `{0}` in signature for method `{1}`. - - - - The registrar cannot marshal the return value of type `{0}` in the method `{1}.{2}`. - - - - The registrar cannot marshal the parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot get the ObjectiveC type for managed type `{0}`. - - - - Failed to compile the generated registrar code. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot marshal the out parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot build a signature for type `{0}' in method `{1}`. - - - - The registrar found a generic method: '{0}'. Exporting generic methods is not supported, and will lead to random behavior and/or crashes - - - - Unexpected error in the registrar for the method '{0}.{1}' - Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not register the assembly '{0}': {1} - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register two managed types ('{0}' and '{1}') with the same native name ('{2}'). - - - - Could not register the selector '{0}' of the member '{1}.{2}' because the selector is already registered on the member '{3}'. - - - - The registrar found an unknown field type '{0}' in field '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - 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). - - - - The type of the variadic parameter in the variadic function '{0}' must be System.IntPtr. - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid RegisterAttribute property {1} found on '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid AdoptsAttribute found on '{0}': expected 1 constructor arguments, got {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}.{1}': unknown field {2}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid {0} found on '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': should have 1 constructor arguments, found {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': could not find the underlying enum type of {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found an invalid type '{0}' in signature for method '{1}': The interface must have a Protocol attribute specifying its wrapper type. - - - - Cannot register two managed protocols ('{0}' and '{1}') with the same native name ('{2}'). - - - - Cannot register more than one interface method for the method '{0}.{1}'. - - - - The registrar found an invalid generic parameter type '{0}' in the parameter {2} of the method '{1}'. The generic parameter must have an 'NSObject' constraint. - - - - The registrar found an invalid generic return type '{0}' in the method '{1}'. The generic return type must have an 'NSObject' constraint. - - - - The registrar cannot export static methods in generic classes ('{0}'). - - - - The registrar cannot export static properties in generic classes ('{0}.{1}'). - - - - The registrar found an invalid generic return type '{0}' in the property '{1}.{2}'. The return type must have an 'NSObject' constraint. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) Please select a newer SDK in your app's {3} Build options. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) This configuration is not supported with the static registrar (pass --registrar:dynamic as an additional mmp argument in your project's Mac Build option to select). Alternatively select a newer SDK in your app's Mac Build options. - - - - The member '{0}' has an Export attribute without a selector. A selector is required. - - - - The registrar cannot marshal the parameter type '{0}' of the parameter '{1}' in the method '{2}.{3}' - - - - The method '{0}.{1}' is implementing '{2}.{3}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. Properties with the [Connect] attribute must have a property type of NSObject (or a subclass of NSObject). - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the variadic method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register the selector '{0}' on the member '{1}.{2}' because Xamarin.iOS implicitly registers this selector. - - - - Invalid enum '{0}': enums with the [Native] attribute must have a underlying enum type of either 'long' or 'ulong'. - - The following are literal names and should not be translated: enum, [Native], long, ulong. -{0} - The full name of the C# enum. - - - - The Name parameter of the Registrar attribute on the class '{0}' ('{3}') contains an invalid character: '{1}' (0x{2}). - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found a generic protocol: '{0}'. Exporting generic protocols is not supported. - - - - Cannot register the extension method '{0}.{1}' because the type of the first parameter ('{2}') does not match the category type ('{3}'). - - - - Cannot register the type '{0}' because the category type '{1}' in its Category attribute does not inherit from NSObject. - - - - Cannot register the type '{0}' because the Type property in its Category attribute isn't set. - - - - Cannot register the type '{0}' as a category because it implements INativeObject or subclasses NSObject. - - - - Cannot register the type '{0}' as a category because it's generic. - - - - Cannot register the method '{0}.{1}' as a category method because it's generic. - - - - Cannot register two categories ('{0}' and '{1}') with the same native name ('{2}') - - - - Cannot register the category method '{0}.{1}' because at least one parameter is required for extension methods (and its type must match the category type '{2}'). - - - - Cannot register the constructor {0}.{1} in the category {0} because constructors in categories are not supported. - - - - Cannot register the method '{0}.{1}' as a category method because category methods must be static. - - - - Invalid character '{0}' (0x{1}) found in selector '{2}' for '{3}.{4}' - - - - The registrar found an unsupported structure '{0}': All fields in a structure must also be structures (field '{1}' with type '{2}' is not a structure). - - - - - The type '{0}' is not available in {3} {4} (it was introduced in {3} {5}){6} Please build with a newer {3} SDK (usually done by using the most recent version of Xcode). - - - - The type '{0}' (used as a base type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the base type. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a parameter in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as the property type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the property. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a return type in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - Internal error in the registrar ({0} ctor with {1} arguments). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (Unknown availability kind: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Cannot export the property '{0}' because its selector '{1}' is an Objective-C keyword. Please use a different name. - - - - The registrar couldn't find the type 'System.Void' in any of the referenced assemblies. - - - - Cannot register the method '{0}' because the signature contains a type ({1}) that isn't a reference type. - - - - Cannot register the method '{0}' because the signature contains a generic type ({1}) with a generic argument type that doesn't implement INativeObject ({2}). - - - - Cannot register the type '{0}' because its Objective-C name '{1}' is an Objective-C keyword. Please use a different name. - - - - Failed to generate a P/Invoke wrapper for {0}: {1} - - - - The registrar can't convert from '{0}' to '{1}' for the return value in the method {2}. - - - - The BindAs attribute on the return value of the method {0} is invalid: the BindAs type {1} is different from the return type {2}. - - - - The BindAs attribute on the parameter #{0} is invalid: the BindAs type {1} is different from the parameter type {2}. - - - - The BindAs attribute on the property {0}.{1} is invalid: the BindAs type {2} is different from the property type {1}. - - - - The registrar can't convert from '{0}' to '{1}' for the parameter '{2}' in the method {3}. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because {0} doesn't have a specific signature. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the delegate to block conversion type for the return value of the method {0}. - - - - The 'ProtocolType' parameter of the 'Adopts' attribute used in class '{0}' contains an invalid character. Value used: '{1}' Invalid Char: '{2}' - - - - The class '{0}' will not be registered because the WatchKit framework has been removed from the iOS SDK. - - - - The registrar found the abstract type '{0}' in the signature for '{1}'. Abstract types should not be used in the signature for a member exported to Objective-C. - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Missing '{0}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Could not find neither the '{0}' nor the '{1}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Failed to compile. Error code - {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Failed to compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The assembly '{0}' can't be AOT-compiled for 32-bit architectures because the native code is too big for the 32-bit ARM architecture. - - - - The compiler output is too long, it's been limited to 1000 lines. - - - - Native linking failed with error code 1. Check build log for details. - - - - Native linking failed. Please review the build log and the user flags provided to gcc: {0} - - - - Native linking failed. Please review the build log. - - - - Mono.framework MDK is missing. Please install the MDK for your Mono.framework version from https://www.mono-project.com/download/ - - - - Native linking warning: {0} - - - - Can't find {0}, likely because of a corrupted Xamarin.Mac installation. Please reinstall Xamarin.Mac. - - - - Native linking failed. Please review the build log. - - - - Invalid architecture '{0}'. The only valid architectures is x86_64. - - - - Native linking error: {0} - - - - Native linking failed, undefined symbol: {0}. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. - - - - Native linking failed, undefined Objective-C class: {0}. The symbol '{1}' could not be found in any of the libraries or frameworks linked with your application. - - - - Native linking failed, duplicate symbol: '{0}'. - - - - Duplicate symbol in: {0} (Location related to previous error) - - - - Native linking failed, undefined symbol: {0}. This symbol was referenced by the managed member {1}.{2}. Please verify that all the necessary frameworks have been referenced and native libraries linked. - - - - References to '{0}' might require additional -framework=XXX or -lXXX instructions to the native linker - - - - Native linking failed for '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Native linking failed because the linker command line was too long ({0} characters). - - - - Can't ignore the dynamic symbol {0} (--ignore-dynamic-symbol={0}) because it was not detected as a dynamic symbol. - - - - Not linking with WatchKit because it has been removed from iOS. - - - - Skipping framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - Linking against framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - The native linker failed to execute: {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Did not link with the framework '{0}', because the current {1} SDK does not contain support for this framework in the simulator. - This is a warning explaining why a native framework won't be referenced from the app when building for the simulator. The following are literal names and should not be translated: SDK - {0}: The name of the native framework - {1}: The current platform (will be either iOS, tvOS, watchOS or macOS). - - - - Missing 'strip' tool. Please install Xcode 'Command-Line Tools' component - - - - Missing 'dsymutil' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to generate the debug symbols (dSYM directory). Please review the build log. - - - - Failed to strip the final binary. Please review the build log. - - - - Missing 'lipo' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to create the a fat library. Please review the build log. - - - - Missing '{0}' tool. Please install Xcode 'Command-Line Tools' component - - - - Xcode license agreement may not have been accepted. Please launch Xcode. - - - - Failed to execute the tool '{0}', it failed with an error code '{1}'. Please check the build log for details. - - - - install_name_tool failed with an error code '{0}'. Check build log for details. - - - - lipo failed with an error code '{0}'. Check build log for details. - - - - pkg-config failed with an error code '{0}'. Check build log for details. - - - - Could not find {0}. Please install the Mono.framework from https://mono-project.com/Downloads - - - - Failed to execute pkg-config: '{0}'. Check build log for details. - - - - The tool xcrun failed to find result when looking for the tool '{0}' (the file '{1}' does not exist). Check build log for details. - - - - Internal consistency error. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new. - - - \ No newline at end of file diff --git a/tools/mtouch/TranslatedAssemblies/Errors.sv.resx b/tools/mtouch/TranslatedAssemblies/Errors.sv.resx deleted file mode 100644 index 5a8b3c93a0a1..000000000000 --- a/tools/mtouch/TranslatedAssemblies/Errors.sv.resx +++ /dev/null @@ -1,1700 +0,0 @@ - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - The error message for code {0} could not be found. Please report this missing message on GitHub at https://github.com/xamarin/xamarin-macios/issues/new - - This is the default message when an error code can not be found. - - - - Unexpected error - Please fill a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - '-devname' was provided without any device-specific action - - - - This version of Xamarin.Mac requires Mono {0} (the current Mono version is {1}). Please update the Mono.framework from http://mono-project.com/Downloads - - - - Could not parse the environment variable '{0}' - - - - Application name '{0}.exe' conflicts with an SDK or product assembly (.dll) name. - - - - New refcounting logic requires SGen to be enabled too. - - - - The output directory * does not exist. - - - - There is no devel platform at {0}, use --platform=PLAT to specify the SDK. - - - - The root assembly '{0}' does not exist - - - - You should provide one root assembly only, found {0} assemblies: '{1}' - - - - Error while loading assemblies: {0}. - - - - Could not parse the command line arguments: {0} - - - - {0} was built against a more recent runtime ({1}) than Xamarin.iOS supports. - - - - Incomplete data is provided to complete *. - - - - Profiling support requires sgen to be enabled too. - - - - The iOS {0} SDK does not support building applications targeting {1}. - - - - This is the sv MT0015 error message. - - - - The option '{0}' has been deprecated. - - - - You should provide a root assembly. - - - - Unknown command line argument: '{0}' - - - - Only one --[log|install|kill|launch]dev or --[launch|debug]sim option can be used. - - - - The valid options for '{0}' are '{1}'. - - - - 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). - - - - The options '--unsupported--enable-generics-in-registrar' and '--registrar' are not compatible. - - - - The root assembly {0} conflicts with another assembly ({1}). - - - - Application name '{0}.exe' conflicts with another user assembly. - - - - Could not find required file '{0}'. - - - - No SDK version was provided. Please add --sdk=X.Y to specify which {0} SDK should be used to build your application. - - - - Could not parse the command line argument '-{0}': {1} - - - - The options '\*' and '\*' are not compatible. - - - - 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 - - - - REPL (--enable-repl) is only supported in the simulator (--sim). - - - - The executable name ({0}) and the app name ({1}) are different, this may prevent crash logs from getting symbolicated properly. - - - - The command line arguments '--enable-background-fetch' and '--launch-for-background-fetch' require '--launchsim' too. - - - - The option '--debugtrack' is ignored unless '--debug' is also specified. - - - - A Xamarin.iOS project must reference either monotouch.dll or Xamarin.iOS.dll - - - - Cannot reference '{0}.dll' in a {1} project - it is implicitly referenced by '{2}'. - - - - Cannot launch a * simulator for a * app. Please enable the correct architecture(s) in your project's iOS Build options (Advanced page). - - - - 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). - - - - The old registrars (--registrar:oldstatic|olddynamic) are not supported when referencing Xamarin.iOS.dll. - - - - Applications targeting ARMv6 cannot reference Xamarin.iOS.dll. - - - - Could not find the assembly '\*', referenced by '\*'. - - - - Cannot reference '{0}' in a {1} app. - - - - No reference to either monotouch.dll or Xamarin.iOS.dll was found. A reference to monotouch.dll will be added. - - - - The Boehm garbage collector is not supported. The SGen garbage collector has been selected instead. - - - - --listsim is only supported with Xcode 6.0 or later. - - - - --extension is only supported when using the iOS 8.0 (or later) SDK. - - - - 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. - - - - {0}.framework is supported only if deployment target is 8.0 or later. {0} features might not work correctly. - - - - You cannot provide a root assembly if --no-root-assembly is passed, found {0} assemblies: '{1}' - - - - {3} {0} requires Xcode {4} or later. The current Xcode version (found in {2}) is {1}. - - - - An output directory (--output) is required if --no-root-assembly is passed. - - - - No command specified. - - - - Unable to canonicalize the path '{0}': {1} ({2}). - - - - The Xcode path '{0}' does not exist. - - - - Cannot find Xcode in the default location (/Applications/Xcode.app). Please install Xcode, or pass a custom path using --sdkroot <path>. - - - - Cannot determine the path to Xcode.app from the sdk root '{0}'. Please specify the full path to the Xcode.app bundle. - - - - The Xcode.app '{0}' is invalid (the file '{1}' does not exist). - - - - Could not find the currently selected Xcode on the system: {0} - - - - Could not find the currently selected Xcode on the system. 'xcode-select --print-path' returned '{0}', but that directory does not exist. - - - - No Xcode.app specified (using --sdkroot), using the system Xcode as reported by 'xcode-select --print-path': {0} - - - - No Xcode.app specified (using --sdkroot or 'xcode-select --print-path'), using the default Xcode instead: {0} - - - - Cannot find the executable in the extension * (no CFBundleExecutable entry in its Info.plist) - - - - Xamarin.iOS only supports embedded frameworks with Unified projects. - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 8.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Xamarin.iOS only supports embedded frameworks when deployment target is at least 2.0 (current deployment target: '{0}'; embedded frameworks: '{1}') - - - - Invalid build registrar assembly: * - - - - Invalid registrar: {0} - - - - Invalid value for target framework: {0}. - - - - Invalid target framework: {0}. Valid target frameworks are: {1}. - - - - Unknown platform: {0}. This usually indicates a bug in {1}; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Extensions are not supported for the platform '{0}'. - - - - {4} {0} does not support a deployment target of {1} for {3} (the minimum is {2}). Please select a newer deployment target in your project's Info.plist. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The minimum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - {4} {0} does not support a deployment target of {1} for {3} (the maximum is {2}). Please select an older deployment target in your project's Info.plist or upgrade to a newer version of {4}. - - The following are literal names and should not be translated: SDK, Xcode -{0} - The version number of the Xamarin product. -{1} - The name of the deployment target such as a device, simulator, etc. -{2} - The maximum version number. -{3} - The platform name, such as 'iOS'. -{4} - The produce name such as Xamarin.iOS or Xamarin.Mac. - - - - Invalid architecture '{0}' for {1} projects. Valid architectures are: {2} - - - - No architecture specified (using the --abi argument). An architecture is required for {0} projects. - - - - WatchOS projects must be extensions. - - - - Incremental builds are enabled with a deployment target < 8.0 (currently {0}). This is not supported (the resulting application will not launch on iOS 9), so the deployment target will be set to 8.0. - - - - The recommended Xcode version for {4} {0} is Xcode {3} or later. The current Xcode version (found in {2}) is {1}. - - - - No executable was copied into the app bundle. Please contact 'support@xamarin.com' - - - - Disabling the new refcount logic is deprecated. - - - - The command line argument --download-crash-report also requires --download-crash-report-to. - - - - REPL (--enable-repl) is only supported when linking is not used (--nolink). - - - - Asm-only bitcode is not supported on watchOS. Use either --bitcode:marker or --bitcode:full. - - - - Bitcode is not supported in the simulator. Do not pass --bitcode when building for the simulator. - - - - No reference to '{0}' was found. It will be added automatically. - - - - A target framework (--target-framework) must be specified. - - - - Incremental builds (--fastdev) is not supported with the Boehm GC. Incremental builds will be disabled. - - - - The GC must be in cooperative mode for watchOS apps. Please remove the --coop:false argument to mtouch. - - - - The option '{0}' cannot take the value '{1}' when cooperative mode is enabled for the GC. - - - - The target framework '{0}' is deprecated. Use '{1}' instead. - - - - - - Could not find 'mlaunch'. - - - - - Aot files could not be copied to the destination directory {0}: {1} - - - - Aot files could not be copied to the destination directory {0}: Could not start process. - - - - Aot files could not be copied to the destination directory {0} - - - - No reference to Xamarin.iOS.dll was found. - - - - machine.config file '{0}' can not be found. - - - - - Internal error: {0}. Please file an issue at https://github.com/xamarin/xamarin-macios/issues/new. - - - - Invalid assembly build target: '{0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly '{0}' is specified multiple times in --assembly-build-target arguments. - - - - The assemblies '{0}' and '{1}' have the same target name ('{2}'), but different targets ('{3}' and '{4}'). - - - - The static object '{0}' contains more than one assembly ('{1}'), but each static object must correspond with exactly one assembly. - - - - No assembly build target was specified for '{0}'. - - - - The assembly build target name '{0}' is invalid: the character '{1}' is not allowed. - - - - The assemblies '{0}' have different custom LLVM optimizations ('{1}'), which is not allowed when they are all compiled to a single binary. - - - - The assembly build target '{0}' did not match any assemblies. - - - - The assembly '{0}' was loaded from a different path than the provided path (provided path: {1}, actual path: {2}). - - - - 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. - - - - Bitcode has been enabled because this version of Xamarin.iOS does not support building watchOS projects using LLVM without enabling bitcode. - - - - Native code sharing has been disabled because {0} - - - - the container app's deployment target is earlier than iOS 8.0 (it's {0}). - - - - the container app includes I18N assemblies ({0}). - - - - the container app has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - Native code sharing has been disabled for the extension '{0}' because {1} - - - - the bitcode options differ between the container app ({0}) and the extension ({1}). - - - - the --assembly-build-target options are different between the container app ({0}) and the extension ({1}). - - - - the I18N assemblies are different between the container app ({0}) and the extension ({1}). - - - - the arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - the other arguments to the AOT compiler are different between the container app ({0}) and the extension ({1}). - - - - LLVM is not enabled or disabled in both the container app ({0}) and the extension ({1}). - - - - the managed linker settings are different between the container app ({0}) and the extension ({1}). - - - - the skipped assemblies for the managed linker are different between the container app ({0}) and the extension ({1}). - - - - the extension has custom xml definitions for the managed linker ({0}). - - A warning related to custom linker configuration, see: https://docs.microsoft.com/xamarin/cross-platform/deploy-test/linker. The following are literal names and should not be translated: xml, linker -{0} - A list of xml file names. - - - - the interpreter settings are different between the container app ({0}) and the extension ({1}). - - - - the interpreted assemblies are different between the container app ({0}) and the extension ({1}). - - - - the container app does not build for the ABI {0} (while the extension is building for this ABI). - - - - the container app is building for the ABI {0}, which is not compatible with the extension's ABI ({1}). - - - - the remove-dynamic-registrar optimization differ between the container app ({0}) and the extension ({1}). - - - - the container app is referencing the assembly '{0}' from '{1}', while the extension references a different version from '{2}'. - - - - Hybrid AOT compilation requires all assemblies to be AOT compiled - - - - It is recommended to reference dynamic symbols using code (--dynamic-symbol-mode=code) when bitcode is enabled. - - - - Invalid architecture: {0}. 32-bit architectures are not supported when deployment target is 11 or later. - - - - Can't launch a 32-bit app on a simulator that only supports 64-bit. - - - - The directory {0} containing the mono symbols could not be found. - - - - The executable assembly {0} does not reference {1}.dll. - - - - Could not set the current language to '{0}' (according to LANG={1}): {2} - - - - The --assembly-build-target command-line argument is ignored in the simulator. - - - - Incremental builds have been disabled because incremental builds are not supported in the simulator. - - - - 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. - - - - Could not touch the file '{0}': {1} - - - - Debugging symbol file for '{0}' does not match the assembly and is ignored. - - - - No root assemblies found. You should provide at least one root assembly. - - - - Product assembly '{0}' not found in assembly list: '{1}' - - - - Unknown optimization: '{0}'. Valid optimizations are: {1}. - - - - Found more than 1 assembly matching '{0}' choosing first:{1}{2} - - - - 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. - - - - Cannot find the assembly '{0}' referenced from '{1}'. - - - - Cannot find the assembly '{0}', referenced by a {2} attribute in '{1}'. - - - - File '{0}' is not a valid framework. - - - - The interpreter is not supported in the simulator. Switching to REPL which provide the same extra features on the simulator. - - - - Cannot find the assembly '{0}', passed as an argument to --interpreter. - - - - Projects using the Classic API are not supported anymore. Please migrate the project to the Unified API. - - - - Building 32-bit apps is not supported anymore. Please change the architecture in the project's Mac Build options to 'x86_64'. - - - - Please use device specific builds on WatchOS when building for Debug. - - - - ARM64_32 Debug mode requires --interpreter[=all], forcing it. - - - - Unable to parse the cflags '{0} from pkg-config: {1} - - - - Unable to parse the linker flags '{0}' from the LinkWith attribute for the library '{1}' in {2} : {3} - - - - Internal error: The interpreter is currently only available for 64 bits. - - - - Internal error: byref array is neither string, NSObject or INativeObject. - - - - Internal error: can't convert from '{0}' to '{1}' in {2}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the smart enum {0} doesn't seem to be a smart enum after all. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: unsupported tokentype ({0}) for {1}. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: the static registrar should not execute unless the linker also executed (or was disabled). A potential workaround is to pass '-f' as an additional {0} argument to force a full build. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: symbol without a name (type: {0}). Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - Internal error: 'can't convert frameworks to frameworks: {0}'. Please file a bug report with a test case (https://github.com/xamarin/xamarin-macios/issues/new). - - - - The assembly {0} was referenced by another assembly, but at the same time linked out by the linker. - - - - The linker output contains more than one assemblies named '{0}':\n\t{1} - - - - Not all assemblies for {0} have link tasks - - - - Link tasks for {0} aren't all the same - - - - The assembly '{0}' was resolved from the system's GAC: {1}. This could potentially be a problem in the future; to avoid such problems, please make sure to not use assemblies only available in the system's GAC. - - - - Unknown platform: {0}. This usually indicates a bug; please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - Debugging symbol file for '{0}' is not valid and was ignored. - - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or use the dynamic registrar or set the managed linker behaviour to Link Platform or Link Framework SDKs Only in your project's Mac Build Options > Linker Behavior (to try to avoid the new APIs). - - - This version of {0} requires the {1} {2} SDK (shipped with Xcode {3}). Either upgrade Xcode to get the required header files or set the managed linker behaviour to Link Framework SDKs Only in your project's iOS Build Options > Linker Behavior (to try to avoid the new APIs). - - - Not linking with the framework {0} (used by the type {1}) because it's not available on the current platform ({2}). - - - Not linking with the framework {0} (referenced by a module reference in {1}) because it's not available on the current platform ({2}). - - - Could not map the iOS version {0} to a macOS version for Mac Catalyst - - - Could not map the macOS version {0} to a corresponding iOS version for Mac Catalyst - - - Could not copy the assembly '{0}' to '{1}': {2} - - - - Could not load the assembly '{0}': {1} - - - - Dependency tracking error: no files to compare. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new with a test case. - - - - Failed to re-use cached version of '{0}': {1}. - - - - Failed to create the executable '{0}': {1} - - - - Could not copy the directory '{0}' to '{1}': {2} - - - - Could not create symlink '{0}' -> '{1}': error {2} - - - - Cannot include different versions of the framework '{0}' - - - - Framework '{0}' included from: {1} (Related to previous error) - - - - Unsupported bitcode platform: {0}. - - - - Unsupported TvOS ABI: {0}. - - - - Could not extract the native library '{0}' from '{1}'. 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'). - - - - Invalid escape sequence when converting .s to .ll, \\ as the last characted in {0}:{1}. - - - - Invalid escape sequence when converting .s to .ll, bad octal escape in {0}:{1} due to {2}. - - - - Could not decompress the native framework '{0}' from '{1}'. Please review the build log for more information from the native 'unzip' command. - - - - The binding library '{0}' contains a user framework ({0}), but embedded user frameworks require iOS 8.0 (the deployment target is {1}). Please set the deployment target in the Info.plist file to at least 8.0. - - - - The required 'Xamarin.Mac.dll' assembly is missing from the references - - - - The assembly '{0}' is not compatible with this tool or profile - - - - {0} {1} could not be found. Target framework '{2}' is unusable to package the application. - - - - Target framework '{0}' is invalid. - - - - useFullXamMacFramework must always target framework .NET 4.5, not '{0}' which is invalid. - - - - Mismatch between Xamarin.Mac reference '{0}' and target framework selected '{1}'. - - - - Can not resolve reference: {0} - - - - One or more reference(s) to type '{0}' already exists inside '{1}' before linking - - - - One or more reference(s) to type '{0}' still exists inside '{1}' after linking - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Not a Mach-O static library (unknown header '{0}', expected '!<arch>'). - - - - Not a Mach-O dynamic library (unknown header '0x{0}'): {1}. - - - - Unknown format for fat entry at position {0} in {1}. - - - - File of type {0} is not a MachO file ({1}). - - - - Invalid entry '{0}' in the static library '{1}', entry header doesn't end with 0x60 0x0A (found '0x{2} 0x{3}') - - - - Could not link assemblies. {0} - - - - Can not resolve reference: {0} - - - - Option '--optimize={0}{1}' will be ignored since the static registrar is not enabled - - - - - Option '--optimize={0}{1}' will be ignored since linking is disabled - - - - Option '--optimize={0}' will be ignored since it's only applicable to {1}. - This is a warning that is shown when the command-line option --optimize=... is not valid for a particular platform -{0} - The optimization option that is not valid for the current platform -{1} - The platforms in question, such as 'iOS'. - - - - Extra linker definitions file '{0}' could not be located. - - - - Definitions from '{0}' could not be parsed. - - - - Can not load mscorlib.dll from: '{0}'. Please reinstall Xamarin.iOS. - - - - Native library '{0}' was referenced but could not be found. - - - - Failed to resolve "{0}" reference from "{1}" - - - - Xamarin.Mac Unified API against a full .NET framework does not support linking SDK or All assemblies. Pass either the `-nolink` or `-linkplatform` flag. - - Using the linker is not supported in certain situations in Xamarin.Mac, see: https://docs.microsoft.com/xamarin/mac/deploy-test/linker. The following are literal names and should not be translated: Xamarin.Mac Unified API, .NET, SDK, All, `-nolink`, and `-linkplatform`. - - - - Referenced by {0}.{1} - - - - Unknown HttpMessageHandler `{0}`. Valid values are HttpClientHandler (default), CFNetworkHandler or NSUrlSessionHandler - - - - Only first {0} of {1} \"Referenced by\" warnings shown. - - - - Failed to resolve the reference to \"{0}\", referenced in \"{1}\". The app will not include the referenced assembly, and may fail at runtime. - - - - Unable to link assembly '{0}' as it is mixed-mode. - - - - Invalid HttpMessageHandler `{0}` for watchOS. The only valid value is NSUrlSessionHandler. - - - - Could not process XML description: {0} - - - - The assembly '{0}' is referenced from two different locations: '{1}' and '{2}'. - - - - Can not load the root assembly '{0}'. - - - - - The linker step '{0}' failed processing `{1}`. - This is a message when processing an assembly/type/field/method/property/event fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly/type/field/method/property/event that failed processing. - - - - - - - - - - - - Can't resolve the reference '{0}', referenced from the method '{1}' in '{2}'. - - - - Error processing the method '{0}' in the assembly '{1}': {2} - - - - Error processing the method '{0}' in the assembly '{1}' - - - - Error processing assembly '{0}': {1} - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect fields. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect properties. - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a '{1}' parameter type (expected 'ObjCRuntime.BindingImplOptions). - - - - The [BindingImpl] attribute on the member '{0}' is invalid: did not expect a constructor with a {1} parameters (expected 1 parameters). - - - - The property {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This property will throw an exception if called. - - - - The method {0}.{1} contains a '{2}' exception clause, which is currently not supported when compiling for bitcode. This method will throw an exception if called. - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because the previous instruction was unexpected ({3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} at offset {1} because could not determine the type of the delegate type of the first argument (instruction: {3}) - - - - Could not optimize the call to BlockLiteral.{2} in {0} because the type of the value passed as the first argument (the trampoline) is {1}, which makes it impossible to compute the block signature. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1} because no [UserDelegateType] attribute could be found on {2}. - - - - Could not optimize the call to BlockLiteral.SetupBlock in {0} at offset {1}: {2}. - - - - It's not safe to remove the dynamic registrar, because {0} references '{1}.{2} ({3})'. - - - - {0} was stripped of architectures except {1} to comply with App Store restrictions. This could break existing codesigning signatures. Consider stripping the library with lipo or disabling with --optimize=-trim-architectures - - - - Xamarin.Mac 'Partial Static' registrar does not support linking. Disable linking or use another registrar mode. - - - - Can not find the corlib assembly '{0}' in the list of loaded assemblies. - - - - - - - - - - - The linker step '{0}' failed during processing: {1} - This is a message when processing fails in the linker. - {0} - The name of the step that fails. - {1} - A string describing what failed. - - - - The linker step '{0}' failed while processing {1}: {2} - This is a message when processing an assembly fails in the linker. - {0} - The name of the step that fails. - {1} - The name of the assembly that failed processing. - {1} - A string describing what failed - - - - - - - - - - - Could not {0} the assembly '{1}' - - - - Debugging is not supported when building with LLVM. Debugging has been disabled. - - - - Could not AOT the assembly '{0}' because it doesn't exist. - - - - The dependency '{0}' of the assembly '{1}' was not found. Please review the project's references. - - - - 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. - - - - Debug info files (*.mdb / *.pdb) will not be loaded when llvm is enabled. - - - - Bitcode support requires the use of LLVM (--abi=arm64+llvm etc.) - - - - AOT of '{0}' was requested but was not found - - - - Exclusion of AOT of '{0}' was requested but was not found - - - - The main template could not be expanded to `{0}`. - - - - Failed to compile the generated code for P/Invoke methods. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot build a signature for type `{0}`. - - - - The registrar found an invalid type `{0}` in signature for method `{2}`. Use `{1}` instead. - - - - The registrar found an invalid type `{0}` in signature for method `{1}`: The type implements INativeObject, but does not have a constructor that takes two (IntPtr, bool) arguments. - - - - The registrar cannot marshal the return value for type `{0}` in signature for method `{1}`. - - - - The registrar cannot marshal the return value of type `{0}` in the method `{1}.{2}`. - - - - The registrar cannot marshal the parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot get the ObjectiveC type for managed type `{0}`. - - - - Failed to compile the generated registrar code. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar cannot marshal the out parameter of type `{0}` in signature for method `{1}`. - - - - The registrar cannot build a signature for type `{0}' in method `{1}`. - - - - The registrar found a generic method: '{0}'. Exporting generic methods is not supported, and will lead to random behavior and/or crashes - - - - Unexpected error in the registrar for the method '{0}.{1}' - Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not register the assembly '{0}': {1} - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register two managed types ('{0}' and '{1}') with the same native name ('{2}'). - - - - Could not register the selector '{0}' of the member '{1}.{2}' because the selector is already registered on the member '{3}'. - - - - The registrar found an unknown field type '{0}' in field '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - 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). - - - - The type of the variadic parameter in the variadic function '{0}' must be System.IntPtr. - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid RegisterAttribute property {1} found on '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid AdoptsAttribute found on '{0}': expected 1 constructor arguments, got {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}.{1}': unknown field {2}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid {0} found on '{1}.{2}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': should have 1 constructor arguments, found {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Invalid BindAsAttribute found on '{0}': could not find the underlying enum type of {1}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found an invalid type '{0}' in signature for method '{1}': The interface must have a Protocol attribute specifying its wrapper type. - - - - Cannot register two managed protocols ('{0}' and '{1}') with the same native name ('{2}'). - - - - Cannot register more than one interface method for the method '{0}.{1}'. - - - - The registrar found an invalid generic parameter type '{0}' in the parameter {2} of the method '{1}'. The generic parameter must have an 'NSObject' constraint. - - - - The registrar found an invalid generic return type '{0}' in the method '{1}'. The generic return type must have an 'NSObject' constraint. - - - - The registrar cannot export static methods in generic classes ('{0}'). - - - - The registrar cannot export static properties in generic classes ('{0}.{1}'). - - - - The registrar found an invalid generic return type '{0}' in the property '{1}.{2}'. The return type must have an 'NSObject' constraint. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) Please select a newer SDK in your app's {3} Build options. - - - - Your application is using the '{0}' framework, which isn't included in the {3} SDK you're using to build your app (this framework was introduced in {3} {2}, while you're building with the {3} {1} SDK.) This configuration is not supported with the static registrar (pass --registrar:dynamic as an additional mmp argument in your project's Mac Build option to select). Alternatively select a newer SDK in your app's Mac Build options. - - - - The member '{0}' has an Export attribute without a selector. A selector is required. - - - - The registrar cannot marshal the parameter type '{0}' of the parameter '{1}' in the method '{2}.{3}' - - - - The method '{0}.{1}' is implementing '{2}.{3}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. - - - - The registrar cannot marshal the property type '{0}' of the property '{1}.{2}'. Properties with the [Connect] attribute must have a property type of NSObject (or a subclass of NSObject). - - - - The registrar found a signature mismatch in the method '{0}.{1}' - the selector '{4}' indicates the variadic method takes {2} parameters, while the managed method has {3} parameters. - - - - Cannot register the selector '{0}' on the member '{1}.{2}' because Xamarin.iOS implicitly registers this selector. - - - - Invalid enum '{0}': enums with the [Native] attribute must have a underlying enum type of either 'long' or 'ulong'. - - The following are literal names and should not be translated: enum, [Native], long, ulong. -{0} - The full name of the C# enum. - - - - The Name parameter of the Registrar attribute on the class '{0}' ('{3}') contains an invalid character: '{1}' (0x{2}). - - - - Invalid {0} found on '{1}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar found a generic protocol: '{0}'. Exporting generic protocols is not supported. - - - - Cannot register the extension method '{0}.{1}' because the type of the first parameter ('{2}') does not match the category type ('{3}'). - - - - Cannot register the type '{0}' because the category type '{1}' in its Category attribute does not inherit from NSObject. - - - - Cannot register the type '{0}' because the Type property in its Category attribute isn't set. - - - - Cannot register the type '{0}' as a category because it implements INativeObject or subclasses NSObject. - - - - Cannot register the type '{0}' as a category because it's generic. - - - - Cannot register the method '{0}.{1}' as a category method because it's generic. - - - - Cannot register two categories ('{0}' and '{1}') with the same native name ('{2}') - - - - Cannot register the category method '{0}.{1}' because at least one parameter is required for extension methods (and its type must match the category type '{2}'). - - - - Cannot register the constructor {0}.{1} in the category {0} because constructors in categories are not supported. - - - - Cannot register the method '{0}.{1}' as a category method because category methods must be static. - - - - Invalid character '{0}' (0x{1}) found in selector '{2}' for '{3}.{4}' - - - - The registrar found an unsupported structure '{0}': All fields in a structure must also be structures (field '{1}' with type '{2}' is not a structure). - - - - - The type '{0}' is not available in {3} {4} (it was introduced in {3} {5}){6} Please build with a newer {3} SDK (usually done by using the most recent version of Xcode). - - - - The type '{0}' (used as a base type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the base type. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a parameter in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as the property type of {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the property. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - The type '{0}' (used as a return type in {1}) is not available in {2} {3} (it was introduced in {2} {4}){5} Please build with a newer {2} SDK (usually done by using the most recent version of Xcode). - - This is a message for usage of a type that is not available targeting older platform versions. The following are literal names and should not be translated: SDK, Xcode -{0} - The full C# type name. -{1} - The name of the method. -{2} - The platform name, such as 'iOS'. -{3} - The current platform version number. -{4} - The platform version where the type was introduced. -{5} - An additional message about the platform version introducing the type. - - - - Internal error in the registrar ({0} ctor with {1} arguments). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (Unknown availability kind: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Cannot export the property '{0}' because its selector '{1}' is an Objective-C keyword. Please use a different name. - - - - The registrar couldn't find the type 'System.Void' in any of the referenced assemblies. - - - - Cannot register the method '{0}' because the signature contains a type ({1}) that isn't a reference type. - - - - Cannot register the method '{0}' because the signature contains a generic type ({1}) with a generic argument type that doesn't implement INativeObject ({2}). - - - - Cannot register the type '{0}' because its Objective-C name '{1}' is an Objective-C keyword. Please use a different name. - - - - Failed to generate a P/Invoke wrapper for {0}: {1} - - - - The registrar can't convert from '{0}' to '{1}' for the return value in the method {2}. - - - - The BindAs attribute on the return value of the method {0} is invalid: the BindAs type {1} is different from the return type {2}. - - - - The BindAs attribute on the parameter #{0} is invalid: the BindAs type {1} is different from the parameter type {2}. - - - - The BindAs attribute on the property {0}.{1} is invalid: the BindAs type {2} is different from the property type {1}. - - - - The registrar can't convert from '{0}' to '{1}' for the parameter '{2}' in the method {3}. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because {0} doesn't have a specific signature. - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the block to delegate conversion method for the method {0}'s parameter #{1}. - - - - Unable to locate the delegate to block conversion type for the return value of the method {0}. - - - - The 'ProtocolType' parameter of the 'Adopts' attribute used in class '{0}' contains an invalid character. Value used: '{1}' Invalid Char: '{2}' - - - - The class '{0}' will not be registered because the WatchKit framework has been removed from the iOS SDK. - - - - The registrar found the abstract type '{0}' in the signature for '{1}'. Abstract types should not be used in the signature for a member exported to Objective-C. - - - - Internal error in the registrar (BindAs parameters can't be ref/out: {0}). Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The registrar can't compute the block signature for the delegate of type {0} in the method {1} because it couldn't find the Invoke method of the delegate type. - - - - Missing '{0}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Could not find neither the '{0}' nor the '{1}' compiler. Please install Xcode 'Command-Line Tools' component - - - - Failed to compile. Error code - {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Failed to compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Could not compile the file(s) '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - The assembly '{0}' can't be AOT-compiled for 32-bit architectures because the native code is too big for the 32-bit ARM architecture. - - - - The compiler output is too long, it's been limited to 1000 lines. - - - - Native linking failed with error code 1. Check build log for details. - - - - Native linking failed. Please review the build log and the user flags provided to gcc: {0} - - - - Native linking failed. Please review the build log. - - - - Mono.framework MDK is missing. Please install the MDK for your Mono.framework version from https://www.mono-project.com/download/ - - - - Native linking warning: {0} - - - - Can't find {0}, likely because of a corrupted Xamarin.Mac installation. Please reinstall Xamarin.Mac. - - - - Native linking failed. Please review the build log. - - - - Invalid architecture '{0}'. The only valid architectures is x86_64. - - - - Native linking error: {0} - - - - Native linking failed, undefined symbol: {0}. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. - - - - Native linking failed, undefined Objective-C class: {0}. The symbol '{1}' could not be found in any of the libraries or frameworks linked with your application. - - - - Native linking failed, duplicate symbol: '{0}'. - - - - Duplicate symbol in: {0} (Location related to previous error) - - - - Native linking failed, undefined symbol: {0}. This symbol was referenced by the managed member {1}.{2}. Please verify that all the necessary frameworks have been referenced and native libraries linked. - - - - References to '{0}' might require additional -framework=XXX or -lXXX instructions to the native linker - - - - Native linking failed for '{0}'. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Native linking failed because the linker command line was too long ({0} characters). - - - - Can't ignore the dynamic symbol {0} (--ignore-dynamic-symbol={0}) because it was not detected as a dynamic symbol. - - - - Not linking with WatchKit because it has been removed from iOS. - - - - Skipping framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - Linking against framework '{0}'. It is prohibited (rejected) by the Mac App Store - - - - The native linker failed to execute: {0}. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new - - - - Did not link with the framework '{0}', because the current {1} SDK does not contain support for this framework in the simulator. - This is a warning explaining why a native framework won't be referenced from the app when building for the simulator. The following are literal names and should not be translated: SDK - {0}: The name of the native framework - {1}: The current platform (will be either iOS, tvOS, watchOS or macOS). - - - - Missing 'strip' tool. Please install Xcode 'Command-Line Tools' component - - - - Missing 'dsymutil' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to generate the debug symbols (dSYM directory). Please review the build log. - - - - Failed to strip the final binary. Please review the build log. - - - - Missing 'lipo' tool. Please install Xcode 'Command-Line Tools' component - - - - Failed to create the a fat library. Please review the build log. - - - - Missing '{0}' tool. Please install Xcode 'Command-Line Tools' component - - - - Xcode license agreement may not have been accepted. Please launch Xcode. - - - - Failed to execute the tool '{0}', it failed with an error code '{1}'. Please check the build log for details. - - - - install_name_tool failed with an error code '{0}'. Check build log for details. - - - - lipo failed with an error code '{0}'. Check build log for details. - - - - pkg-config failed with an error code '{0}'. Check build log for details. - - - - Could not find {0}. Please install the Mono.framework from https://mono-project.com/Downloads - - - - Failed to execute pkg-config: '{0}'. Check build log for details. - - - - The tool xcrun failed to find result when looking for the tool '{0}' (the file '{1}' does not exist). Check build log for details. - - - - Internal consistency error. Please file a bug report at https://github.com/xamarin/xamarin-macios/issues/new. - - - \ No newline at end of file diff --git a/tools/mtouch/mtouch.csproj b/tools/mtouch/mtouch.csproj index 7027101e35a0..665a2126dce4 100644 --- a/tools/mtouch/mtouch.csproj +++ b/tools/mtouch/mtouch.csproj @@ -531,10 +531,6 @@ Errors.fr.resx Errors.mtouch.fr - - Errors.hu.resx - Errors.mtouch.hu - Errors.it.resx Errors.mtouch.it @@ -547,10 +543,6 @@ Errors.ko.resx Errors.mtouch.ko - - Errors.nl.resx - Errors.mtouch.nl - Errors.pl.resx Errors.mtouch.pl @@ -559,18 +551,10 @@ Errors.pt-BR.resx Errors.mtouch.pt-BR - - Errors.pt-PT.resx - Errors.mtouch.pt-PT - Errors.ru.resx Errors.mtouch.ru - - Errors.sv.resx - Errors.mtouch.sv - Errors.tr.resx Errors.mtouch.tr