Search results for

Apple Maps Guides

154,053 results found

Post

Replies

Boosts

Views

Activity

How can I obtain the documentation for the specific implementation of WAC?
Hi everyone, We are currently exploring ways to implement a frictionless Wi-Fi setup for our hardware devices without requiring a dedicated third-party application. We are interested in leveraging Apple's WAC (Wireless Accessory Configuration) to sync Wi-Fi credentials directly from iOS devices. However, we have struggled to find comprehensive technical documentation or specifications regarding the WAC service. Could anyone point us to the official source for these materials? Additionally, we have a couple of technical questions: 1.We are testing WAC provisioning and found that the Home app can discover our device and successfully get it online. However, it always ends with a Failed to add accessory message. Does WAC support imply that a device should be addable via the Home app? If not, why is the Home app able to discover and start the setup for a non-HomeKit WAC device? 2. Our device is already Apple AirPlay certified. Does implementing WAC require additional standalone certification, or
1
0
39
1w
Swiftui Map Leagal Text is transformed when rotationEffect is applied to Map
I have a problem when applying rotationEffect to a map in in SwiftUI. The legal text in the map is transformed as shown in this image: The following code is part of a much larger and complex view; it is a minimal example to reproduce the error: import SwiftUI import MapKit struct ContentView: View { @State private var offset = CGSize.zero var body: some View { ZStack { let drag = DragGesture() .onChanged { g in offset.width = g.translation.width offset.height = g.translation.height } Map(interactionModes: [.zoom]) .frame(width: 320, height: 220) .rotationEffect(.degrees(Double(offset.width / 12))) .highPriorityGesture(drag) } } } I hope you can help me with this problem.
1
0
40
1w
Approved app stuck in “Ready for Distribution” — release controls disabled
My iOS app has passed App Review and is marked “Ready for Distribution,” but App Store Connect does not allow me to release it because the App Store Version Release controls are disabled. App Review is closed and the Resolution Center is unavailable. I have submitted multiple Apple Developer Support cases and called phone support, but the issue remains unresolved. This appears to be an App Store Connect backend state issue affecting a first-time app with subscriptions. Can Apple engineering assist in unlocking release permissions for iOS version 1.0?
1
0
100
1w
The Nightmare of Small Toolbar Icons
When building in Xcode on MacOS Tahoe, it seems it is no longer possible to dynamically specify a small size toolbar for NSToolbar/NSToolbarItem. It works in MacOS code compiled and linked on earlier systems. I don't want to use SFSymbol, or templates. I have over 60 custom-made .png toolbars, in individual Image Set files, at the previous requisite sizes of 24x24 / 48x48, and 32x32 / 64x64. Sure -- I can configure an NSToolbar with whatever size .png assets I want. I just can't dynamically switch between the two groups of sizes. According to the Apple Coding Assistant, the only solution is to change the image names of each of the NSToolbarItems at runtime. OK -- but even when attempting that, the NSToolbarItems refuse to take on their smaller size... ...unless: they are attached to a custom view NSToolbarItem with an NSButton of style Bevel. I have about 10 of those, and YES -- I CAN change those to a small size. Is this REALLY what I'm forced to do?! The Apple Coding Assistant just runs me
1
0
101
1w
Reply to Small Size Icons and NSToolbar on MacOS 12.0 Monterey -- can it work?
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?
Topic: UI Frameworks SubTopic: AppKit Tags:
1w
VideoMaterial Black Screen on Vision Pro Device (Works in Simulator)
VideoMaterial Black Screen on Vision Pro Device (Works in Simulator) App Overview App Name: Extn Browser Bundle ID: ai.extn.browser Purpose: A visionOS web browser that plays 360°/180° VR videos in an immersive sphere environment Development Environment & SDK Versions Component Version Xcode 26.2 Swift 6.2 visionOS Deployment Target 26.2 Swift Concurrency MainActor isolation enabled App is released in the TestFlight. Frameworks Used SwiftUI - UI framework RealityKit - 3D rendering, MeshResource, ModelEntity, VideoMaterial AVFoundation - AVPlayer, AVAudioSession WebKit - WKWebView for browser functionality Network - NWListener for local proxy server Sphere Video Mechanism The app creates an immersive 360° video experience using the following approach: // 1. Create sphere mesh (10 meter radius for immersive viewing) let mesh = MeshResource.generateSphere(radius: 10.0) // 2. Create initial transparent material var material = UnlitMaterial() material.color = .init(tint: .clear) // 3. Create entity and invert
0
0
157
1w
Will resubmitting my app send it to the back of the line?
Hi everyone - My first iOS app submission has been in Waiting for Review since Jan 27 (we actually submitted Jan 23, saw no movement, and resubmitted with a small update), and Apple Support has not responded to my outreach. Since Jan 27, our team has implemented a handful of app updates from our roadmap and plans to submit the updated version of the app once the first submission is approved. However, we're at a crossroads: Do we wait for the first submission (currently 14 days and counting) and submit the updated version once (hopefully) approved, rolling the dice that an update to an existing app would see a faster 2-3 day turnaround? Cancel our current version and resubmit the updated one, with the risk that we're just moving ourselves to the back of the queue and get stuck in another 15-20 day Waiting for Review status? Any devs with insight or experience navigating these choices, any suggestions would be greatly appreciated.
2
0
153
1w
Reply to Biometrics prompt + private key access race condition on since iOS 26.1
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
Topic: Privacy & Security SubTopic: General Tags:
1w