Disclaimer:
This app has been on the App Store for more than 3 years now and I haven't done any changes regarding Network.
Apple's review notes:
Guideline 2.1 - Performance
We discovered one or more bugs in your app when reviewed on iPad
running iOS 10.3.1 on Wi-Fi connected to an IPv6 network.
Specifically, your app displayed an error message when we tried to
create an account.
Please see attached screenshots for details.
Next Steps
To resolve this issue, 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.
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 supporting IPv6 Networks, please review
Supporting IPv6 DNS64/NAT64 Networks and About Networking.
Guideline 2.1 - Information Needed
We were unable to sign in to review your app with the demo account
information you provided.
We have attached a screenshot of the error message displayed when we
attempted to sign in.
Next Steps
To help us proceed with the review of your app, please provide a user
name and password in the App Review Information section for your app
in iTunes Connect. Please be sure to include content in your app that
demonstrates the features and functionality available in your app.
To provide demo account information:
Log in to iTunes Connect
Click on "My Apps"
Select your app
Click on the app version on the left side of the screen
Scroll down to "App Review Information"
Provide information in "Demo Account" and/or "Notes" as appropriate
Click "Done"
Once you've completed all changes, click the "Save" button at the top of the App Version Information page.
Reply to this message to confirm the availability of a valid demo account and we will continue the review.
While your iTunes Connect status shows as Metadata Rejected, we do not
require a new binary to correct this issue. Once this information is
available, we can continue your review.
Could anyone help me understand what is going on?
Apple began requiring all App Store submissions to support IPv6-only networks as of June 1, 2016.
Apple began reviewing existing apps on September 7, 2016 to remove “apps that no longer function as intended, don’t follow current review guidelines, or are outdated.”
The message you received indicates that Apple reviewed your app and found that it didn't work on an IPv6-only network. This means it doesn't follow current review guidelines and is eligible for removal.
You need to test your app on an IPv6-only network, figure out why it doesn't work, fix it, and submit the fixed version.
Related
My app was rejected when being reviewed for the iOS App Store. It appeared there was a technical inconsistency when running the app on the reviewing device versus devices I used for testing. I opened a Technical Support Incident (TSI), as I believed I needed technical support in order to further investigate the issue. They responded with the following:
App Review has found an issue with your app that requires a technical investigation. To initiate this investigation, request a rejection clarification using the "Contact the App Review Team” form:
https://developer.apple.com/appstore/contact/?topic=clarification.
When completing the form above, please include the name of your app and its associated Apple ID.
However, it seems that "rejection clarification" is no longer an option on this website:
I'm wondering if anyone has faced a similar issue, and what is the best way to proceed?
I got the following response from Apple Developer Technical Support (DTS):
You would select 'appeal an app rejection or app removal' and request diagnostic information from the devices used (if it is available).
My App got rejected because we didn't provide Demo account for Login. Also the screenshots provided are of only Launch screen and Login/SignUp pages.
Apple rejected the binary saying:
1 Performance: App Completeness
To help us proceed with the review of your app, please provide a user
name and password in the App Review Information section for your app
in App Store Connect.
3 Performance: Accurate Metadata
Please revise your screenshots to ensure that they accurately reflect
the app in use on the supported devices
However, to fix this I can provide the functional Login Account and the New screenshots depicting the actual content of App.
Still they have asked me for a new binary even if there is no change in the App-side:
Since your App Store Connect status is Rejected, a new binary will be
required.
My question is:
Should I appeal to Apple for using my existing build after I provide the login credentials and updated screenshots?
Or do I need to upload a new binary even if there are no changes in it except the build number?
Apple reject my application due to below reason:
2.2 Binary Rejected
Guideline 2.1 - Performance - App Completeness We discovered one or more bugs in your app when reviewed on iPad and iPhone running iOS
From Apple
2. 1 Performance: App Completeness
3. 1.1 Business: Payments - In-App Purchase
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPad and iPhone running iOS 11.3.1 on Wi-Fi connected to an IPv6 network. Specifically no action occurs when we attempt to purchase your declared In-App Purchases.
Please see attached screenshots for details.
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.
Guideline 3.1.1 - Business - Payments - In-App Purchase
We also found that your app offers in-app purchases that can be restored but does not include a "Restore Purchases" feature to allow users to restore the previously purchased in-app purchases, as specified in the "Restoring Purchase Products" section of the In-App Purchase Programming Guide:
"Users restore transactions to maintain access to content they've already purchased. For example, when they upgrade to a new phone, they don't lose all of the items they purchased on the old phone. Include some mechanism in your app to let the user restore their purchases, such as a Restore Purchases button."
To restore previously purchased in-app purchase products, it would be appropriate to provide a "Restore" button and initiate the restore process when the "Restore" button is tapped by the user.
Request a phone call from App Review
At your request, we can arrange for an Apple Representative to call you within the next three to five business days to discuss your App Review issue.
Request a call to discuss your app’s review.
/// My openions:
I have tested complete application with live enviorenment and IAP working fine with restoring functionality.
Also in my feature section:
Please suggest:
Thanks
Please add any character in display name then save it. Then remove that word and save it.
It will change automatically waiting for review.
On the next day of my question I just edit the discription of in app purchase and save it. It removed the error and show status waiting for review.
See the screen shot.
I have to solve the problem of how to allow review (testing) of our app by prospective developers, when the app is not yet Ad Hoc. I can't get it that far. Here's the problem:
I have to find a new developer to help update our app for 2016. It's a 365-day calendar of info that updates every year. The initial app download is a shell (free) in which 29 in-apps, each a different geographical region of information, can be purchased & downloaded. Regions are 16.95 each. In order to help candidates familiarize themselves with the app, they need to be able to download an in-app region and see the app function. I can't expect candidates to pay 16.95 for a region, so I need a way for them to test the app.
1: I can't use the promo code feature in iTunes Connect because it is worthless for in-app testing, which makes it worthless for many apps out there since the in-app is often where much of the critical content lies.
2: I can't sign candidates on as Sandbox or TestFlight testers because I can't upload the app into iTunes connect without getting an error message I don't know how to fix. When I try and submit the app through XCode or the App Uploader, I get an error reading, "The Info.plist in the package must contain the CFBundleShortVersionString key." I don't know what to do with that error, so I can't get a version into the iTunes Connect environment to invite testers into.
My problem is that after migrating project to XCode6 I just can't submit my app - it's permanently becomes "invalid" - get status "invalid binary" after 10-30 minutes.
Before migration there was no any troubles
There is no code modifications since old XCode version (5.1)
Most frustrating is as other users I received email from ITC
support, but it does not contains any details at all!
iTunes Connect
Dear XXX,
The status for the following app has changed to Invalid Binary.
App Name: XXX
App Version Number: 2.0
App SKU: XXX
App Apple ID:XXX
To make changes to this app, sign in to iTunes Connect and open the Manage Your Applications module.
If you have any questions regarding your app, click Contact Us in iTunes Connect.
Regards,
The iTunes Store team
I wrote email to ITC support, but there is still no answer. Any suggestions? It's hard to me find any reason cos app successfully passes validation during upload.
Large amount of tests lead me to next conclusion: one of third-party libraries (AppsFlyer) uses Advertising Identifier. I removed it from my app and for now all is ok.
I think this problem is because of new builds/prereleases system - things which previously lead to warnings during validation/uploading now are not appear.
So annoying...
I'm using several libraries which uses the AdvertiserId on several apps and the builds were submitted successfully.
When submitting the app, Apple ask 3 question about your app. The third is about using the Advertiser ID. Did you checked any of the options there? If not, You should....