“apple pencil charging”

Has anyone experienced an app disappearing from App Store Connect? Any advice on escalation would be appreciated. There have been a couple of cases where the app was automatically removed from the store after a software update even though the status said it was ready for distribution. It happened in March 5th. I've asked Apple, Inc. But there has been no explanation.

[quote='881073022, chkpnt, /thread/748447?answerId=881073022#881073022, /profile/chkpnt'] Is this a bug or intentional? [/quote] I’d call it a bug, by my opinion doesn’t matter (-: If this is causing your product significant grief then it’s worth filing a bug about, even if it’s intentional. [quote='881095022, chkpnt, /thread/748447?answerId=881095022#881095022, /profile/chkpnt'] I've filed FB22313288. [/quote] Thanks. It’s been marked as a duplicate of a bug that was filed internally, one that’s definitely with the right folks. I don’t have any info to share beyond that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m still not entirely sure what stage you’re at here. You started this thread talking about manually checking requirements, which is not what I recommend when dealing with XPC. Rather, you should apply the requirement directly to the XPC connection, as explained in this forums post. With that in mind, it’s a question of crafting the right requirement. There are two parts to this: Identifying your clients Identifying your code loaded into system clients Identifying your clients should be straightforward. You start with the DR of those clients and then adjust the Boolean logic to suit your specific needs. It’s not possible to identify your code loaded into system clients, so the best you can do is identify those systems clients themselves. And there’s no good way to do that: You could use the client’s designated requirement (DR), but that might break if the system changes the context in which it loads your authorisation plug-ins (as has happened in the past). You could use a much broader requirement, like anch

On my macOS 15.7.4 machine: $ pkgutil --pkg-info-plist com.apple.pkg.MobileDevice groups com.apple.findsystemfiles install-location Library/Apple/ install-time 1771452321 pkg-version 4.0.0.0.1.1762585687 pkgid com.apple.pkg.MobileDevice receipt-plist-version 1 volume /

[quote='881100022, nathan-pierce-veertu, /thread/819456?answerId=881100022#881100022, /profile/nathan-pierce-veertu'] FB22313446 [/quote] Thanks. I’ve been discussing this with the Virtualization team and I think I know what’s going on here. But, just to confirm, on a Mac that’s showing this problem, what does this command report: % pkgutil --pkg-info-plist com.apple.pkg.MobileDevice … … pkg-version 4.0.0.0.1.1772003596 … Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Strange: In my test application I removed Apple Sandbox and now it works here. Using the same settings it does not work in my real app. I guess there is a wrong Xcode setting for my target. Need to investigate…

Really nobody knows where the Apple documentation is regarding the meaning of the Yellow DOT ? On [medium] I found an article , someone said what the yellow red and blue circles mean, but there is no source from apple docummentations .. also I don't know why apple banned medium.com , this forum didn't let me post the link to that article. This docummentation is incomplete, it does not say what YELLOW / RED / BLUE circle means: https://support.apple.com/guide/iphone/learn-the-meaning-of-iphone-status-icons-iphef7bb57dc/ios PS. The article mentioned that the Yellow circle means the app was installed trough Test Flight

We are facing the exact same limitation on our side, and not only with CoreLocation but also with background (silent) push notifications. With a scene-based app, launchOptions is always nil, and while UIScene.ConnectionOptions is supposed to be the replacement, it does not cover all cases. As mentioned by Apple, “not every launch option will have an equivalent connection option” — and background push notifications seem to be one of those missing cases. In practice, when the app is woken up by a silent push (content-available), there is no reliable way to distinguish this scenario from a normal launch using connectionOptions. This makes it impossible to prevent unintended UI initialization or to branch logic correctly at startup. Relying on delegate callbacks (like didReceiveRemoteNotification) helps once the app is already running, but it does not solve the initial launch ambiguity — especially when the app is relaunched in the background. So overall, we fully agree with the original concern: there i

So, the standard term for this is network interfaces. macOS supports a wide array of network interfaces. I have lots of background to this in the various posts referenced by Extra-ordinary Networking. [quote='820120021, happyanimal55, /thread/820120, /profile/happyanimal55'] I'd like to permanently delete them [/quote] Don’t attempt to do that. Some of these interfaces are used for stuff that’s vital to the internal operation of macOS, for example, communication between the main CPU and various co-processors. My general advice is that you adjust your workflows so that these don’t get in the way. If you’re writing code, the suggestions in Extra-ordinary Networking should help. If not, I’ve found this command to be super helpful: % networksetup -listallhardwareports … Hardware Port: Wi-Fi Device: en0 Ethernet Address: … … It gives you the BSD name of each user-visible interface, which you can then use with commands like ifconfig. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple

[quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] I've had issues getting the dmg signed by the Apple notary service [/quote] That text suggests that you’ve misunderstood how notary works. The notary service doesn’t sign your product. Rather, you present it with a distribution-ready product, one that’s already signed, and the notary service checks it and, if all is well, issues a signed ticket. See Notarisation Fundamentals for more about how this process works. As to why the notary service is refusing to notarise your product, it’s hard to say without more info. It sounds like you were able to submit the product and get a response, but the status is Invalid, indicating a problem with your submission. In that case the next step is to look at the notary log. What does it say? See Fetching the Notary Log for info on how to get the log. [quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] The only big change we made this time was switching to Maven [/quote] Ah, Jav