Joshua Browder (Hacker News):
Just got a call from Apple. The DoNotPay App will be removed by them in 5 minutes because “the app is too App Store like.” Each
@DoNotPayLaw
service needs to be a separate app and give 30% to Apple, violating guidelines 3.1.1 and 3.2.2(i) respectively.
When I asked: “why did they approve us for years and not have any problem,” the lady indicated that the policy had changed during the pandemic and government service apps are now required to process payments and give 30% to Apple through In-App Purchase.
When I tried to make the free client (like Netflix) under the new guideline “3.1.3(f) Free Stand-alone Apps,” they said it doesn’t apply to us and we must use iAP if we want to have an app.
Tim Cook told Congress that Apple was not taking advantage of the pandemic and had not added any fees. It had only “exempted additional categories of apps.” So why does this keep happening? Who told App Review to trawl through longstanding apps and threaten that they must add IAP? And why has this continued after the high-profile WordPress fiasco in August?
Joshua Browder:
DECISION REVERSED: APP BACK ON THE STORE. They admitted they made a mistake. Sunlight and transparency solves all problems, but not all developers are active on Twitter.
It’s a double failure that apps are in danger of removal even though they didn’t violate the guidelines and that this cannot be resolved using the official channels.
Stefan Esser:
Apple keeps abusing their monopoly and only in case the victim has enough outreach and can make enough fuzz they decide to reverse the decisions. Just how many other devs do not have that outreach and get bullied at will.
Previously:
App Store App Store Rejection DoNotPay In-App Purchase iOS iOS 14 iOS App
Resynth (via Hacker News):
The entire source code for the code hosting service used by developers, GitHub.com, has just been leaked to the public.
In a suspicious commit to the official GitHub DMCA repository, an unknown individual uploaded the confidential source code, impersonating Nat Friedman using a bug in GitHub’s application.
Nat Friedman:
GitHub hasn’t been hacked. We accidentally shipped an un-stripped/obfuscated tarball of our GitHub Enterprise Server source code to some customers a couple of months ago. It shares code with github.com. As others have pointed out, much of GitHub is written in Ruby.
Git makes it trivial to impersonate unsigned commits, so we recommend people sign their commits and look for the ‘verified’ label on GitHub to ensure that things are as they appear to be.
As for repo impersonation – stay tuned, we are going to make it much more obvious when you’re viewing an orphaned commit.
Bug Git GitHub Web
Juli Clover:
Apple today seeded a macOS Big Sur 11.0.1 release candidate to developers for testing purposes, with the new beta coming one week after the first macOS Big Sur 11.0.1 beta was released.
Note that macOS 11.0 has not been released to the public, nor did it have a release candidate. And there is no standalone download for the release candidate. You need to use the Beta Access Utility to update an existing macOS installation.
Xcode 12.2 also has a release candidate. However, unlike with GM builds, the archive expands to a beta app. So, presumably, this is not suitable for submitting to the Mac App Store.
Dave Nanian:
Today marks the first day during Big Sur’s development that I’ve actually been able to make a bootable copy.
The first day it’s been possible at all. Today. November 5th.
November. 5th.
Previously:
Update (2020-11-07): Apple:
You can now submit apps built with Xcode 12.2 Release Candidate using the SDK for iOS 14.2, tvOS 14.2, watchOS 7.1, and macOS 11.0.1 Release Candidate to the App Store.
Steve Troughton-Smith:
You cannot:
- Mention macOS 11, Big Sur, or Apple Silicon in your release notes
You can:
- Submit an app built with the macOS 11 SDK
- Submit an Intel+Apple Silicon app
- Submit from a machine running Xcode 12.2 on macOS 11.0.1 on Apple Silicon
Frank Reiff:
Given the impossibility of mentioning either Big Sur or Apple Silicon, I’m going to spend the next few days readying Mac App Store submissions but wait till after Tuesday’s event to submit them for review.
Matthias Gansrigler:
You’ll notice that the first item in the release notes reads “Improves compatibility with macOS”
I’d have loved to state that the app is now compatible with Big Sur, and runs natively on Apple Silicon. But I’ve heard reports (nothing official) that you’ll get rejected for it.
Max Seelemann:
Xcode 12.2 RC is crashing for me when trying to submit a universal Mac app to the App Store.
Also happens on the command line when using “xcodebuild -exportArchive”.
Mac Mac App Store macOS 11.0 Big Sur macOS Beta SuperDuper Xcode
