We are facing some weird issue from last couple of days and our app is rejected from apple 3-4 times because of this reason.
"Thank you for your resubmission. We noticed that the previous issue has not been resolved. We are unable to proceed with the review of your app until this issue has been addressed"
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.
We have tested it hundreds times and everything works great with us on same devices. Is it something related to iPv6 ? Any help will be greatly appreciated.
Thanks
I have same experience. IPv6 rejected
Step 1:
Go to your project and check for all related AF_INET , IPv4
Step 2:
Replace them in AF_INET6 as IPv6
Step 3:
submit those dummy changes version as new project to iTune app store (dont use it for real production just for to PASS test)
Once that confirms you that it PASS, then do those changes to your real production release.
Hope it helps.
EDIT:
Also test your code with IPv6 only to make sure it does not crash.
Related
I had completed a Flutter app, which seems to work well in simulator. I then went on to release the initial version of the app to AppStore Connect and sent it to beta testers via TestFlight and they were able to test it without any issue and sent me some feedback.
I made a few changes to the app based on the feedback (nothing too drastic) and tested it throughly in the simulator which seems to work fine. But now when the users download the app via TestFlight it crashed while opening and I cant seem to fix it no matter what I try. Any help would be really appreciated
So far I have tried,
Followed this article letter to letter
Modify optimisation parameters in Build Settings as mentioned here
Tried this SO answer
Crash report from XCode is not much of use since it is not very readable (as attached in the picture).
Can't yet seem to find any reliable answer, Any help on this would be much appreciated.
I tried to release the iOS app in the Apple App Store. But it failed the review.
The app connects to Azure SQL Server DB on startup. It is implemented in C# Xamarin.Forms.
Initially (build x.x.x.0), I posted the app with following errors reported by reviewer:
"Snix_Connect (provider: SNI_PN7, error: 35 - SNI_ERROR_35)"
or
"Snix_Connect (provider: SNI_PN7, error: 40 - SNI_ERROR_40)"
I search the issue and tried to reproduce it.
I concluded that this usually happened when there are some issues with the Internet connection. I was able to reproduce it in the following 2 cases:
Disconnect WiFi router from the Internet, but preserve switched on,
and the iPhone still connected to this router.
Playing with VPN on iPhone. And while VPN is in progress of connection, I also tried to log in at this moment. This is not a robust method of reproducing the issue, but sometimes I got the error message above.
After this, I published the build on TestFlight. This is to test exactly the same binary as I uploaded for review. One of the teammates tested it on his device as well, and it worked fine on both devices: mine and him.
For completeness of the information, the app also worked fine on Android devices.
To make the error message more user-friendly I did the following.
If exception contains the errors above (with SNI_PN7), I replaced it with the following before showing to the user “Wi-Fi may be switched on, but not connected to the Internet, or Internet connection misconfigured".
In the current build, I have added the button “View report details” near error message. If the user taps this button he gets a page with stack trace and button “Copy report to clipboard”.
I asked reviewed, I also attached the file with screenshots on how to tap the button, and how to scroll page with the report and copy text to the clipboard. If he gets an error then I want him to copy the error report and share it with me.
After posting this last version, the reviewer completely ignored my request to share error details, and just attached a screenshot with the error message:
“Several errors occur: * Can't connect to the database. This may occur when there are issues with an Internet connection, unstable Internet connection, misconfiguration of firewall, VPN or antivirus, or issues with DB server. Please check Internet connection and configuration, and try again. * Error on checking connection to the database * Wi-Fi may be switched on, but not connected to the Internet, or Internet connection misconfigured (Ul code: 2)”
The reviewer just responded to me:
“We discovered one or more bugs in your app when reviewed on iPad running iOS 12.4.1 on Wi-Fi.
Next Steps:
To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue. For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue.”
Nothing useful for me.
Note, in previous builds reviewer several times repeated me, that login/password is incorrect. Then I wrote to him directly in review note:
“In case I provide you wrong login/password (/) to test application, you will get the following error message: «Login or/and password is incorrect», possibly with additional info, but the message is very clear about wrong login/password. All other error messages are not related to the wrong login/password.”
After this, I sent the appeal to the Apple:
“The reviewer does not provide enough info why he/she has issues to login to
I added functionality to build x.x.x.5 so that the reviewer can get technical info right from the app, and I asked about this info during the review. But the reviewer didn't provide any information. It looks like he/she completely ignored what I have asked about in the notes”
There is no response for appeal more than 3 working days.
Note, it was 5-th build I posted for review. Every time the reviewer responses about 1 day. He stops responding to my clarification in the resolution center. It looks like he behaves in a cat-and-mouse way, but not willing to publish the app.
I try to publish the app from September 16, I fixed, and clarify what I could suppose may be error cause on the Apple reviewer side. But no obvious progress, and I actually can't realize what I can do more...
Could somebody give me an idea about what I can do more? What can be wrong with the app? Why reviewer device could have issues to connect to Azure SQL Server?
I added details here that I consider essential. But if you need more info, let me know.
Thank you.
Recently I submitted my App to App Store for review and get a rejection which says my App is loading forever:
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPhone and
iPad running iOS 12 on Wi-Fi.
Specifically, the activity indicator spun indefinitely on launch, then
no further action was generated at the time of review.
Next Steps
To resolve this issue, please run your app on a device to identify any
issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to
this message in Resolution Center to provide information on how these
features were intended to work.
For new apps, uninstall all previous versions of your app from a
device, then install and follow the steps to reproduce the issue. For
updates, install the new version as an update to the previous version,
then follow the steps to reproduce the issue.
Resources
For information about testing your app and preparing it for review,
please see Technical Note TN2431: App Testing Guide.
For a networking overview, please review About Networking. For a more
specific overview of App Review’s IPv6 requirements, please review the
IPv6 and App Review discussion on the Apple Developer Forum.
Please see attached screenshot for details.
Before I submit for review, I have tested it on simulators and real devices, both takes 5-10 seconds to open.
I am using Firebase and Ionic, can someone give me some suggestions, what caused this issue? I google searched that Firebase supports IPv6 and now I have no clue why the issue occurred.
There's no hardcoded IP in the source, the only URL I am using is querying rates from Canada Post by url: 'https://ct.soa-gw.canadapost.ca/rs/ship/price'
Any help is appreciated.
We are having the same kind of report from Apple despite the fact we are testing on 6 different devices, iOS 11, 12, 12.1 with or without network.
We are also getting no issues from our beta testers.
As far as I can tell, on the Launchscreen we are spending about 6 seconds (iPhoneX) waiting for Metal to launch. There is nothing else in our log until our first VC hits its viewDidLoad.
We had the same kind of report two weeks ago with a very different iteration of our app, on resubmission the app went through
Now we have tightened up a lot of app behaviour and been rejected for the same reason multiple times
Its frustrating because of the lack of supporting information from Apple, such as logs.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
My last release of application which is 12.8 is rejected by apple saying that i have to add the IPv6 support to the app, I read and reviewed the recommended apple doc named Supporting IPv6 DNS64/NAT64 Networks thoroughly and came to know that already i am using the NSURLConnection class for network connectivity which is mentioned in the same doc, you can see the image from doc under section "Ensuring IPv6 DNS64/NAT64 Compatibility" mentioning the name of NSURLConnection class as a one of recommended class, below is that image
See the Recommended column in above image,
I thought something might be wrong. So, I did the set up of "local IPv6 Wi-Fi network on our Mac" as per the suggestion in the same apple doc under section *"Test for IPv6 DNS64/NAT64 Compatibility Regularly" and I wondered that the app is working like a charm without any issue or warning in debugger related to network connectivity.
I want some suggestions and recommendations from you related to same issue that is i am missing something to add support to IPv6 network connectivity. I have googled around for same thing and found the solutions whatever i have already tested, but still why apple rejected the app that i need to fix.
Any help will be highly appreciated.
Note:
Also not able to get one thing that this is the version 12.8 the app is on app store from last 3 years till the day apple never asked or raised the bug for adding support to IPv6.
Don't believe everything that a reviewer says. You might think that I'm, pardon me for my language, bull-shiting. I am not. They use an iPad to test an app unless it doesn't support such. I got two of my iPhone & iPad apps rejected for the exactly same reason. In the end, they were wrong. One app which keeps track of subway train arrivals connecting a remote server got rejected at the beginning of last Jan. for that reason. But they tested the app at 4 AM according to a screenshot they showed me. No subway is running at that time in my country. The app was working as expected. When I said that to the reviwer through the resolution board, he approved it in a matter of minutes. The other app, which uses the device camera, got rejected for the same reason some 10 days ago. But it doesn't even get on the Internet in the first place. So I was very suspicous. And I appealed. After talking to an appeal board person, it turned out that the app crashed on the iPad because of its support of the camera flash, which the iPad doesn't have.
So what should you do? Talk to the reviewer and ask for more information. So let me say again. Don't believe everything they say when they mention IPv6.
Sometimes apple is really behaves like strange, Nothing was there related to IPv6 support already as i have mentioned in question the network connectivity framework i used "NSURLConnection" supports the IPv6, Still why/how the reviewer raised that issue dont know, It wasted my lot of time, Yesterday i push the app to app store and today it is approved,
Whatever #EI Tomato told was right.
Happy Coding to all!!
I too got faced the same issue. I replied the review team to test the app build again and to provide me crash logs.
And withing a day, my app is approved for distribution.
So if anyone facing the same issue, make sure you test your app against IPv6 WiFi hotspot (Apple source).
If it worked with that environment, reply app review team to review again as it worked with the suggested environment. Most probably your app will get approved after that :)
Hope it might help someone. Upvote if it answered your issue. :)
Thanks to #El Tomato.
TL;DR
[Rejection reason from Apple for my case]
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPad running iOS 11.2 on Wi-Fi connected to an IPv6 network.
Specifically, your app was unresponsive upon launch.
Please see attached screenshots for details.
[My reply to them]
The app (Binary (0.0.xxxxx)) is working fine in our iPad and iPhone running iOS 11.2.1.
... MY DETAILED EXPLANATION ON HOW I TESTED THE APP ...
Can you please review again with the Binary (0.0.xxxxx)?
Is it possible for us to get the crash log, if any?
My app uses Alamofire 3.42 to make our API calls along with a host of other frameworks. All the frameworks and our server are IPv6 compatible and yet our app fails for the Apple Testing team when tested in an IPv6 only environment.
We have tested our app in a NAT64 as prescribed by Apple with successful outcome. Our packet trace too shows IPv6 addresses being called successfully and yet our app update keeps getting rejected again and again.
When we submitted the app the first time, it did get rejected once for the IPv6 issue but got accepted the next time we submitted. Although, now we are trying to submit an update which keeps getting rejected with only this issue being quoted.
This has taken a lot of our time and would really appreciate some help with this. TIA!