Post not yet marked as solved
Post marked as unsolved with 0 replies, 1,034 views
Hello fellow developers,I am the developer of several apps that are available on the Mac App Store.Yesterday, I finished working on two small updates (minor layout adjustments, nothing fancy or feature changes) for two of my apps - when I woke up this morning, I checked my notifications on my iPhone and saw two App Store Connect notifications that let me know, that both of my updates were rejected.The apps were first released back in August of 2017.Both the updates were rejected for the same reason:1 Safety: Objectionable Content (macOS)Guideline 1.1.6 - SafetyThank you for your submission. During our review, we found that your app is not appropriate for the App Store.We encourage you to review your app concept and evaluate whether you can incorporate different content and features to bring it into compliance with the App Store Review Guidelines.Next StepsFor information about available diagnostic and other low-level data, see I/O Kit Fundamentals.First of all, yes, both of the apps use IOKit. The apps show some battery information (voltage, current health, battery level etc.). This feature is available since the very first release and I am kind of curious why this is a problem now.In an earlier update I implemented a feature that read sensor information. In order to do so, I had to add a sandbox exception which lead to a rejection. I know that with this framework (well with some methods at elast), you can cause some serious damage to a machine (i.e. lowering the fan speeds etc.), but these methods need the sandbox exception added to your app - which will get your app rejected.Did anyone else submit an update and get it rejected? Probably the easiest step would be to simply remove this feature (it is "only" one of many features), but I am stil, curious why all of the sudden this is a problem and for the last 59 builds it was totally fine.TL;DR: Can IOKit no longer be used in sandboxed apps?Regards,Sascha