“eskimo”

AFAICT, based on my view of your capabilities, this additional capability was assigned to your team correctly. Specifically, the capability enables com.apple.developer.family-controls for Development, Ad hoc, and App Store distribution for these App IDs: Q________K.c__.j________.u____________r Q________K.c__.j________.u____________r.device-activity-monitor Q________K.c__.j________.u____________r.shield-configuration Q________K.c__.j________.u____________r.shield-action Note Recently we’ve started enabling the capability for the entire team, rather than for specific App IDs, but your request was processed before that policy change. Please run this experiment: Navigate to Developer > Account > Identifiers. Select one of the App IDs from the above list. Make sure the Family Controls (Distribution) capability is enabled for on it. Now navigate to Developer > Account > Profiles. Click the add (+) button to start creating a new profile. Select App Store Connect and click Continue. Select the same App ID

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Earlier I wrote: [quote='884220022, DTS Engineer, /thread/821842?answerId=884220022#884220022'] I’m gonna use FB22464790 to dig into this a little. [/quote] I now have a definitive answer for this. It seems that you aren’t do anything wrong here, and that something within Core WLAN is preventing link-quality events from being delivered. We’ll use your bug to investigate that. On the workaround front, the obvious option is to poll the link quality property. In my tests that was updated as expected. Now, polling is less than ideal but, hey, that’s why it’s called a workaround (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So the lead bug for this seems to be FB18764644. Looking at that it seems that the 26.5 betas should show improvements, but probably won’t fix all the cases of this. I don’t have any info to share as to whether a full fix will catch the macOS 26.5 bus or not. As always, I recommend that you re-test on beta releases as we seed them, although I recognise that testing for this particular bug is tricky, and gets trickier as we approach a complete fix. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885154022, PolarBear3395, /thread/812992?answerId=885154022#885154022, /profile/PolarBear3395'] Is the only way to fix this literally to wipe your Mac and do a clean install? [/quote] It might be the only supported way to recover, but there are alternative approaches you might take. As your aware, the file system protections here are contingent on SIP being enabled, so you could: Disable SIP, make the change, re-enable SIP. Or boot into macOS Recovery and make the change from there. This isn’t supported because we don’t support changing data structures behind the back of running systems. Did anyone file a bug about this? Because I scanned this thread and can’t actually see a bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885388022, pkahohi, /thread/823479?answerId=885388022#885388022, /profile/pkahohi'] Is there any mechanism to obtain a hashed or tokenized representation of the SIM/subscriber identity … ? [/quote] No. You could file an enhancement request for that, but I don’t fancy its chances. Such an API could be used for fingerprinting, which is something that Apple is actively working against. See the footnote about entropy at the bottom of this reply. [quote='885388022, pkahohi, /thread/823479?answerId=885388022#885388022, /profile/pkahohi'] are there any Apple-recommended approaches to uniquely distinguish between different SIM cards over time … ? [/quote] No, but an ER along those lines seems more viable to me. [quote='885388022, pkahohi, /thread/823479?answerId=885388022#885388022, /profile/pkahohi'] The gap is this [/quote] One way to close that gap would be for you to stand up a web service that allows your app to request some sort of authorisation token when that service is accessed over WWAN. Your app co

Thanks for all the details. Yeah, I’ve never been happy with the whole ‘running your app as command-line tool’ process. It seems very brittle, especially in situations like yours where the installer package, and hence the post-install script, runs outside of a user context. However, it is a documented, and hence supported, approach. Given that, we need to keep it working, so a bug report is called for. Before I send you off in that direction, however, I want to ask about this: [quote='885329022, pnelson, /thread/823493?answerId=885329022#885329022, /profile/pnelson'] My OS is 26.5 [/quote] Because macOS 26.5 is still in beta, it’d be to your advantage to determine whether this problem was introduced by that update. If you retest this on macOS 26.4, does it have the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad that you got at least something working. [quote='885311022, captadoh, /thread/808917?answerId=885311022#885311022, /profile/captadoh'] So it looks like this is a hardware thing. [/quote] I’d be quite surprised if that were the case. Are you able to go back and retest with your iPhone 12 mini? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885262022, floorish, /thread/823455?answerId=885262022#885262022, /profile/floorish'] Contacting App Review seems to be available after a submission is rejected [/quote] As Etresoft mentioned, there are other options. [quote='885262022, floorish, /thread/823455?answerId=885262022#885262022, /profile/floorish'] the com.apple.security.scripting-targets entitlement is not a temporary exception [/quote] Correct. [quote='885262022, floorish, /thread/823455?answerId=885262022#885262022, /profile/floorish'] are these entitlements also rarely accepted? [/quote] I don’t know. I have a couple of theories on that: Apps that publishes a scripting target, both app and third-party, are so rare that no one every exercises this case. Folks use this a lot, never have any App Review problems, and thus I never hear any complaints. I suspect it’s the former, but really that’s just a guess. Regardless, you can decide whether this is relevant to you by first checking whether any of your target apps publish helpful scriptin

I can’t say definitively. As I’ve said a couple of times, I’m not involved in this approval process. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I got this working as following: Using Xcode 26.4, I created a new project from the macOS > App template, choosing Storyboard for the UI. I removed @main from AppDelegate. I added a main.swift file like so: import Cocoa func main() { let delegate = AppDelegate() _ = NSApplication.shared NSApp.delegate = delegate NSApp.run() } main() The difference is that I put the code into a main() function. That function name isn’t special — you could just as easily call it foo() — but it’s important that the code not be at the top level. Top-level code is weird in Swift (-: Having said that, I recommend against doing this. Rather, just call NSApplicationMain. Note that the doc you referenced says “which is functionally similar to”, not “is implement as”. The actual implementation of NSApplicationMain is very different, and by not calling it you’re taking yourself far off the beaten path. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.co

It looks like you’re trying to build this software from open source, which suggests two potential paths forward: You can escalate this via the support channel for the open source project. They may already have investigated this issue. You can dig into the source code to investigate it yourself. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, I have a question (-: What platform are you targeting? Because the answers here are very different between iOS, including its child platforms, and macOS. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I read your bug report and it’s somewhat light on details. Could you update the bug with more about what you’re like to see here? Specifically, are you concerned about threads or about messages within those threads? And maybe a description of how this features works on other forums platforms? FWIW, I rely on the thread read/unread state a lot, which is visually indicated by the title of the thread being in bold. I find that super useful, and also quite reliable these days. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com