Are you saying Apple is rejecting you because you’re not using IPv6? If so that may not be the reason. That is a pre-recorded message that everyone gets when your app crashes. Ask them for a console log of the run to see if you’re getting a run time error.
Rob
Sorry for the delay Rob, at the beginning of my app charge a 55mb audio, there the app does not respond in 8 or 10 seconds. And apple assumes that it is for connectivity, but I think it’s actually because of the audio load.
There is another way of loading it that does not weigh so much.
If you have a large audio file, consider using audio.loadStream() instead of audio.loadSound(). They do the same thing except that .loadSounds() blocks until it completes. .loadStream() loads in the background and returns as soon as it has enough of the file to begin playing the sound.
The other thing you can do is start some type of loading progress bar/busy wait spinner.
Rob
I found this thread after 4 app rejections now from Apple citing the IPV6 app rejection notice. We have tested our app extensively including the IAP with sandbox account, and we have Version 2017.3103 (2017.6.30) of Corona.
I’m at a loss. They keep saying the app isn’t IPV6 compliant. With 10% adoption of IPV6 in the globe (and most of them being providers), I can’t imagine why they are enforcing this so early.
Any help here would be greatly appreciated. I’ve reached a new record of 4 rejections after being an iOS developer for 9 years.
The Apple message is most likely a red herring. It’s a generic message they send when your app crashes on start up. It’s not likely IPv6 at all.
You should ask them for the console log of the run and see if you can find why you’re crashing. You can also upload to iTunes and use TestFlight to get some other developers to download and run your app while tethered and see if they can see any errors using Xcode’s device log viewer.
One thing many developers skip over is making sure to delete the app from the device before testing and you have data left over from previous installs.
Rob
Hey Rob,
Thanks for chiming in. Let me add some more significant details I might have left out.
Yes, we did uninstall every time during testing.
When we test on IPV4, everything works as it should.
Apple is only testing with IPV6, no IP4 at all (wifi) (per their notice to me).
I have asked for the crash logs.
So the pointer for me is IPV6 itself. The IAP works with IPV4 (including call backs).
Other than putting my Mac on the LAN, turning on Internet sharing for IPV6 only - are there any other checks you recommend when using the Corona SDK?
When asking Apple for the crash report or even a stack trace, here’s their response.
None of which I’m able to duplicate using multiple test devices, arg!
Hello,
Thank you for your response. You app was presenting bugs, not crashing on launch nor crashing after a particular action.
Best regards,
App Store Review