Earlier quoted context omitted.
Maybe Apple should improve PWA support so that could be a reality instead of a pipe dream.
Because you need a pwa for a blog website?!
Yeah, if you want to get notifications when people interact with your site.
A Tumblr developer on the App Store approval process
151–160 of 165 posts
Re: A Tumblr developer on the App Store approval process
#152Earlier quoted context omitted.
> App Store Reviewers are completely asinine I recently had an interaction with a food delivery customer care executive (many like this; of other businesses as well) and the kind of conversation I had with them it seemed to me that someone must have flattened the brain matter with a rock before stuffing it back inside their skulls. Then it dawned upon me. Nope. They just are as much a victim of these huge corps and t…
At this point it's really better to automatize support. They can't do anything a policy rule-based bot couldn't do.
That's one of the reasons representatives are stuck with scripts and decision trees these days: it's just another step on the road to complete automation of phone support.
Having dealt with companies that decided to automate their phone support entirely, this is not something to look forward to at all.
Re: A Tumblr developer on the App Store approval process
#153Earlier quoted context omitted.
open a browser, navigate to https://www.reddit.com/r/tits/ , click yes, done!
When I go to that link (on iOS), my only option is to “view in app”, which is a shitty option to offer. PWAs would free them from having to put up with Apple’s restrictions crap.
> PWAs would free them from having to put up with Apple’s restrictions crap.
Apple knows this, hence why they've not implemented the features needed by PWAs, and why they ban all browser rendering and JavaScript engines besides iOS Safari's.
Re: A Tumblr developer on the App Store approval process
#154> In the case of Tumblr, this would be a reviewer going to search, typing in something like 'tits’ and finding porn. Just want to emphasize this part. App Store Reviewers are completely asinine. Like, dumb as a rock. It’d almost be funny if their stupidity didn’t block your app approval. To be explicitly clear: if your app contains UGC, they will explicitly go and search for things to ding you on, and then fault you…
> They will go to the search bar and type in “milf” or “butts” (I wish I were joking). They’ll try to search for drugs on your marketplace. I don’t understand why you think that’s dumb. This is what people who download the app will do, so they’re trying out real scenarios that will happen. They don’t want to have there be a segment on the nightly news saying, “App Store Full of Porn!” Which is what will happen in the…
I feel like with that logic web browsers should be banned including their own. There’s nothing stopping me from buying a brand new iPhone and immediately opening up safari and finding porn. Heck even their own search feature built into the OS can do this. Rules for thee and not for me.
Re: A Tumblr developer on the App Store approval process
#155How come any internet browser can get past the 'porn' policy since all of them will show porn when you type 'porn'?
All the default engines are set to “moderate” by default. “Porn” does not show anything immediately explicit. A tiny hurdle, but still a hurdle and that is enough for many people to rethink. Tumbler you could by default get horrific images in search results.
Re: A Tumblr developer on the App Store approval process
#156Earlier quoted context omitted.
That doesn't make sense to me. The iPhone comes with a web browser. If a user wants milfs and butts they can put that in the address bar.
> The iPhone comes with a web browser. The iPhone comes with a web browser that has parental controls . A parent can have some degree of control over what their kids see when they use Safari. A parent does not have that choice with typical applications.
Sure they do. I’ve used those parental controls myself.
Every single app in the App Store has an age rating. An underaged user can only download apps in the age categories that their parents have specifically authorized.
Re: A Tumblr developer on the App Store approval process
#157> In the case of Tumblr, this would be a reviewer going to search, typing in something like 'tits’ and finding porn. Just want to emphasize this part. App Store Reviewers are completely asinine. Like, dumb as a rock. It’d almost be funny if their stupidity didn’t block your app approval. To be explicitly clear: if your app contains UGC, they will explicitly go and search for things to ding you on, and then fault you…
Couldn't you just create an account for them that has a few whitelisted posts that are squeaky clean? Or better yet apply the whitelist when a request is made from a not-yet-released version of the app, based on headers?
Secretly giving Apple’s reviewers a different version of the app is a very good way to get them really upset at you. (And, IMO, rightfully so: you’re no longer acting in good faith. They might not be either, but when you’ve changed your position you lose the ability to make the “we tried our best to be reasonable” argument.)
Re: A Tumblr developer on the App Store approval process
#158Earlier quoted context omitted.
> I need to connect to an iPhone as a target device in order to build. This is not correct. You can build just fine without any iOS device.
Alright, I looked around and finally came across this StackOverflow answer[0] that supports your point. Turns out, if you use let Xcode handle code signing for you, you need a physical device for it to target (which is what we were doing), however there also exists an option to manually sign code yourself, in which case you wouldn't need a physical device. Thanks for the correction, I'm glad to be wrong! [0] https://…
You can just select the simulator target if you’re testing your app. When making a release build, you can either select a real iOS device or the generic iOS device that is there for that purpose. (Honestly, I agree with you on some of your points, but some of them seem a bit contrived or a derivative of “I need to learn how to do things in Xcode”. I’d be the first to admit it has a confusing interface for some things, but there’s also like some part of it you’re just going to have to deal with.)
Re: A Tumblr developer on the App Store approval process
#159Earlier quoted context omitted.
Well I guess my own experiences with Apple reviews must be fictional garbage too then! (I should clarify that, like GP, I am referring to the substance of the review, not the tone.)
> Well I guess my own experiences with Apple reviews must be fictional garbage too then! This has fallen off the front page, so I’m asking out of real curiosity: 1. Have you genuinely had an app rejection that states that the reviewer typed “milf” (or something equivalently unlikely) into a search bar - and that is given as the reason for the rejection? ie: how else does the OP know this is the actual reason? 2. Do y…
Hi! I assure you, everything I wrote is accurate to the best of my knowledge, except for one part I should probably address first: yes, nobody in app review will literally “yell” at you. Their correspondence will be invariably polite; I simply used it as a figure of speech to indicate that they will flag you for something. In a sense, the politeness is even more irritating because you’ll get a message like “sorry, we can’t approve this app” and then a rep will come on and parrot the same thing to you, and regardless of how polite they are you know you’re going to have to deal with a significant headache at best and a complete loss at worst, if whatever Apple wants you to change is integral to your app.
Now, to answer the other part: yes, as stupid as it sounds, they do exactly this. I work on iSH and they flagged a build of our app for package management functionality. Ok, we said, that’s not the main purpose of the app, and we don’t want to fight you about it, so we’ll remove it. And they approved it…for a bit, until they rejected it again. Why? “During review, your app downloaded code”. Our app doesn’t download code. What actually happened was that we ship a wget, and the reviewer used this to go to a website and re-download a package manager, and then used that to download code. I mean, what are we supposed to do in response to that? We removed what you wanted us to remove (even if we didn’t have to, based on a close reading of the rules) and if you are going to go and download it again, what are we supposed to do?
I’m not really in a position to speak for my employer and their review experience, but the UGC content/porn example is one every social media app knows about. You’ll get a rejection in App Store Connect with the “problematic content” and you’ll go check up on the demo account you gave them and it’ll have these terms in the search history. Blonde, boobs, sexy: it’s the stupidest search queries, but they will absolutely go and type those words into the search field and flag you for it, and your analytics will confirm it.