I send to the apple review my App, and they reply to me this “Please run your app on a device while connected to an IPv6 network (all apps must support IPv6) to identify any issues, then revise and resubmit your app for review.”
I don’t know how fix the problem.
This is a generic message Apple sends out when your app fails for any reason. They turn off IPv4 networking, run your app, if it dies/gives them a black screen, they assume you’re making IPv4 calls. I wish Apple would automatically provide you a console log run of the test device. Since iOS 10 has come around, the logs are polluted with other messages making your messages hard to find and follow.
That said, you can always ask them provide you with a console log from their test run and that might help you narrow down the problem.
What all real iOS devices did you test on?
Did you test using their testFlight system or just developer/adHoc builds?
Rob
I too got an app rejected because the InApp-Purchase is not working with iPv6.
Here is the info I got:
Purchasing is not working running iOS 10.2.1 on Wi-Fi connected to an IPv6 network.
Apps must support IPv6.
I tested the purchasing (not with 10.2.1 yet) and it is working fine. I can’t test this with IPv6 because I don’t know how.
Are there any known issues regarding the new iOS and the IPv6 network?
I’m unaware of any IPv6 issues that we have. Apple tends to blame anything not working on using IPv4 networking (like connecting to an IP address in the format of: xxx.xxx.xxx.xxx) even when frequently its some other error causing the problem. If you have any print statements around your purchasing code and in your transaction call back function you can ask them for a console log of the run that had the error and you might be able to learn something for that.
Rob
I am also experiencing the same issue. I have read a post from this forum dated back in August 2016 that this is sometimes related to having asset file with underscore in the file name, is this still true?
I do have many asset files in my app with underscore in the file name.
@schwab, many times, Apple will try to run the app and it will crash. Apple will give you a message about making sure you test on an IPv6 network since they require everything to work on IPv6 in addition to IPv4. They assume any crash is most likely due to networking which isn’t true.
Many times iOS versions are under tested and legit bugs happen when doing a first time install on a device. It’s always good to ask Apple’s testers to send you a console log of your dump so you can look for errors and find the specific cause of your rejection.
Underscores in file names should be just fine. They are valid Unix filename characters.
Rob
@Rob,
The Apple review team has attached a crash log which doesn’t seems to show specific error or I simply don’t know how to read it.
Exception Type: EXC\_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC\_CORPSE\_NOTIFY Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d Triggered by Thread: 0
Would you know what the Namespace SPRINGBOARD mean?
Springboard is the name of the home screen app where you tap your icons to launch other apps.
Thanks Rob,
So would you have any idea why the app crash during the test? There is no error in the Corona simulator. Would you recommend I try with another Corona build?
The best thing you can do is download and install the app yourself on a real iOS device from TestFlight Apple’s testing service. You can also use Corona to build and install on the device for you. That way it will capture log information to Corona’s console log from the device which can help considerably for tracking down device oriented bugs.
Rob
Thank you for the advice Rob,
I have tried to build and copy to device but the Corona’s log seems to be stuck on Device Logs Starts and when I tried to launch on the actual device, it just stuck on the Default screen. I have even tried to create a new simple main.lua to see if it runs but it doesn’t seem to proceed. Would you know why?
What version of Corona are you using?
I’m using the latest daily build v2017.3055
@Rob, I figured out that it has something to do with composer. My project used to run on director.lua for scene transition and it worked using director but when I switch to composer for scene management, it stops working. Does the latest composer comes with the corona sdk download?
You might want to try maybe 3054. There is something weird going on with iOS caching things (usually if you’re using the same bundle ID/provisioning profile for multiple apps) where the log information doesn’t show up. You can look through Xcode but Apple has polluted their log so much it’s really hard to use.
Composer is part of Corona but if you’re having problems there, they should show up in the simulator. Usually when it doesn’t work on device but runs in the simulator you have a case sensitivity issue. We should issue warnings in our console log if we detect that though.
Rob
My problem wasn’t connected to the IPv6 at all (see above). I tested the purchase again and it worked… so I told the app review team about it and they tested again and the app was accepted.
Thank you. The new build 2017.2056 works with composer now. Thanks!
I submitted a new build using 2017.3056 to Apple for review but they came back with the same error. Everything works fine in Corona simulator and even on my iphone for testing. They said the binary crashed right away. I wonder why…
I have been getting rejected again by Apple even though the app deployed and run without error on simulator and actual device. Some of the errors from the log look like this:
21 UIKit 0x00000001986e16a4 0x198660000 + 530084 22 UIKit 0x00000001988f1a98 0x198660000 + 2693784 23 UIKit 0x00000001988f7808 0x198660000 + 2717704 24 UIKit 0x000000019890c104 0x198660000 + 2801924 25 UIKit 0x00000001988f47ec 0x198660000 + 2705388 26 FrontBoardServices 0x000000019439792c 0x19435d000 + 239916 27 FrontBoardServices 0x0000000194397798 0x19435d000 + 239512 28 FrontBoardServices 0x0000000194397b40 0x19435d000 + 240448 29 CoreFoundation 0x000000019276eb5c 0x192691000 + 908124 30 CoreFoundation 0x000000019276e4a4 0x192691000 + 906404 31 CoreFoundation 0x000000019276c0a4 0x192691000 + 897188 32 CoreFoundation 0x000000019269a2b8 0x192691000 + 37560 33 UIKit 0x00000001986da7b0 0x198660000 + 501680 34 UIKit 0x00000001986d5534 0x198660000 + 4805
Would you guys know how to read this?
I think we need to see more of the error message. There isn’t enough in that snippet to know what’s happening.
Rob