Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 3 years ago.
Improve this question
From Apple
2. 1 Performance: App Completeness
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPad running iOS 12.1.1 on Wi-Fi.
Specifically, we were unable to connect to the internet
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 help to solve this issue and enable app for external tester or generate public url for app.
Disclaimer: We are checking internet connectivity on login and its working good in iPad and iPhone both.
Apple is testing your app in ipv6 connection. so it may get timeout or network not connected errors.
you can check this similar question and can debug your issue.
IPv6 App Store Rejection
Apple App Store IPV6 Requirement
There is an issue in your code:
(flags == NetworkReachabilityFlags.Reachable)
should be:
(flags & NetworkReachabilityFlags.Reachable) != 0
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed last year.
Improve this question
My app is rejected with the following message i don't fully understand, because there is a login and it is not Apple related. I provided the login in Resolution Center.
Guideline 2.1 - Performance - App Completeness
Specifically, we were still unable to Sign up or Sign in with Apple. Please review the details below and complete the next steps.
Review device details:
Device type: iPhone and iPad
OS version: iOS 14.4
Next Steps
Please run your app on a device to reproduce the issues, then revise and submit your app for review.
If at first you're unable to reproduce the issue, try the following:
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce.
For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.
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.
I can give you multiple options to debug and solve this problem:
https://developer.apple.com/forums/thread/651533?page=8 There is an issue with 14.4 and xcode 12 related to apple login. You can try with iOS 13 and submit video at resolution centre.
Is it due to two factor authentication ? Cross-check apple ID settings.
Try changing http to https on web server, if applicable.
Let us know which option was useful to you.
It sounds like Apple believes there is a social login (Google, Facebook, etc) included in your app. You're going to need to ensure there's not.
You've already mentioned that there's not - but perhaps there is some package you're using which includes code that triggers some automated flagging process? Review your third party dependencies.
The best thing you can do though is get more specificity from Apple. They will usually clarify rejection notices if you contact them with questions.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
Apple started to reject our app because they can't access our app because of geo-restriction. We have also a video which shows our app's demonstration in the review process. And Apple Review Team can't access app in U.S.A. It's a gambling app and it must be geo-restricted according to the App Store Review Guidelines.
5.3.4 Apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) or lotteries must have necessary licensing and permissions in the locations where the App is used, must be geo-restricted to those locations, and must be free on the App Store. Illegal gambling aids, including card counters, are not permitted on the App Store. Lottery apps must have consideration, chance, and a prize.
We show a pop up to user which says basically that they could not access to the app because of the geo-restricted.
Apple Review Team's Response:
5.3.4 Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPhone running iOS 13.5 on Wi-Fi.
Specifically, upon launch, your app displayed an error message. All apps submitted to the App Store must function correctly and provide access to all features and content at the time of review, regardless of network, device capability, location, etc.
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.
How can we make the app geo-restrict and also provide access to all features?
Thank you.
Specifically, upon launch, your app displayed an error message.
Was your error message clear to the user, explaining what had happened and what they must do to resolve the issue? Did you explain this restriction in your App Store description (particularly if you're submitting to any store where the restriction would apply), and in your App Store submission? Even if the user cannot proceed, they should have a good experience. It shouldn't just be an alert saying "go away." A legitimate user might launch your product while traveling, and it should be clear that they need to wait until they get home.
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.
This is the key point. Contact them. You may need to give them a backdoor that unlocks it for the Apple site. You may need to give them a special login. They may work with you in other ways. But contact them.
When you say "keeps getting rejected," that suggest more to the story. Did you contact them and did they tell you other things? Did you just keep submitting?
even though your app is geo restricted,you need to implement code for testing purpose so that they can test all the functionality of the app.i suggest you create a user for testing that will bypass the geo restriction and specify the name and password at notes in app submission.
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?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
My concern is to improve my app by collecting crash reports via the crash report service in iOS. For internal testing I uploaded a beta version of it using Xcode, containing a built-in error throwing NSRangeException. After archiving and uploading the app to the store it was installed on an iPhone 5s running iOS 9.3.3 using TestFlight. In my opinion I followed all the steps described here, but with no success.
In the diagnostic settings of the device, automatic crash reporting is enabled and I can see various crash logs (>10) caused by my app. On the iTunes Connect website I see only three overall crashes and just one is shown in the Xcode Organizer. Even after syncing the device through iTunes nothing changed.
Contacting Apple-Support didn´t help either. because they had "very little information available".
For stability improvement I need to make the crash reports available, so I have a couple questions:
Which steps are done internally by the crash reporting service and how long does it take to see some results? (As mentioned in iOS developer library documentation it can take up to three days, which are long overdue by now).
Are the reports caused by the same error gathered and reported as a single entry? If not what is the procedure?
I already searched for some similar questions and came up with the following information:
Users say that the iOS app crashes without any further explanation
Not able to get crash reports in iTunes connect for a live application in AppStore
I can not get a crash report in iTunes Connect
submit crash logs to Apple via iTunes Connect
How do you view TestFlight crash logs?
I hope somebody has deeper insight or already gained more experience using Apple`s Crash Report Service and could share this information. Thanks a lot in advance.
Fabric may be a good choice.
It can collect you crash report, and give a crash description.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
Im actually getting ready to post my app to iTunes .
The app is a WiFi based app and it is dependent on an other hardware device to be up and running in the same WiFi network. So without this hardware device the user will not be able to login into the app and use it.
Hence I would not be able to provide in a demo account to Apple as they will not be having the needed hardware with them.
So the question is that, Will my app get rejected if the demo account is not provided?
My app was rejected because of that. So we had to find a way to let Apple test the whole app. The easiest way will be to provide a demo mode which enable/simulate all of your feature.
I recently went through a similar situation with my company. We have hardware that the app connects with and controls so we had to make a demo account for Apple to use that used hardware in our office in order for them to go through the app.
With hardware you will also be forced to either send your hardware in for apple to test with the app so they can see it actually working with the app or create a video that shows the app interacting with the hardware.
I think that it will depend on what hardware you have and how the app works but we were able to get our app approved by just making a video that demonstrates the app and hardware working together.
I think for this you need to register your hardware for MFi Program. After that you can upload your app in App Store.
Short answer - If your app requires login then yes unless no.
Descriptive answer - If your app needs some type of login then you are required to submit a demo account using which app QA engineers can test your app before approving it. It is necessary for them because they test around 700 apps in a day and out of those more than 50% apps requires a login. It is nearly impossible for them to create new accounts with pre-filled data to test app. For example If your app has subscription of 10 USD per month then they are not going make in-app purchase to test that feature.