Posts

Post not yet marked as solved
0 Replies
1k 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
Posted
by inexcitus.
Last updated
.
Post marked as solved
1 Replies
647 Views
Hello,an update for my app (2.0.2) was approved by the app review team on 2018/09/29 at 11p.m.It is 2018/10/01 at 5 p.m. and the update is still not available in the App Store. When I search for my app the last build (2.0.1) is shown.Did anyone ever had such a problem? How long can it take for updates to show up?Regards,Sascha
Posted
by inexcitus.
Last updated
.
Post not yet marked as solved
1 Replies
1k Views
Hello,as a developer I am so excited about the new Mac App Store, this is by far my favorite feature of macOS Mojave (and the Dark Mode of course).I have a couple of apps and I noticed that there is a new "Developer" site in the Mac App Store.This page can be found by typing in the developer name in the search bar. Is there a way to directly link to this page? I didn't see any "Share" button on this page like a product page has.Additionally, an image is shown, but for my profile it is empty. How can I add this image?I have added an image (and blurred out the name, I don't want to use this thread for marketing purposes 😊)ImageRegards,Sascha
Posted
by inexcitus.
Last updated
.
Post not yet marked as solved
1 Replies
473 Views
Hello everyone,I am developing an app that has a feature to detect and delete rarely used apps.The apps are installed in the /Applications folder. The apps were installed by the Mac Store, so the "owning" user is root.Although I have an admin account on my machine, I am not able to delete the apps from the /Applications folder because I do not have permissions to do so (root > admin).I found a couple of different apps on the Mac Store, that have the same features as my app. Because they are published in the Mac Store, the apps are sandboxed (take "Delete Apps" for example). When an app is selected for deletion, an admin prompt is shown where I can type in my password.How can I show such a prompt in a sandboxed app?I tried creating a helper utility using SMJobBless, but it always returns an error. I read the overview page and it seems that SMJobBless always returns an error in a sandboxed app.I created an AppleScript, which worked fine. However, I had to add the entitlement "com.apple.security.temporary-exception.apple-events" which is not allowed in sandboxed apps (published on the Mac Store).Because there are apps that show admin prompts, my question is: How can I ask the user for temporary access for an operation?Any help is appreciated.Regards,Sascha
Posted
by inexcitus.
Last updated
.