81–90 of 99 posts
Earlier quoted context omitted.
Isn’t this only a good thing if the human being on the other end makes reasonable decisions in the interest of (1) the App Store and (2) iOS developers? I understand I am biased by only seeing stories from developers who have issues getting apps approved, but these stories rarely end with a reasonable outcome.
Do we get to read the stories that end with a reasonable outcome? I highly doubt it.
Why is Apple so hard on small developers with incredible scrutiny on releases and sometimes seemingly arbitrary eval criteria, and Tik Tok can run rampant with a keylogger injected with JavaScript? Genuinely asking in good faith here as this is way out of my domain of expertise. I worked as a UI/UX designer for a company that shipped iOS and Android games exclusively and they (Apple App Store reviewers) were always h…
Money
Does anyone have a good link to a guide for dealing with the App Store reviewers' capriciousness? Or is it simply a roll of the dice, no matter how closely one follows the Apple documentation?
I'm about to release my first iOS app, and all of these posts of late are making me nervous. Does anyone have a good link to a guide for dealing with the App Store reviewers' capriciousness? Or is it simply a roll of the dice, no matter how closely one follows the Apple documentation?
I'm about to release my first iOS app, and all of these posts of late are making me nervous. Does anyone have a good link to a guide for dealing with the App Store reviewers' capriciousness? Or is it simply a roll of the dice, no matter how closely one follows the Apple documentation?
It’s annoying, but it’s not a huge deal.
The little experience I had with AppStore approval is that it’s mostly a game of persistence. They probably see some benefit from a little friction to prevent spam or perhaps it’s just pure stupid bureaucracy. I was rejected for asking access to the camera. The App applied filters to images taken. I stated as much in XCode, something along: this app needs access to the camera in order to apply its effects. Rejected f…
“Fun fact”: mentioning pre-release software is actually very much allowed by the App Store guidelines, and has been for several years. The App Store reviewers themselves have failed to keep up with the developer program license agreement changing and removing the “you can’t talk about beta software” bit. As an app developer it’s hilarious that we have to keep better track of that agreement than they are willing to bu…
For app developer, getting rejected is a huge deal.
For the reviewer, it is just a normal Friday. Trust me they don't care that much.
I'm about to release my first iOS app, and all of these posts of late are making me nervous. Does anyone have a good link to a guide for dealing with the App Store reviewers' capriciousness? Or is it simply a roll of the dice, no matter how closely one follows the Apple documentation?
In my experience they’ve been fine. Plan on getting dinged for something you forgot or for something minor. Make the tweak and resubmit. No biggie. It’s annoying, but it’s not a huge deal.
Would it have killed Apple to highlight the offending words in the original review?
TL;DR Apple re-used the term "Continuity Camera", which now applies to both a preexisting feature from iOS 12 and a prerelease feature in iOS 16. The app's description refers to the preexisting feature, but app review metadata-rejected the app anyway. Also, app review initially neglected to mention the specific problem, instead simply hand-waving about the rule against mentioning prerelease features.
Appreciate the TLDR. I was reading the tweets and confused on what the problem was.. Apple's naming scheme here seems awful.