Apple Maps Guides

I, too, have gone through a nightmare with small size toolbar icons on MacOS Tahoe. Every attempt I've made to programmatically swap out toolbar sizes has failed for NSToolbarItem -- unless it has an NSButton (bevel style) as a custom view. Apple's Coding Assistant has taken me down multiple blind alleys. Can't I just have multiple toolbars, including a small size toolbar where I can switch to it by hiding the full-size toolbar?

Apple don't need money, they have enough money lol

Hello, i got the same thing, apple don't want to activate any account or what ??? i'm waiting for 2 week, Google as validated my account in 1 day !!! are you serious Apple ??? Answer to my question support !

I enrolled two days ago. I haven't got any email from Apple till now regarding my membership. It's showing pending in account details. Any idea on how long it might take as I have a time line to meet.

Same issue here... wish someone from Apple would comment...

In the end, I've decided to remove the blue dot on the map since the application doesn't necessarily need it. Therefore, the application doesn't need Location Services any more. I'm going to move on with my life, forgetting about the blue dot. What a big deal...

Well, that’s not good. I suggest you retry this on the current 26.3 beta, just in case. Assuming the problem shows up there as well, you should file a bug about it. Make sure to include a sysdiagnose log taken shortly after reproducing the problem, ideally as soon as you see the fuzzy screen you showed in your screenshot. Once you’re done, please post your bug number and I’ll take another look. At the API level, one option you have is to create an LAContext and pass it in to each SecItemCopyMatching call via kSecUseAuthenticationContext. It’s not clear whether you’re doing that or not. Please confirm either way. It’s also not clear if it’s even the right thing to do. This technique makes sense when the user performs a single high-level operation that requires multiple cryptographic operations with the same key. However, if the user performs two separate high-level operations back-to-back and that reproduces this issue, then trying to work around this using kSecUseAuthenticationContext isn’t really the right c

[quote='875615022, daniel-l, /thread/814827?answerId=875615022#875615022, /profile/daniel-l'] Is this a known service-side delay? [/quote] That depends on what you mean by “delay”. I recommend you read my up-thread post that discusses the “in-depth analysis” path. [quote='875615022, daniel-l, /thread/814827?answerId=875615022#875615022, /profile/daniel-l'] should I just wait? [/quote] Yes. If it stays stuck longer than a week, write back here and I’ll dig deeper. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='875490022, digitalbrandingmasters, /thread/815000?answerId=875490022#875490022, /profile/digitalbrandingmasters'] All 6 submissions stuck. [/quote] Yep. That’s typical of what I’ve seen developer report in cases like this. [quote='875490022, digitalbrandingmasters, /thread/815000?answerId=875490022#875490022, /profile/digitalbrandingmasters'] my oldest submission is now over 63 hours stuck In Progress [/quote] Indeed. That’s longer that typical, but certainly not unheard of. If it stays stuck that way for longer than a week, ping me here and I’ll dig deeper. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Doing what you’re suggesting on iOS isn’t really feasible. There are two potential sticking points: Running in the background Inter-process communication (IPC) I talk about the first in general terms in iOS Background Execution Limits. However, in your case this might not be a showstopper because you’re interacting with a Bluetooth LE accessory, and Core Bluetooth does have background execution facilities [1]. The second point is much more problematic. In general, iOS doesn’t allow unmediated IPC between apps from different teams. This isn’t a limitation, but a deliberate design decision based on security and privacy policy. The only path forward I see here is for you to ship an SDK that interacts with the Bluetooth accessory directly, that is, from within the process of the app that adopts the SDK. However, that presents other challenges: Each app will need to request the Bluetooth privilege from the user. You have to find a way to mediate access from multiple apps. You can’t do that on the iOS side because

I have filed FB21917334 Thanks! however not in a Hypervisor Framework category as it does not exist Virtualization is fine. But that’s not a problem; it’ll find its way to the right place. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com