- 浏览: 356187 次
- 性别:
- 来自: 福州
-
文章分类
- 全部博客 (145)
- iPhone不能分类的 (37)
- UITableView (7)
- CALayer (4)
- UIButton (2)
- NSFileManager (4)
- UIAlertView (1)
- ASIHTTPRequest (2)
- NSDate (8)
- UIImageView (1)
- UIFont (1)
- Mac OS X (4)
- NSString (5)
- UINavigationBar (2)
- UIView (7)
- UIScrollView (1)
- UIDatePicker (1)
- NSLog (2)
- UIWebView (2)
- MKMapView (6)
- core plot (1)
- UILabel (2)
- UIImage (3)
- NSArray NSMutableArray (2)
- iphone基础知识 (3)
- NSDictionary NSMutableDictionary (1)
- Block (2)
- UINavigationController (1)
- Quartz (3)
- UIColor (1)
- NSNotificationCenter (1)
- NSNumber (1)
- NSError (1)
- NSTimer (1)
- NSURL (1)
- KVO (1)
- UIBarButtonItem (1)
- NSUserDefaults (1)
- 软键盘 (1)
- UITextView (2)
- CLLocationManager (1)
- xCode (2)
- VC (3)
- Private Framework (1)
- xCode调试技巧 (2)
- IOS7 (3)
- cocos2d-x (5)
- 后台运行 (1)
- Chromium (0)
最新评论
-
feishihai：
太 感谢 了！！！其他地方说的都只有一半！！
xcode5 Icon already includes gloss effects doesnot work解决方法 -
hhb19900618：
你这个效果有渐变吗？
UITableView阴影 -
zhaoyubetter：
不对啊。这是遍历 value啊
NSDictionary遍历所有的key和Values -
sunqingquan：
学习啦，加油
NSError code错误列表信息 -
liubiqu：
如果有xib文件需要增加一个language,这样调用选择图片 ...
iphone系统控件里显示中文标题设置
官网地址:
File-system operation attempted on non-existent file Available in Mac OS X v10.4 and later. Declared in Failure to get a lock on file Available in Mac OS X v10.4 and later. Declared in Read error, reason unknown Available in Mac OS X v10.4 and later. Declared in Read error because of a permission problem Available in Mac OS X v10.4 and later. Declared in Read error because of an invalid file name Available in Mac OS X v10.4 and later. Declared in Read error because of a corrupted file, bad format, or similar reason Available in Mac OS X v10.4 and later. Declared in Read error because no such file was found Available in Mac OS X v10.4 and later. Declared in Read error because the string encoding was not applicable. Access the bad encoding from the Available in Mac OS X v10.4 and later. Declared in Read error because the specified URL scheme is unsupported Available in Mac OS X v10.4 and later. Declared in Read error because the specified file was too large. Available in Mac OS X v10.5 and later. Declared in Read error because the string coding of the file could not be determined Available in Mac OS X v10.5 and later. Declared in Write error, reason unknown Available in Mac OS X v10.4 and later. Declared in Write error because of a permission problem Available in Mac OS X v10.4 and later. Declared in Write error because of an invalid file name Available in Mac OS X v10.4 and later. Declared in Write error because the string encoding was not applicable. Access the bad encoding from the Available in Mac OS X v10.4 and later. Declared in Write error because the specified URL scheme is unsupported Available in Mac OS X v10.4 and later. Declared in Write error because of a lack of disk space Available in Mac OS X v10.4 and later. Declared in Write error because because the volume is read only. Available in Mac OS X v10.6 and later. Declared in Key-value coding validation error Available in Mac OS X v10.4 and later. Declared in Formatting error (related to display of data) Available in Mac OS X v10.4 and later. Declared in The user cancelled the operation (for example, by pressing Command-period). This code is for errors that do not require a dialog displayed and might be candidates for special-casing. Available in Mac OS X v10.4 and later. Declared in Marks the start of the range of error codes reserved for file errors Available in Mac OS X v10.4 and later. Declared in Marks the end of the range of error codes reserved for file errors Available in Mac OS X v10.4 and later. Declared in Marks the start of the range of error codes reserved for validation errors. Available in Mac OS X v10.4 and later. Declared in Marks the start and end of the range of error codes reserved for validation errors. Available in Mac OS X v10.4 and later. Declared in Marks the start of the range of error codes reserved for formatting errors. Available in Mac OS X v10.4 and later. Declared in Marks end of the range of error codes reserved for formatting errors. Available in Mac OS X v10.4 and later. Declared in An error was encountered while parsing the property list. Available in Mac OS X v10.6 and later. Declared in The version number of the property list is unable to be determined. Available in Mac OS X v10.6 and later. Declared in An stream error was encountered while reading the property list. Available in Mac OS X v10.6 and later. Declared in An stream error was encountered while writing the property list. Available in Mac OS X v10.6 and later. Declared in Marks beginning of the range of error codes reserved for property list errors. Available in Mac OS X v10.6 and later. Declared in Marks end of the range of error codes reserved for property list errors. Available in Mac OS X v10.6 and later. Declared in Marks beginning of the range of error codes reserved for errors related to executable files. Available in Mac OS X v10.5 and later. Declared in Executable is of a type that is not loadable in the current process. Available in Mac OS X v10.5 and later. Declared in Executable does not provide an architecture compatible with the current process. Available in Mac OS X v10.5 and later. Declared in Executable has Objective C runtime information incompatible with the current process. Available in Mac OS X v10.5 and later. Declared in Executable cannot be loaded for some other reason, such as a problem with a library it depends on. Available in Mac OS X v10.5 and later. Declared in Executable fails due to linking issues. Available in Mac OS X v10.5 and later. Declared in Marks end of the range of error codes reserved for errors related to executable files. Available in Mac OS X v10.5 and later. Declared in The constants in this enumeration are The enumeration constants beginning with These values are returned as the error code property of an Returned when the URL Loading system encounters an error that it cannot interpret. This can occur when an error originates from a lower level framework or library. Whenever this error code is received, it is a bug, and should be reported to Apple. Available in Mac OS X v10.2 and later. Declared in Returned when an asynchronous load is canceled. A Web Kit framework delegate will receive this error when it performs a cancel operation on a loading resource. Note that an Available in Mac OS X v10.2 and later. Declared in Returned when a URL is sufficiently malformed that a URL request cannot be initiated Available in Mac OS X v10.2 and later. Declared in Returned when an asynchronous operation times out. Available in Mac OS X v10.2 and later. Declared in Returned when a properly formed URL cannot be handled by the framework. The most likely cause is that there is no available protocol handler for the URL. Available in Mac OS X v10.2 and later. Declared in Returned when the host name for a URL cannot be resolved. Available in Mac OS X v10.2 and later. Declared in Returned when an attempt to connect to a host has failed. This can occur when a host name resolves, but the host is down or may not be accepting connections on a certain port. Available in Mac OS X v10.2 and later. Declared in Returned when the length of the resource data exceeds the maximum allowed. Available in Mac OS X v10.5 and later. Declared in Returned when a client or server connection is severed in the middle of an in-progress load. Available in Mac OS X v10.2 and later. Declared in See Available in Mac OS X v10.2 and later. Declared in Returned when a redirect loop is detected or when the threshold for number of allowable redirects has been exceeded (currently 16). Available in Mac OS X v10.2 and later. Declared in Returned when a requested resource cannot be retrieved. Examples are “file not found”, and data decoding problems that prevent data from being processed correctly. Available in Mac OS X v10.2 and later. Declared in Returned when a network resource was requested, but an internet connection is not established and cannot be established automatically, either through a lack of connectivity, or by the user's choice not to make a network connection automatically. Available in Mac OS X v10.2 and later. Declared in Returned when a redirect is specified by way of server response code, but the server does not accompany this code with a redirect URL. Available in Mac OS X v10.2 and later. Declared in Returned when the URL Loading system receives bad data from the server. This is equivalent to the “500 Server Error” message sent by HTTP servers. Available in Mac OS X v10.2 and later. Declared in Returned when an asynchronous request for authentication is cancelled by the user. This is typically incurred by clicking a “Cancel” button in a username/password dialog, rather than the user making an attempt to authenticate. Available in Mac OS X v10.2 and later. Declared in Returned when authentication is required to access a resource. Available in Mac OS X v10.2 and later. Declared in Returned when a server reports that a URL has a non-zero content length, but terminates the network connection “gracefully” without sending any data. Available in Mac OS X v10.2 and later. Declared in Returned when content data received during an NSURLConnection request cannot be decoded for a known content encoding. Available in Mac OS X v10.5 and later. Declared in Returned when content data received during an NSURLConnection request has an unknown content encoding. Available in Mac OS X v10.5 and later. Declared in Returned when a response to an NSURLConnection request cannot be parsed. Available in Mac OS X v10.5 and later. Declared in Returned when a file does not exist. Available in Mac OS X v10.2 and later. Declared in Returned when a request for an FTP file results in the server responding that the file is not a plain file, but a directory. Available in Mac OS X v10.2 and later. Declared in Returned when a resource cannot be read due to insufficient permissions. Available in Mac OS X v10.2 and later. Declared in Returned when an attempt to establish a secure connection fails for reasons which cannot be expressed more specifically. Available in Mac OS X v10.2 and later. Declared in Returned when a server certificate has a date which indicates it has expired, or is not yet valid. Available in Mac OS X v10.2 and later. Declared in Returned when a server certificate is signed by a root server which is not trusted. Available in Mac OS X v10.2 and later. Declared in Returned when a server certificate is not signed by any root server. Available in Mac OS X v10.2 and later. Declared in Returned when a server certificate is not yet valid. Available in Mac OS X v10.4 and later. Declared in Returned when a server certificate is rejected. Available in Mac OS X v10.4 and later. Declared in Returned when a client certificate is required to authenticate an SSL connection during an NSURLConnection request. Available in Mac OS X v10.6 and later. Declared in Returned when a specific request to load an item only from the cache cannot be satisfied. This error is sent at the point when the library would go to the network accept for the fact that is has been blocked from doing so by the “load only from cache” directive. Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Returned when Available in Mac OS X v10.2 and later. Declared in Foundation Constants Reference
NSError Codes
NSError codes in the Cocoa error domain.enum {
NSFileNoSuchFileError = 4,
NSFileLockingError = 255,
NSFileReadUnknownError = 256,
NSFileReadNoPermissionError = 257,
NSFileReadInvalidFileNameError = 258,
NSFileReadCorruptFileError = 259,
NSFileReadNoSuchFileError = 260,
NSFileReadInapplicableStringEncodingError = 261,
NSFileReadUnsupportedSchemeError = 262,
NSFileReadTooLargeError = 263,
NSFileReadUnknownStringEncodingError = 264,
NSFileWriteUnknownError = 512,
NSFileWriteNoPermissionError = 513,
NSFileWriteInvalidFileNameError = 514,
NSFileWriteInapplicableStringEncodingError = 517,
NSFileWriteUnsupportedSchemeError = 518,
NSFileWriteOutOfSpaceError = 640,
NSFileWriteVolumeReadOnlyError = 642m
NSKeyValueValidationError = 1024,
NSFormattingError = 2048,
NSUserCancelledError = 3072,
NSFileErrorMinimum = 0,
NSFileErrorMaximum = 1023,
NSValidationErrorMinimum = 1024,
NSValidationErrorMaximum = 2047,
NSFormattingErrorMinimum = 2048,
NSFormattingErrorMaximum = 2559,
NSPropertyListReadCorruptError = 3840,
NSPropertyListReadUnknownVersionError = 3841,
NSPropertyListReadStreamError = 3842,
NSPropertyListWriteStreamError = 3851,
NSPropertyListErrorMinimum = 3840,
NSPropertyListErrorMaximum = 4095
NSExecutableErrorMinimum = 3584,
NSExecutableNotLoadableError = 3584,
NSExecutableArchitectureMismatchError = 3585,
NSExecutableRuntimeMismatchError = 3586,
NSExecutableLoadError = 3587,
NSExecutableLinkError = 3588,
NSExecutableErrorMaximum = 3839,
}
Constants
NSFileNoSuchFileErrorFoundationErrors.h.NSFileLockingErrorFoundationErrors.h.NSFileReadUnknownErrorFoundationErrors.h.NSFileReadNoPermissionErrorFoundationErrors.h.NSFileReadInvalidFileNameErrorFoundationErrors.h.NSFileReadCorruptFileErrorFoundationErrors.h.NSFileReadNoSuchFileErrorFoundationErrors.h.NSFileReadInapplicableStringEncodingErroruserInfo dictionary using the NSStringEncodingErrorKey key.FoundationErrors.h.NSFileReadUnsupportedSchemeErrorFoundationErrors.h.NSFileReadTooLargeErrorFoundationErrors.h.NSFileReadUnknownStringEncodingErrorFoundationErrors.h.NSFileWriteUnknownErrorFoundationErrors.h.NSFileWriteNoPermissionErrorFoundationErrors.h.NSFileWriteInvalidFileNameErrorFoundationErrors.h.NSFileWriteInapplicableStringEncodingErroruserInfo dictionary using the NSStringEncodingErrorKey key.FoundationErrors.h.NSFileWriteUnsupportedSchemeErrorFoundationErrors.h.NSFileWriteOutOfSpaceErrorFoundationErrors.h.NSFileWriteVolumeReadOnlyErrorFoundationErrors.h.NSKeyValueValidationErrorFoundationErrors.h.NSFormattingErrorFoundationErrors.h.NSUserCancelledErrorFoundationErrors.h.NSFileErrorMinimumFoundationErrors.h.NSFileErrorMaximumFoundationErrors.h.NSValidationErrorMinimumFoundationErrors.h.NSValidationErrorMaximumFoundationErrors.h.NSFormattingErrorMinimumFoundationErrors.h.NSFormattingErrorMaximumFoundationErrors.h.NSPropertyListReadCorruptErrorFoundationErrors.h.NSPropertyListReadUnknownVersionErrorFoundationErrors.h.NSPropertyListReadStreamErrorFoundationErrors.h.NSPropertyListWriteStreamErrorFoundationErrors.h.NSPropertyListErrorMinimumFoundationErrors.h.NSPropertyListErrorMaximumFoundationErrors.h.NSExecutableErrorMinimumFoundationErrors.h.NSExecutableNotLoadableErrorFoundationErrors.h.NSExecutableArchitectureMismatchErrorFoundationErrors.h.NSExecutableRuntimeMismatchErrorFoundationErrors.h.NSExecutableLoadErrorFoundationErrors.h.NSExecutableLinkErrorFoundationErrors.h.NSExecutableErrorMaximumFoundationErrors.h.Discussion
NSError code numbers in the Cocoa error domain (NSCocoaErrorDomain). Other frameworks, most notably the Application Kit, provide their own NSCocoaErrorDomain error codes.NSFile indicate file-system errors or errors related to file I/O operations. Use the key NSFilePathErrorKey or the NSURLErrorKey (whichever is appropriate) to access the file-system path or URL in the userInfo dictionary of the NSError object.Declared In
FoundationErrors.h
URL Loading System Error Codes
NSError object with the domain “NSURLErrorDomain”.typedef enum
{
NSURLErrorUnknown = -1,
NSURLErrorCancelled = -999,
NSURLErrorBadURL = -1000,
NSURLErrorTimedOut = -1001,
NSURLErrorUnsupportedURL = -1002,
NSURLErrorCannotFindHost = -1003,
NSURLErrorCannotConnectToHost = -1004,
NSURLErrorDataLengthExceedsMaximum = -1103,
NSURLErrorNetworkConnectionLost = -1005,
NSURLErrorDNSLookupFailed = -1006,
NSURLErrorHTTPTooManyRedirects = -1007,
NSURLErrorResourceUnavailable = -1008,
NSURLErrorNotConnectedToInternet = -1009,
NSURLErrorRedirectToNonExistentLocation = -1010,
NSURLErrorBadServerResponse = -1011,
NSURLErrorUserCancelledAuthentication = -1012,
NSURLErrorUserAuthenticationRequired = -1013,
NSURLErrorZeroByteResource = -1014,
NSURLErrorCannotDecodeRawData = -1015,
NSURLErrorCannotDecodeContentData = -1016,
NSURLErrorCannotParseResponse = -1017,
NSURLErrorFileDoesNotExist = -1100,
NSURLErrorFileIsDirectory = -1101,
NSURLErrorNoPermissionsToReadFile = -1102,
NSURLErrorSecureConnectionFailed = -1200,
NSURLErrorServerCertificateHasBadDate = -1201,
NSURLErrorServerCertificateUntrusted = -1202,
NSURLErrorServerCertificateHasUnknownRoot = -1203,
NSURLErrorServerCertificateNotYetValid = -1204,
NSURLErrorClientCertificateRejected = -1205,
NSURLErrorClientCertificateRequired = -1206,
NSURLErrorCannotLoadFromNetwork = -2000,
NSURLErrorCannotCreateFile = -3000,
NSURLErrorCannotOpenFile = -3001,
NSURLErrorCannotCloseFile = -3002,
NSURLErrorCannotWriteToFile = -3003,
NSURLErrorCannotRemoveFile = -3004,
NSURLErrorCannotMoveFile = -3005,
NSURLErrorDownloadDecodingFailedMidStream = -3006,
NSURLErrorDownloadDecodingFailedToComplete = -3007
}
Constants
NSURLErrorUnknownNSURLError.h.NSURLErrorCancelledNSURLConnection or NSURLDownload delegate will not receive this error if the download is canceled.NSURLError.h.NSURLErrorBadURLNSURLError.h.NSURLErrorTimedOutNSURLConnection will send this error to its delegate when the timeoutInterval in NSURLRequest expires before a load can complete.NSURLError.h.NSURLErrorUnsupportedURLNSURLError.h.NSURLErrorCannotFindHostNSURLError.h.NSURLErrorCannotConnectToHostNSURLError.h.NSURLErrorDataLengthExceedsMaximumNSURLError.h.NSURLErrorNetworkConnectionLostNSURLError.h.NSURLErrorDNSLookupFailedNSURLErrorCannotFindHostNSURLError.h.NSURLErrorHTTPTooManyRedirectsNSURLError.h.NSURLErrorResourceUnavailableNSURLError.h.NSURLErrorNotConnectedToInternetNSURLError.h.NSURLErrorRedirectToNonExistentLocationNSURLError.h.NSURLErrorBadServerResponseNSURLError.h.NSURLErrorUserCancelledAuthenticationNSURLError.h.NSURLErrorUserAuthenticationRequiredNSURLError.h.NSURLErrorZeroByteResourceNSURLError.h.NSURLErrorCannotDecodeRawDataNSURLError.h.NSURLErrorCannotDecodeContentDataNSURLError.h.NSURLErrorCannotParseResponseNSURLError.h.NSURLErrorFileDoesNotExistNSURLError.h.NSURLErrorFileIsDirectoryNSURLError.h.NSURLErrorNoPermissionsToReadFileNSURLError.h.NSURLErrorSecureConnectionFailedNSURLError.h.NSURLErrorServerCertificateHasBadDateNSURLError.h.NSURLErrorServerCertificateUntrustedNSURLError.h.NSURLErrorServerCertificateHasUnknownRootNSURLError.h.NSURLErrorServerCertificateNotYetValidNSURLError.h.NSURLErrorClientCertificateRejectedNSURLError.h.NSURLErrorClientCertificateRequiredNSURLError.h.NSURLErrorCannotLoadFromNetworkNSURLError.h.NSURLErrorCannotCreateFileNSURLDownload object was unable to create the downloaded file on disk due to a I/O failure.NSURLError.h.NSURLErrorCannotOpenFileNSURLDownload was unable to open the downloaded file on disk.NSURLError.h.NSURLErrorCannotCloseFileNSURLDownload was unable to close the downloaded file on disk.NSURLError.h.NSURLErrorCannotWriteToFileNSURLDownload was unable to write to the downloaded file on disk.NSURLError.h.NSURLErrorCannotRemoveFileNSURLDownload was unable to remove a downloaded file from disk.NSURLError.h.NSURLErrorCannotMoveFileNSURLDownload was unable to move a downloaded file on disk.NSURLError.h.NSURLErrorDownloadDecodingFailedMidStreamNSURLDownload failed to decode an encoded file during the download.NSURLError.h.NSURLErrorDownloadDecodingFailedToCompleteNSURLDownload failed to decode an encoded file after downloading.NSURLError.h.Availability
Declared In
NSURLError.h
发表评论
相关推荐
虽然Objective-C提供了`@try`、`@catch`、`@throw`等异常处理机制，但在iOS开发中，通常建议使用错误对象（NSError）来传递错误信息，而不是抛出异常，以保持程序的稳定性和性能。 5. **Auto Layout约束冲突（Auto...
总之，当遇到HTTP状态码500时，首先检查客户端的请求设置，特别是`Content-Type`，然后与后端团队密切合作，通过日志、调试工具和错误信息来定位问题。同时，确保发送的数据格式正确，并考虑所有可能影响请求的环境...
如果连接失败，error参数将包含错误信息。 4. 错误码的处理 error.code有多种可能的值，例如13表示已连接，7表示用户取消连接等。在错误处理中，需要根据不同的错误码进行相应的处理。 5. Simulator的注意事项 ...
本文将深入探讨一个特定的错误：“Error Domain=NSCocoaErrorDomain Code=3840”，以及如何解决这个问题。 错误描述：“Error Domain=NSCocoaErrorDomain Code=3840 'The operation couldn’t be completed. (Cocoa...
根据状态码，我们可以判断是否发生了404或504错误，并采取相应措施，如显示自定义错误页面或提示信息。 总结来说，解决iOS UIWebView中404、504错误的关键在于监听网络请求的状态并处理返回的HTTP状态码。通过适当...
6. 错误处理：当网络请求失败时，AFNworking会通过错误对象提供详细的错误信息，帮助开发者定位问题。 ```objective-c NSString *errorDescription = error.localizedDescription; NSInteger errorCode = error.code...
- 错误处理通常在`failure:` block中进行，AFHTTPRequestOperation会将服务器返回的错误信息封装成NSError对象。 9. **异步编程**： - 所有的网络请求都是异步的，使用block回调来处理请求结果，这有助于保持UI的...
guard let jsonData = data else { throw NSError(domain: "", code: 0, userInfo: nil) } return try JSONSerialization.jsonObject(with: jsonData, options: []) } .catch { error in // 处理错误 print(...
ShowMessageFmt('发生错误: %d', [Error.Code]); end; end else // 验证失败，未知错误 ShowMessage('验证失败，未知错误'); end; end); end; ``` 在`evaluatePolicy`的回调中，我们根据返回的错误代码判断...
同时也要关注`ZBarReaderDelegate`中的错误处理方法，如`- (void)imagePickerController:(UIImagePickerController *)controller didFailWithError:(NSError *)error`，以便捕获并处理可能出现的扫描错误。...
5. 错误处理：FMDB 使用 `NSError` 对象处理错误，通过 `-hadError` 方法检查是否出错，`-lastErrorMessage` 获取错误信息，`-lastErrorCode` 获取错误代码。 6.事务处理：FMDB 支持事务，通过 `-beginTransaction`...
例如，你可以使用`+ (void)reverseGeocodeLocation:(CLLocation *)location completionHandler:(void(^)(NSArray *placemarks, NSError *error))completionHandler`方法来获取给定位置的地址信息。这个方法接受一个`...
var error: NSError? if context.canEvaluatePolicy(.deviceOwnerAuthenticationWithBiometrics, error: &error) { // 设备支持并已设置TouchID/FaceID } else { // 设备不支持或未设置TouchID/FaceID } ``` 接...
error = [NSError errorWithDomain:@"MockDataError" code:100 userInfo:nil]; completion(nil, error); } }); } ``` 在这个示例中，`fetchDataWithCompletionBlock:`方法接受一个Block作为参数，这个Block会在...
- (void)URLSession:(NSURLSession *)session task:(NSURLSessionTask *)task didCompleteWithError:(NSError *)error { // 处理请求完成或错误 } @end ``` 在实际项目中，为了提高用户体验，你还可以添加加载...
// 打印错误信息 print("Touch ID不能使用！错误原因：\(error?.localizedDescription ?? "未知错误")") } } } ``` 在这个示例中，`canEvaluatePolicy(_:error:)`方法用于检查设备是否可以执行指纹验证。`....
LBXScan库提供了错误处理机制，开发者可以通过代理方法`- (void)lbxScanView:(LBXScanView *)scanView error:(NSError *)error;`处理这些错误。 7. **性能优化**： - LBXScan库内部使用了GPU加速的二维码检测算法...
throw NSError(domain: "InvalidData", code: 1, userInfo: [NSLocalizedDescriptionKey: "Name is required"]) } if name.isEmpty { throw NSError(domain: "InvalidData", code: 2, userInfo: ...