2 ms·
Presumably you can't check for violation yourself without submitting.
by megous 7y ago
Presumably you can't check for violation yourself without submitting.
- saagarjha 7y agoOf course you can! How do you think Apple's checking your binaries?
- megous 7y agoUsing some internal tool.
- saagarjha 7y agoNo, it’s almost certainly just a search for strings and looking through the symbol table.
- megous 7y agoThat would be very easy to work around with dlopen and some string obfuscation. It's probably a bit more involved.
- plorkyeran 7y agoIn practice it is pretty easy to slip things past the automated checks if you try to, which is one of the reasons they threaten you with a permaban for doing so.
- justinclift 7y agoThe internal tool is very likely using/parsing otool / ldd output and similar. eg cli tooling that comes with macOS itself
- rdevnull 7y agoexactly. Apparently Apple just started now to check against these private APIs.
- plorkyeran 7y agoYou can, and the rejection email even provides instructions for how to do so.
- megous 7y agoAnd where will you get the current list of all forbidden functions/APIs, not just those for this specific case with Electron?
- LeoNatan25 7y agoWhatever symbols are found in the public header files in the /System/Library/Frameworks. Iirc, there are tools which look at a binary's used symbols and compare them to those headers.