Exceptions and Errors on iOS
异常:程序缺陷导致;不可恢复;给开发者使用;
错误:资源受限导致;可恢复;提示给用户。
https://blog.jayway.com/2010/10/13/exceptions-and-errors-on-ios/
Cocoa, and by inheritance Cocoa Touch on iOS makes a clear distinction between what is an exception, and what is an error in your application. This should be obvious since NSException
and NSError
both inherit from the NSObject
root class with no relations at all.
Programmer vs. User
Exceptions are intended for signaling programming errors and fatal errors that the application can never recover from. One such error is index out of bounds when accessing an array. There is little reason to catch any exception; if you for example could not calculate a legal array index the first time around your app is in an illegal state. Exceptions are for your own use as a developer, to catch all programming errors in testing before shipping to the end user. Only secondary to inform the user of fatal errors when possible.
Errors are intended for signaling user errors, and conditions that can not be predicted until the end user runs your application. One such error is network timeout. There are many reasons to catch these errors; e.g. the user could be asked to check the network connectivity, and try again. Errors should always be handled, and be properly presented to the user. A user is much more forgiving if your application fails with a clear reason, than if it simply crashes or refuses to work.
Signal and Handle Exceptions
Exceptions are thown in Objective-C, just as in most other programming languages. You can construct your NSException
object manually, and throw it using the @throw
compiler directive if you like. But the preferred way is to use the NSException
convenience class methods.
1
2
|
[NSException raise:NSInvalidArgumentException
format:@"Foo must not be nil"];
|
Here we see the first divergence from how for example Java and C# handles exceptions. In Objective-C different exceptions are not normally signaled by different subclasses, but instead the exception is given a name, in the form of a constant string. Exceptions are however handled quite traditionally.
1
2
3
4
5
6
7
8
9
|
@try {
// Normal code flow, with potential exceptions
}
@catch (NSException* e) {
// Handle exception or re-throw
}
@finally {
// Mandatory cleanup
}
|
Signal and Handle Errors
Errors do not use any special feature of the Objective-C run-time or programming language. Errors are instead treated as normal method arguments.
For synchronous tasks the error is returned as the last out argument of the method. A typical synchronous method signature with error handling looks like this:
1
2
|
- (id)initWithContentsOfURL:(NSURL *)url
error:(NSError **)outError
|
The client of such a task can always pass NULL
to explicitly ignore the details of the error, the method must therefor also signal the error by the return value. This is typically done by returning nil
, or NO
if no other return value should exist. Ignoring the error is never recommended.
For asynchronous tasks the error is returned as the last argument of a delegate method. A typical asynchronous method signature with error handling looks like this:
1
2
|
- (void)connection:(NSURLConnection *)connection
didFailWithError:(NSError *)error
|
The client of such a task can never opt out of receiving the error. It is still never recommended to ignore the error.
The information in an NSError
is always localized and phrased in end-user friendly words. This is something you can trust of errors from system frameworks, and a hard requirement on you when you create your own errors. Therefor handling the error is never a burden, in the simplest case you can simply display the localized error message to the end user and call it a day.
1
2
3
4
5
6
7
8
9
|
- (void)connection:(NSURLConnection *)connection
didFailWithError:(NSError *)error
{
[[[[UIAlertView alloc] initWithTitle:[error localizedDescription]
message:[error localizedFailureReason]
delegate:nil
cancelButtonTitle:NSLocalizedString(@"OK", nil)
otherButtonTitles:nil] autorelease] show];
}
|
There is more to NSError
Cocoa and Cocoa Touch have much in common. Classes not brought straight over from Mac OS X to iOS often have a sibling anyway. One such class is NSAlert
from Mac OS X and it’s sibling UIAlertView
on iOS. They serve the same purpose of displaying an alert message to the end user, optionally with a few choices in the form of buttons.
One convenience method for handling errors on Mac OS X is -[NSAlert alertWithError:]
, it did not survive the transformation to UIAlertView
on iOS. It is a pity, since it is a convenient way to quickly setup an alert with all the localized and human readable information. Basically turning the example code for handling an asynchronous error above from five lines of code, into a single line of code.
But that is not all. NSAlert
and NSError
on Mac OS X also have standardize facilities for handling recovery options. For example adding a “Retry” button to the alert, and calling the correct methods in response to this user selection.
On iOS NSError
still have all the facilities to handle error recoveries, it is only UIAlertView
that is lacking the final user facing bits. Fortunately this is easy to add. NSError
manages error recovery with information held in it’s userInfo dictionary. The following keys are used:
NSLocalizedRecoverySuggestionErrorKey
– A localized text with a general suggestion for how to recover from the error, for example “Check the network connection”.NSLocalizedRecoveryOptionsErrorKey
– An array of localized button titles such as “Retry”.NSRecoveryAttempterErrorKey
– An object conforming to the informal protocolNSErrorRecoveryAttempting
.
The informal protocol NSErrorRecoveryAttempting
declares one method that is significant for iOS:
1
2
|
- (BOOL)attemptRecoveryFromError:(NSError *)error
optionIndex:(NSUInteger)recoveryOptionIndex
|
The recoveryOptionIndex
is the index into the array of button titles, and is the actual choice the user made for recovering from the error.
Adding a -[UIAlertView alertWithError:]
convenience method to UIAlertView is made really easy since Objective-C has categories, and classes themselves are object instances so we can use the UIAlertView
class as alert delegate for error recovery alerts.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
@implementation UIAlertView (CWErrorHandler)
static NSMutableDictionary* cw_recoveryErrors = nil;
+(void)alertViewCancel:(UIAlertView *)alertView;
{
NSValue* key = [NSValue valueWithPointer:(const void *)alertView];
[cw_recoveryErrors removeObjectForKey:key];
}
+ (void)alertView:(UIAlertView *)alertView
clickedButtonAtIndex:(NSInteger)buttonIndex;
{
NSValue* key = [NSValue valueWithPointer:(const void *)alertView];
NSError* error = [cw_recoveryErrors objectForKey:key];
NSString* buttonTitle = [alertView buttonTitleAtIndex:buttonIndex];
NSInteger recoveryIndex = [[error localizedRecoveryOptions]
indexOfObject:buttonTitle];
if (recoveryIndex != NSNotFound) {
[[error recoveryAttempter]
attemptRecoveryFromError:error
optionIndex:recoveryIndex];
}
[cw_recoveryErrors removeObjectForKey:key];
}
+(UIAlertView*)alertViewWithError:(NSError*)error;
{
UIAlertView* alert = [UIAlertView alloc];
[[alert initWithTitle:[error localizedDescription]
message:[error localizedFailureReason]
delegate:nil
cancelButtonTitle:NSLocalizedString(@"Cancel", nil)
otherButtonTitles:nil] autorelease];
if ([error recoveryAttempter]) {
if (cw_recoveryErrors == nil) {
cw_recoveryErrors = [[NSMutableDictionary alloc]
initWithCapacity:4];
}
NSValue* key = [NSValue valueWithPointer:(const void *)alertView];
[cw_recoveryErrors setObject:error
forKey:key];
for (id recoveryOption in [error localizedRecoveryOptions]) {
[alert addButtonWithTitle:recoveryOption];
}
alert.delegate = (id)self;
}
return alert;
}
@end
|
Conclusion
The clean separation of exceptions and errors help you as a developer to catch programming errors during development and with unit tests, and also handle errors of interest to the end users in a standardized and uniform way. The very nature of NSError
encourages developers to write descriptive error messages that end users can understand and make informed discussions about. Errors are unavoidable in any application of non-neglectable complexity, gracefully handling these errors gives an aura of quality and ensures happy users. Happy users means better sales.
Full source code to the examples in this post, including some more convenience methods can be downloaded here, and are released under the Apache 2 open source license.
Exceptions and Errors on iOS的更多相关文章
- Exceptions & Errors - 异常与错误
来源于 Ry’s Objective-C Tutorial - RyPress 一个学习Objective-C基础知识的网站. 个人觉得很棒,所以决定抽时间把章节翻译一下. 本人的英语水平有限,有让大 ...
- ruby Errors & Exceptions
When you first started coding, errors were probably the last thing you wanted to see. After all, it’ ...
- Python Tutorial 学习(八)--Errors and Exceptions
Python Tutorial 学习(八)--Errors and Exceptions恢复 Errors and Exceptions 错误与异常 此前,我们还没有开始着眼于错误信息.不过如果你是一 ...
- Handling Errors and Exceptions
http://delphi.about.com/od/objectpascalide/a/errorexception.htm Unfortunately, building applications ...
- 笔记-python-tutorial-8.errors and exceptions
笔记-python-tutorial-8.errors and exceptions 1. errors and exceptions 1.1. syntax errors >& ...
- 使用ab对nginx进行压力测试
nginx以高并发,省内存著称. 相信大多数安装nginx的同学都想知道自己的nginx性能如何. 我想跟大家分享下我使用ab工具的压力测试方法和结果, ab是针对apache的性能测试工具,可以只安 ...
- Java Servlet规范
截自网址:http://blog.csdn.net/u010391029/article/details/46521051 JavaServlet Specification Version 2.3 ...
- CI框架使用PHPmail插件发送QQ邮件:
有助请顶,不好请评.0:33 2016/3/12CI框架使用PHPmail插件发送QQ邮件:发送成功,不过修改了主机参数,还包含了一个phpmail中的一个另外的文件,详见下方:参见:http://c ...
- 关于搭建一个高性能网站的服务器的架设思路以及nginx测试的并发
对于高性能网站的架设,主要就是请求量大,那我们该如何进行支撑? 考虑到下面的几个方面: 1.要减少请求,那对于开发人员来说,网站的css文件进行合并,背景图片也要合并,一般都是请求一张比较大的图片,然 ...
随机推荐
- ZOJ - 3777(状压dp)
The 11th Zhejiang Provincial Collegiate Programming Contest is coming! As a problem setter, Edward i ...
- cf779D(记忆化dp)
题目链接: http://codeforces.com/problemset/problem/799/D 题意: 给出两个矩阵边长 a, b, 和 w, h, 以及一个 c 数组, 可选择 c 数组中 ...
- 关于特殊目录如com null无法删除的处理办法
1.把以下批处理做成一个del.bat放在桌面 del /f /a /q \\?\%1 rd /s /q \\?\%1 2.需要删除的文件或者文件夹拉到这个文件上就可以了 可以删除没有属性项目中没有安 ...
- Hibernate的优化方案
使用参数绑定 使用绑定参数的原因是让数据库一次解析SQL,对后续的重复请求可以使用生成好的执行计划,这样做节省CPU时间和内存. 避免SQL注入. 尽量少使用NOT 如果where子句中包含not关键 ...
- centos7.2上安装python3和pip19.0.3
安装libressl 下载地址: https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.7.4.tar.gz 或者 :https://pan. ...
- Mysql常见问题集锦
缺少libstdc++.so.6库的原因及解决办法 https://blog.csdn.net/u010417185/article/details/69951312 https://www.cnbl ...
- ubuntu 的 python从2.* 升级到3.*
1.在ubuntu 的终端中用代码下载最新的Python sudo apt-get install python3 2.用命令删除usr/bin/目录下的默认python link文件root@sal ...
- Django 01 django基本介绍及环境搭建
Django 01 django基本介绍及环境搭建 #http服务器 #用来接收用户请求,并将请求转发给web应用框架进行处理 #Web应用框架 #处理完请求后在发送给http服务器,http服务器在 ...
- hdu3949(线性基,求第k小的异或和
题目链接:http://acm.hdu.edu.cn/showproblem.php?pid=3949 XOR Time Limit: 2000/1000 MS (Java/Others) Me ...
- c语言字符串操作总结(转)
本文转自:http://www.jb51.net/article/37410.htm 1)字符串操作 strcpy(p, p1) 复制字符串 strncpy(p, p1, n) 复制指定长度字符串 s ...