在Apple审核期间,App Purchase无法正常工作
我有一个使用In App购买的应用程序,它已被Apple批准,现在已经在Appstore中。几天前,我提交了一个新版本的应用程序,购买了一个新的耗材,实现了其他的。
I have an app with working In App purchases, it was approved by Apple and it is now in Appstore. A few days ago I submitted a new version of the app with one new consumable purchase, implemented as others were.
我正在使用MKStoreKit和这种方法来购买一个功能:
I'm using MKStoreKit and this method to buy a feature:
// ... showing loading window
[[MKStoreManager sharedManager] buyFeature:feature
onComplete:^(NSString* purchasedFeature,NSData* purchasedReceipt, NSArray* availableDownloads) {
// ... some handler and close loading
onCancelled:^ {
// ... another handler and close loading
}];
在Sandbox模式下,此方法以onComplete块结束,或者取消onCancelled块,获取所有正确的标识符(带有新购买)。但是,由于Apple的评论员的回答,我的装载从未关闭。此外,他们说新购买现在处于开发者行动所需状态,但现在无法编辑,我无法删除它(即使我检查清除否则)。
In Sandbox mode this method ends either in onComplete block, either onCancelled block, getting all correct identifiers (with new purchase too). However, due to Apple's reviewer's answer my loading is never closed. Also, they say that new purchase is now in Developer Action Needed Status, but can not edit it now, and I can not delete it (even if I check Cleared For Sale for NO).
可能问题出现在新购买的产品中还是其他什么?我完全糊涂了......
May the problem be in the new purchase product or is it something else? I'm totally confused...
我该怎么办?有人遇到过这样的问题吗?我无法在Sandbox中重现错误,因为它工作正常,所以有什么方法可以得到与Apple Review Team相同的结果吗?
What can I do? Anyone encountered such a problem? I can not reproduce the error in Sandbox since it is working fine, so is there any way I can get the same result as in the Apple Review Team?
这是由这个新的In App引起的Apple服务器上的一个奇怪的错误。我不知道为什么,但我无法删除它。此外,它打破了所有In Apps,但只有在Apple Review测试时,正如我所说,在沙盒模式下一切都很好。解决方案是写给Apple的支持,过了一段时间他们修复了它,我删除了这个In App,一切都开始工作了。
that was a strange bug on Apple servers caused by this new In App. I don't know why, but I could not delete it. Also, it had broken all In Apps but only while Apple Review testing, as I've said, all was fine in Sandbox mode. The solution was to write to Apple's support, and after a while they fixed it, I deleted this In App and everything started to work as is should.