Your comments

I managed to reproduce this problem and reported it to the developers.

You have 2 certificates in your keychain with the same name. So AppFactory doesn't know which one to choose.

Check on Apple developer and delete the one that you don't need.

Peter, the product linking you single document app to its issue isn't free. That is why i get this when I test your app on my simulator :

The single document app can't make in-app purchases so it asks to register the device as test to bypass the purchasse process. This happens on the simulator but I think that on a real device the download would just fail.

Could you tell us when this problem happens ?

A screen shot of the error would also be helpful.

The rejection because of incompatibility with IPv6 is often used by Apple's reviewers. We test our apps on IPv6 wifi networks and we where never able to reproduce the problem. So here is a message you can send them in response to this kind of rejection :

Here is a simple description of our test procedure.

#1 Our tests consist in putting us in the exact conditions described in Supporting IPv6 DNS64/NAT64 Networks
- We produce and app signed with an adHoc distribution profile.
- We perform a clean install (from scratch) on a device connected to the local network (NAT64).

> our apps launch correctly. We can do in-app purchases using the sandbox, download the purchased content and read.

#2 We could not reproduce the errors reported by the Apple Review team.

#3 We read thoroughly the Technical Q&A QA1764 but could not find any help in it as we seem to stick to every guideline.

#4 We found this post [] on your forum mentioning a discrepancy between the test protocol accessible to developers and largely described above, and the real tests run by the AppReview team. Unfortunately, we cannot put ourselves in the conditions of the AppReview team as we don’t know them. This article also describes some server side configurations that could lead to errors. We checked them all and we are on the safe side.

#5 Other apps using the same binary but accessing other content have been submitted and accepted.


We assigned a 2 months single doc app license to your app on Cloud Connect to allow you to update your app.


The bug was fixed in AppFactory iOS 4.7. So if you update app it should open without an internet connection.