Search results for

Apple Maps Guides

151,865 results found

Post

Replies

Boosts

Views

Activity

Reply to KeyChain Sharing with App Extensions
[quote='868260022, Infibrite, /thread/809012?answerId=868260022#868260022, /profile/Infibrite'] our earlier “Network Extension” tag was a mistake. [/quote] And presumably so was the reply you posted about 10 hours before this one |-: Anyway, the behaviour you’ve described doesn’t gel with Network Extension at all, so I’ve re-tagged your thread accordingly. When dealing with keychain sharing, there are two factors in play: Build time Run time I’m gonna focus on the build-time stuff, because a) that’s where you seem to be stuck, and b) I’m not familiar with Matter extensions and there could be run-time restrictions I’m not familiar with. So, regarding your build, you wrote: [quote='868260022, Infibrite, /thread/809012?answerId=868260022#868260022, /profile/Infibrite'] Could you enable Keychain Sharing for these iOS App IDs … ? [/quote] There’s nothing for us to enable here. Every App ID supports keychain sharing [1]. To illustrate this: I using Xcode 26.1 to create a new test project from the iOS > App templ
2w
Reply to Filter Packet Provider Cpu issue
None of this strikes me as particularly surprising. The packet path is extremely ‘hot’, so adding any work to it is costly. The best thing you can do to improve performance is to avoid the .delay verdict, but your test code is already doing that. Before I send you off to file a bug about this, I have a couple of things for you to check: Make sure you reproduce this on a ‘clean’ machine. I often see weird problems being reported by folks only for us to track it down to some enterprise security setup affecting their main work Mac. If you have any additional network debug logging enabled — see the various instructions on our Bug Reporting > Profiles and Logs page — make sure to disable that during your tests. Usually I test NE stuff on a VM, but in this case you’ll want to run your tests on real hardware. VMs are great, but one place where they differ from real machines is performance. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Reply to System Information in macOS 26.2 RC no longer shows Wi-Fi SSIDs
[quote='809205021, vtsang2025, /thread/809205, /profile/vtsang2025'] Is it an expected behaviour or a bug in the Release Candidate? [/quote] I don’t think that actually matters, in that it’s still fundamentally the wrong behaviour )-: Please do file a bug about this. I’d appreciate you posting your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Reply to Feature Request: Reason for taskExpiration for BGContinuedProcessingTask
[quote='809183021, kaloramik, /thread/809183, /profile/kaloramik'] My feature request is [/quote] The best way to get this suggestion to the folks who can act on it is to put it in an enhancement request. 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
2w
Reply to Local Network Discovery Works in Debug but Not in TestFlight (Wi-Fi Speaker Connection Issue)
[quote='809030021, pankaja, /thread/809030, /profile/pankaja'] This makes me believe something related to local network access … is not being applied correctly in the release/TestFlight environment. [/quote] That’s not impossible, but my experience is that it’s not common. Rather, most folks who see problems like this actually have a Release build issue. I recommend that you check this by following the process in Isolating Code Signing Problems from Build Problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Local Network Discovery Works in Debug but Not in TestFlight (Wi-Fi Speaker Connection Issue)
Hi team, I’m having an issue with my iOS app related to local network communication and connecting to a Wi-Fi speaker. My app works similar to the “4Stream” application. The speaker and the mobile device must be on the same Wi-Fi network so the app can discover and connect to the speaker. What’s happening: When I run the app directly from Xcode in debug mode, everything works perfectly. The speaker gets discovered. The speaker gets connected successfully. The connection flow completes without any problem. But when I upload the same build to TestFlight, the behaviour changes completely. The app gets stuck on the “Connecting…” screen. The speaker is not discovered. But the same code is working fine on Android It never moves forward from that state. So basically: Debug Mode: Speaker is detected and connected properly TestFlight: Stuck at “Connecting…”, speaker does NOT get connected This makes me believe something related to local network access, multicast, Wi-Fi info permissions, or Bonjour discovery is not bei
1
0
139
2w
Reply to KeyChain Error
Are you doing this from Keychain Access? If so, make sure you have the My Certificates tab selected at the top. That shows you the digital identities in your keychain, where each digital identity is the combination of a certificate and a private key that matches the public key in the certificate. If the digital identity is listed there, you should be able to export it as a .p12, which contains both items. OTOH, if that doesn’t list your digital identity then something else is wrong. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: General
2w
Can't renew, can't update contact info
I originally created my Apple Developer account when I was living in Canada (years ago). Now that I live in the U.S. I want to renew it, but I can't - because it thinks I'm still in Canada. When I go to change my contact information, I get a screen that says: Unauthorized Your account can’t access this page. There may be certain requirements to view this content. If you’re a member of a developer program, make sure your Account Holder has agreed the latest license agreement. What do I do?
2
0
664
2w
Reply to App Sandbox denies mach-register for Developer ID signed app but allows it for Apple Distribution signed app
Thank you, Quinn. Your suggestion about using app group IDs worked. After investigation, I found that adding my Team ID-prefixed app group (XXXXXXXXXX.com.mycompany.myapp) to com.apple.security.application-groups in my entitlements resolves both mach-register and mach-lookup without needing any temporary exceptions. Looking at /System/Library/Sandbox/Profiles/application.sb, I can see why this works: (sandbox-array-entitlement com.apple.security.application-groups (lambda (suite) ... (allow mach-lookup mach-register (global-name-prefix (string-append suite .))) ...)) With XXXXXXXXXX.com.mycompany.myapp as the app group, the sandbox allows any Mach service name starting with XXXXXXXXXX.com.mycompany.myapp., which matches Chromium's naming pattern: XXXXXXXXXX.com.mycompany.myapp.MachPortRendezvousServer.. My Developer ID provisioning profile already included XXXXXXXXXX.* in its application-groups, which authorizes any Team ID-prefixed app group. I just needed to explicitly claim it in my entitlements. For Elect
Topic: App & System Services SubTopic: General Tags:
2w
App Sandbox denies mach-register for Developer ID signed app but allows it for Apple Distribution signed app
I'm working on a multi-process macOS application (based on Chromium/Electron) that uses Mach ports for inter-process communication between the main app and its helper processes. Background I have an MAS build working successfully via TestFlight for internal testing. However, public TestFlight testing requires Apple review, and while waiting for that review, I wanted to provide a directly distributable build for external testers. I attempted to create a Developer ID signed build with App Sandbox enabled, expecting it to behave similarly to the MAS build. The Problem With App Sandbox enabled (com.apple.security.app-sandbox) and identical entitlements, I observe different behavior depending on the signing certificate: Apple Distribution certificate: App launches successfully, mach-register and mach-lookup work Developer ID certificate: App crashes at launch, mach-register is denied by sandbox The Console shows this sandbox violation for the Developer ID build: Sandbox: MyApp(13605) deny(1) mach
2
0
118
2w
Payments paused
I got this email from Apple Due to the discontinuation of content associated with your vendor number x, your payments have been paused. We will continue to monitor this account and release your payments once customer refunds have been settled. Does anyone know what happened? I didn't discontinue any content.
1
0
255
2w