“Apple Maps Guides”

Here's the video I initially shared with them. It's recorded via Apple Watch > iPhone screen sharing. And they believe this is a simulator, lol https://youtu.be/izXpnEZCCp4

My Mac Mini crashed and restarted, and the SDKs are all broken again. I am going to have to spend another hour with SIP etc to get this working. Can Apple acknowledge this is a real issue they are working on resolving please? It's an intolerable situation.

antho2305, I discussed your case with the notary team and the conclusion is that: While there were some transient issues caused by oddities at our end… This all falls into the category of the notary service ‘learning’ how to recognise your submissions. Your submissions should be flowing normally now, but if you continue to have problems please reply here with the details and I can take another look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

@Tomato, I should mention that I already provided them a video, voluntarily, showing my app on my watch via screen sharing. So the fact they demand more is a sign of a shark strategy. They feel my desire to comply (blood) and attack with endless requirements. If I agree they'd demand another video with different equipment, and so on and so forth. Another problem is fully practical. The video requires Apple Watch + equipment (e.g. Mac Book) + camera. I simply can't do it in a good enough quality with my two hands. I need to hire a professional for that which is hard for an Individual Developer. Much easier would be reject and reapply hoping for a different reviewer. And finally I would note that I have competitors who perform worse than HeartBLE and I doubt any of them was forced to make a video. The real problem which blows their mind is the monetization. I selected the XX-day Trial + non-consumable model. Just wanted to give it a try, get some experience. Turns out reviewers hate it (or simply not f

[quote='884303022, ParinK124, /thread/822456?answerId=884303022#884303022, /profile/ParinK124'] it is a bit slow. [/quote] Which bit? The Swift Playground app? Or your code running within the Swift Playground app? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are you talking about auto login on the guest? Or the host? Are you trying these operations from a GUI login session? Or doing something outside of a GUI login session, for example, from a launchd daemon? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='822658021, rbmanian75, /thread/822658, /profile/rbmanian75'] Is there anything i am doing wrong? [/quote] It’s hard to say without more context. Specifically: What network have you assigned to the interface? Has the guest successfully acquired an IP address? Does that IP address match the IP address you’re passing in here (ipAddr)? What value as you using for guestPort? Are you sure that the guest is listening on the port? If you run a command on the guest to connect to it’s IP address and port (so ipAddr and guestPort), does that go through? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='884242022, rbmanian75, /thread/822025?answerId=884242022#884242022, /profile/rbmanian75'] But i dont want to have a different subnet for each vm. [/quote] Why is that? Are you expecting the VMs to communicate with each other? Or is there some other reason? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='884233022, DTS Engineer, /thread/821961?answerId=884233022#884233022'] I’m talking with the right folks about this [/quote] I now have specific advice for folks in this situation: Please re-apply for the Contactless Pass Provisioning capability. The approval folks will then assign you the Contactless Pass Provisioning (deprecated) capability, which you can use right now. Once this Xcode issue is resolved (FB22439399), they will assign you the newer Contactless Pass Provisioning (SharableCredential) to use going forward. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='884266022, oleksandr91, /thread/821894?answerId=884266022#884266022, /profile/oleksandr91'] Does it mean that Keychain Access is using some other private API that we are not allowed to use? [/quote] Private APIs aren’t thing. Rather, there are APIs and there are implementation details (-: Keychain Access is built in to the system, so it isn’t restricted to APIs. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='884334022, iceboy, /thread/822626?answerId=884334022#884334022, /profile/iceboy'] I am using the iOS platform. [/quote] Cool. iOS only has one keychain implementation, equivalent to the data protection keychain on macOS, and that simplifies your life. [quote='884334022, iceboy, /thread/822626?answerId=884334022#884334022, /profile/iceboy'] I did not set kSecAttrAccount and kSecAttrAccessible when saving data on older iOS versions. [/quote] kSecAttrAccessible is unlikely to be the problem: Your current code leaves out that attribute from the query and return dictionary you pass to SecItemCopyMatching. In that context a missing attribute is treated as wildcard, so it’ll make any item regardless of what it’s kSecAttrAccessible value is. If the value is not present in the add dictionary you pass to SecItemAdd, the system will default to using no value for kSecAttrAccessible and, assuming there’s no kSecAttrAccessGroup attribute, it’ll place the item in your app’s default keychain access group. Sharing acc