Any logical reason why applying .sharedBackgroundVisibility(.hidden) to a ToolbarItem would not remove the spacing allocated for glass border? Thus causing any element utilizing this functionality to appear offset from the regular buttons. Or is this yet another magical Apple experience I am not blessed enough to understand.
Search results for
Apple Maps Guides
154,002 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello. I want to log in to my account on Xcode. It tells me there is an error in my Apple account or password. There is no problem with the password or account. I contacted support and they couldn't solve the problem. What should I do?
Hello @Omar_luay These forums are for code-level support. This question is better suited for the Apple Support Communities https://discussions.apple.com/welcome I would recommend to post it there instead of the developer forums. One tip I have is to confirm you are typing the exact same credentials you use to log into https://developer.apple.com/account/ Travis Trotto - DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Solved the problem myself. The key is to not set a colorspace. This allows ScreenCaptureKit to return raw values, including values > 1.0. It would be nice if Apple's documentation included more semantics, i.e. more description of the functionality (not just syntax) of their APIs.
Topic:
Media Technologies
SubTopic:
General
Tags:
With the help of Claude and Codex, I've tried upgrading a screen magnification, capture, and pixel peeping app (SnoopX, from Stanford's software repository) to be HDR-aware. For images that are truly HDR (displayed in Apple Photos, Google Photos in Chrome, or Mac Preview), and on an HDR monitor with plenty of EDR headroom (Apple XDR display), I should see pixel values well above 1.0. Apple's Digital Color Meter does. However, my app does not. I think the code is doing all the right things with ScreenCaptureKit, but it never returns values above 1.0. Has anybody gotten this to work? Here is what Codex says about the code it helped me build in my app: • Set captureDynamicRange: We set config.captureDynamicRange = SCCaptureDynamicRangeHDRLocalDisplay (when available). Note: Gemini’s SCCaptureModeHDRLocalDisplay isn’t a real symbol — the actual API is SCCaptureDynamicRange. • Use preset: We try initWithPreset: SCStreamConfigurationPresetCaptureHDRStreamLocalDisplay, but your runtime cra
Thanks for the post and for your patience, that team does not monitor the forums very often and full disclaimer I’m not part of that team, I just look at the requirements from https://developer.apple.com/swift-student-challenge/policy/ and it seems like you are not a full time employee at this time and you are enrolled at school at this time? Fulfill one of the following requirements at the time of submission: * Be enrolled in, or have graduated within the last 90 days from, an accredited academic institution or official homeschool equivalent, or an Apple Developer Academy; * Be enrolled in a STEM organization’s educational curriculum; or * Have graduated from high school or equivalent within the past 6 months and be awaiting acceptance or have received acceptance to an accredited academic institution. On the page there is an email for the team, you should send them an email if you still have questions about requirements. Albert Pascual
Worldwide Developer Relations.
Topic:
Community
SubTopic:
Swift Student Challenge
Tags:
@Khanaphot Thanks for the post. These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome I would contact customer support or take the device to a store if any is near to you. Hope this helps. Albert Pascual
Worldwide Developer Relations.
Topic:
Community
SubTopic:
Apple Developers
Hello, I need help with iCloud Activation Lock on my device. Device: iPhone 16 Pro 256GB Serial Number: HCJD73C0MJ IMEI: 350766435041555 / 350766435124831 I cannot access the original Apple ID, so the device is stuck on Activation Lock. I am the legitimate owner and I have proof of purchase and ID for verification. Please advise on the proper steps to resolve this issue. Thank you.
Topic:
Community
SubTopic:
Apple Developers
Hello. I just got my developer account and my legal entity on my account has a mistake. My last name is spelled wrong. I have sent 3 emails to support about this and for the past week i have zero response to this issue. Can someone advise me on this? The ability to reach anybody from support is ridiculous for something that we can access only after payment especially. I even called apple business program with this and person on the phone said they will try to take to the supervisor but its not their department which i of course know but it was worth a shot to call. What more can i do? I didnt make a mistake when creating my account it was the system that didn’t recognize the letter. Such a stupid and frustrating issue and no response from apple, nada. how long am i suppose to wait?
Topic:
Community
SubTopic:
Apple Developers
We have been using this API call to set the In-App Provisioning capability for 2+ years and it just recently started returning errors. To set the In-App Provisioning capability we had been using the App Store Connect API directly: curl https://api.appstoreconnect.apple.com/v1/bundleIdCapabilities -X POST --header Authorization: Bearer #{appleApiToken} --header Content-Type: application/json -d '{data: {type: bundleIdCapabilities, attributes: {capabilityType: IN_APP_PASS_PROVISIONING}, relationships: {bundleId: {data: {id: #{appStoreBundleIdentifier}, type: bundleIds}}}}}' The IN_APP_PASS_PROVISIONING capability type is shown, by getting the bundle ID capabilities, when In-App Provisioning is set on a bundle ID: curl https://api.appstoreconnect.apple.com/v1/bundleIds/#{appStoreBundleIdentifier}/bundleIdCapabilities --header Authorization: Bearer #{appleApiToken} After manually setting the In-App Provisioning capability via the Apple Developer portal you will see the new capabilityType: { type : bundl
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect API
On our public Apple account we have distribution certificates that work for all Apple platforms. On our Enterprise account it will only generate iOS distribution certificates. Apple support did not provide any concrete solutions, only pointing us to the general docs. Any suggestions?
Sorry I mised your earlier response. 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. This suggests that while UDP packets reach the device, delivery to the process is suspended in background, which explains why the DTLS handshake cannot progress. Indeed. This is pretty fundamental to how iOS works. If your app moves to the background, iOS suspends it. It then can’t do anything until it gets resumed. It’ll be resumed when your app moves to the foreground. It can also be resumed in the background under specific criteria. However, traffic on a UDP socket is not one of those criteria. I talk more about this in iOS Background Execution Limits. Traditionally, VoIP apps use two different techniques for these two scenarios: For ring indication, they use one of the technologies that Kevin described above (VoIP push or Local push connectivity). For the actual conversation, they prevent the app from suspending by virtue of their active audio se
Topic:
App & System Services
SubTopic:
Networking
Tags:
Hello, We are facing an issue with performing a DTLS handshake when our iOS application is in the background. Our app (Vocera Collaboration Suite – VCS) uses secure DTLS-encrypted communication for incoming VoIP calls. Problem Summary: When the app is in the background and a VoIP PushKit notification arrives, we attempt to establish a DTLS handshake over our existing socket. However, the handshake consistently fails unless the app is already in the foreground. Once the app is foregrounded, the same DTLS handshake logic succeeds immediately. Key Questions: Is performing a DTLS handshake while the app is in the background technically supported by iOS? Or is this an OS-level limitation by design? If not supported, what is the Apple-recommended alternative to establish secure DTLS communication for VoIP flows without bringing the app to the foreground? Any guidance or clarification from Apple engineers or anyone who has solved a similar problem would be greatly appreciated. Thank you.
I’ve been waiting since January 31. I submitted several support tickets and made a few calls to Apple Support, but no response from the App Review team.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Hi everyone, I’m implementing subscriptions using StoreKit v2, and I’ve noticed a behavior change starting with iOS 26.1. I’d like to ask if anyone else has experienced the same issue. ■ Issue Immediately after purchasing a new subscription, the value of auto_renew_status (or autoRenewStatus) returned in the receipt is 0 (auto-renew OFF). This issue occurs on iOS 26.1. On iOS 26.0 and earlier, the same parameter returned 1 (auto-renew ON) right after purchase. Sometimes, after executing a “restore” operation, the value changes to 1 later. Since we’ve been using this parameter to determine whether a user’s subscription is active or not, the current behavior is causing some difficulties on our end. ■ Questions Has anyone else observed this issue (where autoRenewStatus is 0 immediately after purchase on iOS 26.1 or later)? How are you handling or working around this behavior in your implementation? If autoRenewStatus is unreliable, we’re considering determining the subscription state based on receipt fields inst