3 ms·
> go through some verification Yep. "Some" verification. Random and arbitrary as Apple's verification is known to be. How many times have you read about a dev
by nottorp 3y ago
> go through some verification
Yep. "Some" verification. Random and arbitrary as Apple's verification is known to be.
How many times have you read about a dev who had an app rejected, resubmitted it with no changes and had it approved?
How many times have you read about rejections without a clear motive and any further explanation?
- dagmx 3y agoAnd how many times have you heard about someone rejected from notorization? It’s been a thing for years now on Mac with many, many notarized apps.
- nottorp 3y agoThere's an example right in the article?
- dagmx 3y agoWhich one? I see no mention of Apple blocking notarization of the app.
- nottorp 3y agoWhatever app had to add a ... map?
- dagmx 3y agoThat has nothing to do with notarization though. That’s just system rules. iOS restricts what apps can run in the background based on their capabilities.
- nottorp 3y agoDid it do anything useful for the user yes/no? Was it rejected by Apple because it didn't fit the usage patterns they could think of in Cupertino yes/no?
- dagmx 3y agoAt this point, it’s clear you’re not even trying to understand the difference between the following 1. App Store rules 2. Notarization of apps outside the App Store 3. System rules like security and task scheduling They are independent concerns. You’re conflating the limitations of the third point and blaming it on the first two.
- nottorp 3y agoThe passing the blame game yes …