Post not yet marked as solved
The com.apple.rpmuxd job is not part of the base system, because it needs to be separately updated. Consider: % sudo launchctl print system/com.apple.rpmuxd system/com.apple.rpmuxd = { active count = 0 path = /Library/Apple/System/Library/LaunchDaemons/com.apple.rpmuxd.plist … Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
Yeah, I think you should file a bug about this. Make sure to include a sysdiagnose log taken while the CPU is pinned. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
Problems like this are almost always related to optimisation. Consider code like this: 1 import Network 2 3 func main() { 4 let connection = NWConnection(host: example.com, port: 80, using: .tcp) 5 // … set up state handler and so on … 6 connection.start(queue: .main) 7 dispatchMain() 8 } 9 10 main() This is likely to work in your Debug build but it’s possible that it might fail in your Release build. That’s because the last reference to connection is on line 6, so the optimiser might release that reference before the call to dispatchMain(). If it does, and nothing else is holding a reference, the underlying object will be deallocated and that’ll cancel the connection. While this is a trivial example, and unlikely to crop up in anything except a test project, I’ve seen this sort of problem show up numerous times in real apps. One good way to track this down is to put log point in your deinitialisers for your networking classes. If those log points fire unexpectedly, you know where to start. Share and Enjoy —
Post not yet marked as solved
These days my go-to API for asynchronous DNS resolution is DNSServiceGetAddrInfo. The DNS-SD API is a bit tricky to call from high-level languages. If you’re using Objective-C, check out the DNSSDObjects sample code. If you’re using Swift, see this post. Neither of these call DNSServiceGetAddrInfo, but they show how to use DNS-SD in general. Oh, and I can’t talk about DNS without my standard warning: If your ultimate goal is to connect to this address, you’re much better off using a connect-by-name API. TN3151 Choosing the right networking API talk about this in some detail. OTOH, these APIs are fine if you’re not actually connecting, for example, you’re building a DNS debugging tool. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
I am passing the return value of TISGetInputSourceProperty after static casting it to CFDataRef to the CFDataGetBytePtr function. That is a ‘selector based’ API, that is, the result you get back depends on the selector (propertyKey) you pass in. What key are you using? As an aside, if you want to trap problems like this early, check the type at runtime using CFGetTypeID: let tis: TISInputSource = … let someProperty: CFString = ; guard let raw = TISGetInputSourceProperty(tis, someProperty) else { … } let data = Unmanaged.fromOpaque(raw).takeUnretainedValue() assert( CFGetTypeID(data) == CFDataGetTypeID() ) … Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
Any chance you could push to get the x-apple.systempreferences URL scheme properly documented? The best first step here is for you to file a bug against the docs. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
What could be the best approach to do this? I don’t see any way to do that programmatically because… The app will mostly be in a closed state. For this to work the system would have to resume (or relaunch) your app in the background every time the device is unlocked, and there’s no facility to do that. The only other way to achieve this would be for the system to main these metrics for you, and give you access to them via some API. Again, there’s no API for that. Are you targeting a managed environment? Or do you expect to ship this on the App Store for general users? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
I have a bunch of links and other info about the system log facility in Your Friend the System Log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Post not yet marked as solved
Same here, Apple still hasn't fix their bug about auto renewal check. Very annoying, have to manually upload file and verify again. We're using Cloudflare to auto renew certificate (90 days validity period), and the certificate we are using is Google Trust Services.
Post not yet marked as solved
Same here, we use Cloudflare to automatically renew the SSL certificate: Universal certificates issued by Let’s Encrypt or Google Trust Services have a 90 day validity period. Cloudflare tries to renew the certificate since 30 days before expiration. I also read the document and thought that after we updated the SSL certificate, Apple detects the renewed certificate and the domain remains verified, and extend the expiration check according to the renewed certificate. But that did not happen, here is an example: SSL certificate expiration date: 5/15 4/17: Receive first warning email (i.e. 30 days before expiration) 4/17: Cloudflare renews the certificate, not sure before or after Apple's check 5/2: Receive second warning email (i.e. 15 days before expiration) We have to manually update the apple-developer-merchantid-domain-association.txt and verify again.
Post not yet marked as solved
Same warning here with MapKit. Thread Performance Checker: Thread running at User-interactive quality-of-service class waiting on a thread without a QoS class specified (base priority 0). Investigate ways to avoid priority inversions PID: 77670, TID: 5270783 Backtrace ================================================================= 3 VectorKit 0x0000000193fef1a4 ___ZN3geo9TaskQueue5applyEmNSt3__18functionIFvmEEE_block_invoke + 40 4 libdispatch.dylib 0x00000001033e9778 _dispatch_client_callout2 + 16 5 libdispatch.dylib 0x000000010340066c _dispatch_apply_invoke3 + 400 6 libdispatch.dylib 0x00000001033e973c _dispatch_client_callout + 16 7 libdispatch.dylib 0x00000001033eb210 _dispatch_once_callout + 84 8 libdispatch.dylib 0x00000001033ff898 _dispatch_apply_redirect_invoke + 232 9 libdispatch.dylib 0x00000001033e973c _dispatch_client_callout + 16 10 libdispatch.dylib 0x00000001033fd5a4 _dispatch_root_queue_drain + 940 11 libdispatch.dylib 0x00000001033fdf18 _dispatch_worker_thread2 + 256 12 libsystem_pthread.dyl
Post not yet marked as solved
Have you taken a look at https://developer.apple.com/documentation/technotes/tn3155-debugging-universal-links? If you're still stuck, can you provide me with either your domain name, app name, or App ID if you're comfortable doing so? I've seen issues with Flutter's deep linking in the past, but I can at least look into the Apple side.
Post not yet marked as solved
This whole discussion assumes that every network connection requires a socket. This isn’t the case on most Apple platforms, which have a user-space networking stack that you can access via the Network framework [1]. [1] The one exception here is macOS, where Network framework has to run through the kernel in order to support NKEs. This is one of the reasons we’re in the process of phasing out NKE support, starting with their deprecation in the macOS 10.15 SDK. Hi Quinn, it's been a while since you wrote the above. Do you know if macOS is still an unfortunate exception that requires a socket per Network framework's connection? cc @eskimo
Post not yet marked as solved
Hello everyone, few months ago I submitted my new app for review, but got automated message back: We need additional time to evaluate your submission and Apple Developer Program account. Your submission status will appear as Rejected in App Store Connect while we investigate. However, we do not require a revised binary or additional information from you at this time. thought it won't take long (I was wrong) , I waited for a whole month and nothing, then I started researching and some other devs suggested to cancel that submition and resubmit , and I did just that , same thing happened this time , almost 3 weeks that i've been waiting , if any one from apple sees this please help me :(
Post not yet marked as solved
You can either force quit Xcode and relaunch it or wait for it to time out. This issue needs to be addressed by Apple to allow users to cancel the operation, as it can be frustrating when Xcode automatically selects a previous device without notice, causing the intended testing device to be overlooked.
