My app got rejected and it is showing this message:
It says it has bugs in iPad running, but I have only built the app for iPhone and not for iPad.
When I'm testing it on iPhone 5s having the same function it is working fine and in live tv I'm giving a url which gets down from the server some times and shows the message this event is currently not working.
How can these issues be resolved.
We found that your app exhibited one or more bugs, when reviewed oniPad running iOS 7.1.1 and iPhone 5s running iOS 7.1.1, on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.
The Live TV features does not work.
For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- screenshots
- steps to reproduce the issue(s)
- symbolicated crash logs - if your issue results in a crash log
If you have difficulty reproducing a reported issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Technical Q&A QA1764: How to reproduce a crash or bug that only App Review or users are seeing.
Follow the information in the tech note that was mentioned in your rejection. This makes sure that you are testing the identical app that was sent to Apple. Debug builds may behave differently from Release builds for all kinds of reasons.
There may be something in your local environment that makes things work only on your network. Go to the nearest Starbucks and try the app there.
Your app may do things that crash when it is run first but fix things for the second run. Erase the app from your device before trying it.
You may know weak points of your app and avoid them subconsciously. Apple's testers don't. They try to break your app. Get someone to try out your app and pay them money for problems found so they try to find the problems.
Related
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.
My app got rejected from app store with a reason that it crashes on launch screen. However, I've searched tremendously for any possibility that could cause the crash on launch, but unfortunately I am not able to reproduce the issue at all.
I've tried all steps mentioned by apple's team: symbolicated the crash logs, changed region of the device from India to US, tried keep the internet connection off/on while launching and so many things.
I have successfully uploaded more than 30 apps on app store and dealt with rejection several times... this time it is really killing me. I would really appreciate any help in this matter.
UPDATE
one thing I just noticed in the log: the app crashed when it was using 9.0.2 and now I've upgraded to 9.1 and it looks impossible to degrade again to 9.0.2 so is there any possibility that issue only occurs in 9.0.2 and if so, how can I resolve it without being able to reproduce it?
You should analyze the crash reports before submitting the app to app store.
You can find the guidelines to submit crash reports in Apple's documentation.
https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AnalyzingCrashReports/AnalyzingCrashReports.html
I am so worried about my new issue with submitting my app to itune store. This gives me error in resolution center like:
----- 2.2 -----
We found that your app exhibited one or more bugs, when reviewed on iPad running iOS 8, on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.
Specifically, the app launches to a blank screen.
For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
complete details of your rejection issue(s)
screenshots
steps to reproduce the issue(s)
symbolicated crash logs - if your issue results in a crash log
What is the issue with my app this is second time when my app is rejected?
Please guide me whats the mistake?
Thanks in Advance.
Vijay
I was using Evernote and it crash once, So after crashing I reopen it and it ask me for submit crash report to developer.
After some googling I have found in my iTunes Connect Account in Application detail there is one option called Crash reports.
So my conscience is that how to enable crash report submission in Application.
If the app asks for sending crash reports this has nothing to do with iTunes Connect.
The reports you see in iTunes Connect are send automatically by the phone (or iTunes?) when the user has agreed to send diagnostic reports when they set up their device. This happens automatically, you don't have to configure anything at all. Just go to iTunes Connect and get the crash reports.
But to be honest, iTunes Connect crash reports seem a little bit unreliable. If you see them at all it takes almost forever until you see them. Another culprit is that you have to check for new reports manually.
So Evernote, like basically everyone else, switched to a 3rd party service for crash reporting.
I use crashlytics in my own apps. But there are many others.
A good read might be Ray Wenderlichs Overview of iOS Crash Reporting Tools: Part 1/2 and Part 2/2
Some personal experience:
Since my apps don't crash often I usually see "Too few reports have been submitted for a report to be shown." in iTunes Connects crash reporter. But when I open the console of crashlytics is see 6 different crashes right now. Most of them affect only two or three people but it's good to be aware of new issues, even if few people are affected.
iTunes Connect does not show crash reports for prerelease versions of iOS. But it happened that I had a horrible bug in my app that lead to a crash instantly after people opened the settings of my app on a prerelease version of iOS. After the first crash report came in via crashlytics I fixed that bug and submitted an update. Because I didn't have time to test against the first betas it would have taken a while to be aware of this crash if I had relied solely on iTunes Connect.
We developed an app, and it works perfectly on several different emulators and devices, not once crashed, but both times we tried submitting to Apple it gets back to us as "2.1 - apps that crash are rejected" (or something).
I cant seem to find the log from them, or any additional infos. Is the crash log available anywhere? Or just ANY info? They only say that it crashed on an iPad 3rd Gen with iOS 6. We ran on a device like that and it didnt crash for us.
Unfortunately, Apple doesn't provide detailed logs of their review process, although crash logs are sometimes provided, as indicated by #jsd in the comments below.
In theory, crash reports get synchronized with iTunes and can be collected by Apple and provided to you via iTunes Connect, but in practice, that rarely works - or only with large delays.
However, you could integrate some Crash Reporting into your App. Here are a few services that allow you to do that without much hassle:
HockeyApp
Crittercism
BugSense
TestFlight
Crash reporting integration in production versions of my apps have been proven to be very helpful, so I'd highly recommend this. Good crash reporting services provide an SDK to be included in your app, and generate symbolicated, readable, ready-to-use crash reports that make tracking bugs very easy.
As for the cause of your app's crash, here are some basic guesses:
Do you use ARC (Automatic Reference Counting)? You should.
Did you run the Static Analyzer in Xcode (Product ➞ Analyze)?
Did you test with different environments (e.g. internet connection via 3G, WiFi or none at all)?
Have you deleted and reinstalled the app on your device, or did you just update it?