“Apple Maps Guides”

[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

All of the APFS locks tend to be held for very short periods of time, so it's not unusual for work to pile up very quickly. More to the point, all of those other threads are (mostly) irrelevant to the issue. I'd actually be looking for any other reference to compression/decompression or xattrs. If they are held for a very short amount of time, shouldn't we rarely see other threads waiting for it ? It's what I would expect, at least. And here we can see that all other threads are waiting for it for the whole spindump duration (Num samples: 940 (1-940) / IORWLockWrite & IORWLockRead → 940). I mean, I know this count the number of times the sampler see these symbols each time it samples the processes (i.e. it doesn't mean this code was running between each sample), but I would be surprised that these exact same stacks is re-happening exactly at the same time as the samples are done by chances: they are likely running for the whole time. Yes, you do. It's defined in IOLocks.h, which maps it to lck_rw

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

[quote='820080021, nixx, /thread/820080, /profile/nixx'] I have submitted this via Feedback Assistant (FB22312299). [/quote] Thanks. I’m not sure what’s going on here, but it’s clearly a regression and thus warrants a bug report. Having said that, there’s a long-standing gotcha you need took out for. Using non-ASCII names for pure data should be fine, but you have to be careful when using non-ASCII names for files within a code-signed bundle. There’s a long-standing problem with that, as explained in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to be clear about terminology here: A load-time import is one that’s statically declared in the binary via the LC_LOAD_DYLIB load command. A run-time import is one that you do from code, using dlopen or some API layered on top of that. Beyond that, I’m going to use the terms from an An Apple Library Primer, and you should read before continuing. [quote='820251021, vd02, /thread/820251, /profile/vd02'] What is the recommended approach on macOS for this kind of explicit dynamic loading … ? [/quote] My recommendation is that you not do this. Apple platforms generally prefer load-time imports because it enables optimisations in the dynamic linker. Specifically, the dynamic linker can build and cache a closure for an app, reusing that closure the next time the app launches. Note We discussed this in detail in WWDC 2017 Session 413 App Startup Time: Past, Present, and Future. Sadly, it’s no longer available from Apple, but the core info is still available from third-party sources.

For 2 years our app was reviewed under 2 days. This time after a week we asked an urgent review because it contained important fixes. The worst part is that Apple is also blocking our work in Testflight. even after a week it is still under review. I submitted a new build and asked to review that one instead. Still nothing after two days. To me it seems Apple is having internal issues and we are powerless and can't work properly with our Testers.