Iphone iOS 5.0下的Aviary SDK问题-objectAtIndexedSubscript

我已经下载了最新的鸟舍代码2.6.0，并将其整合到运行iOS 5.0的iPhone 4S的Xcode 4.2中。每次我启动鸟舍行动，我都会在下面看到ObjectaIndexedSubscript的追踪显示

我看到了这篇文章“”，在iOS 5.0中没有ObjectaIndexedSubscript。在鸟类文献中，它说iOS 5.0是受支持的。我错过了什么

这是我的问题。是否有人尝试将iOS 5.0的最新鸟类代码版本2.6.0整合到一起？如果不是，iOS 5.0的Aviary SDK版本是什么？在哪里可以下载旧版本的Aviary SDK。我只是还没有准备好升级到iOS 6.0。我正试图将此错误报告给Aviary支持部门，但我感觉他们会告诉我升级到iOS 6.0

从鸟舍网站：

运行时要求SDK支持的最低iOS版本为 iOS 5.0。选择此选项的主要原因是我们使用ARC （自动参考计数）以及我们对一些苹果产品的依赖 需要iOS 5的框架和库。”

添加这个家伙类别（从github链接获取），它将完美地工作

---

只需更新到最新的Xcode。在一些旧版本的Xcode中，

objectAtIndexedSubscript:

未在SDK中实现

- (void) launchPhotoEditorWithImage:(UIImage *)editingResImage highResolutionImage:(UIImage *)highResImage
{    

    NSLog(@"launchPhotoEditorWithImage ...");

    // Initialize the photo editor and set its delegate
    AFPhotoEditorController * photoEditor = [[AFPhotoEditorController alloc] initWithImage:editingResImage];
    [photoEditor setDelegate:self];

    NSLog(@"Present photo editor ...");

    // Present the photo editor.
    [self presentViewController:photoEditor animated:YES completion:nil];
}

2013-03-31 19:32:14.953 Photo Editor[348:707] launchPhotoEditorWithImage ...
2013-03-31 19:32:15.421 Photo Editor[348:707] Present photo editor ...
2013-03-31 19:32:15.421 Photo Editor[348:3f03] -[__NSArrayM objectAtIndexedSubscript:]: unrecognized selector sent to instance 0x4ac5f0
2013-03-31 19:32:15.432 Photo Editor[348:3f03] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSArrayM objectAtIndexedSubscript:]: unrecognized selector sent to instance 0x4ac5f0'
*** First throw call stack:
(0x36fbe8bf 0x3232e1e5 0x36fc1acb 0x36fc0945 0x36f1b680 0xb1a45 0x32933d55 0x32935dc7 0x32935c5d 0x32936867 0x37f5c1cf 0x37f5c0a4)
terminate called throwing an exception[Switching to process 9987 thread 0x2703]
[Switching to process 9987 thread 0x2703]
warning: Attempting to create USE_BLOCK_IN_FRAME variable with block that isn't in the frame.
kill
Current language:  auto; currently objective-c
quit
Program ended with exit code: 0