Search results for

apple pencil battery life

146,242 results found

Post

Replies

Boosts

Views

Activity

403 Forbidden error
Hello Apple Developer Support, I am facing an issue when attempting to use the App Store Connect API with my API key. While basic access (e.g., /v1/apps) works correctly, any requests related to Certificates, Identifiers & Profiles (CIP) are failing with a 403 Forbidden error. Here are the details of the request and validation results: JWT Details: { header: { alg: ES256, kid: 2XLW343BLM, typ: JWT }, payload: { iss: 9cf6159c-e038-4703-b542-7652242a6dbf, iat: 1757515277, exp: 1757516357, aud: appstoreconnect-v1 } } Test Results: ✅ /v1/apps?limit=1 → Status: 200 (working) ❌ /v1/bundleIds?limit=1 → Status: 403 Error: Unable to find a team with the given Content Provider ID 9cf6159c-e038-4703-b542-7652242a6dbf to which you belong. ❌ /v1/certificates?limit=1 → Status: 403 Error: This request is forbidden for security reasons. ❌ /v1/profiles?limit=1 → Status: 403 Error: Unable to find a team with the given Content Provider ID. I have already confirmed that: All API keys were generated correctly. All re
13
0
1.3k
2w
Reply to Instructions for debugging recent macos kernel versions?
Hello Kevin, uname -v on my local system shows: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:30 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6020 so I've been using T6020 as the platform when building the kernel. The corresponding xnu source is this tag https://github.com/apple-oss-distributions/xnu/tree/xnu-11417.140.69 and the KDK is KDK_15.6_24G84.kdk. sw_vers shows me: sw_vers ProductName: macOS ProductVersion: 15.6 BuildVersion: 24G84 So I think that's the right KDK version for this system. I'm guessing the XCode version doesn't matter for these experiments (as long as the build succeeds), but for the record, I'm on XCode 16.4: xcodebuild -version Xcode 16.4 Build version 16F6 Apart from the other build instructions, the primary one I use to generate a DEVELOPMENT variant of the kernel is: export KDK=/Library/Developer/KDKs/KDK_15.6_24G84.kdk make SDKROOT=macosx KDKROOT=$KDK BUILD_WERROR=0 BUILD_JSON_COMPILATION_DATABASE=1 TARGET_CONFIGS=DEVELOPMENT ARM64 T6020 and then to generate a (boot
Topic: App & System Services SubTopic: Core OS Tags:
2w
Reply to Safe areas ignored after navigating a WebView/WebPage back in a NavigationStack
Yes, I'm having the same problem (with a wrapped WKWebView, but presumably also the new WebView). The jumping-on-back-button issue was also a problem before iOS 26, but you could work around it by using .ignoresSafeArea(.all, edges: .bottom) However, now in iOS 26, Apple wants the content to flow behind the toolbar, meaning the above fix is no longer suitable. Did you manage to find a workaround?
Topic: Safari & Web SubTopic: General Tags:
2w
Reply to I Need some clarifications about FoundationModels
Happy to help answer some of these! Yes. The Foundation Models framework uses the on-device system foundation model. It's an ~3 billion parameter model designed and trained by Apple. Is the language model provided by FoundationModels designed and trained by Apple? Or is it based on an open‑source model? The exact same on-device model is available on iOS, iPadOS, macOS, and VisionOS on all devices that support Apple Intelligence. Is this on‑device model available on iOS (and iPadOS), or is it limited to macOS? No. The general on-device model you access via Foundation Models is not a coding model and isn't suitable for most code tasks. Xcode on Mac has a separate built-in coding model to help with code completion. When I write code in Xcode, is code completion powered by this same local model? If so, why isn’t the same model available in the left‑hand chat sidebar in Xcode (so that I can use it there instead of relying on ChatGPT)? Yes and no. You can give the on-device model access t
2w
Reply to Supervised devices show wifi setup screen on restart
This behavior still exists in iOS 26.0.1 and iPadOS 26.0.1 even after upgrading the Apple Configurator host to macOS Tahoe 26.0.1. On every restart, Software Update Complete is displayed, along with: Your iPad has been updated to iPadOS 26.0.1. Your iPhone has been updated to iOS 26.0.1. Followed by the Welcome screen with the Get Started button. (Upgrading the Apple Configurator host to macOS Tahoe 26.0.1 did, however, fix the blank Profiles bug in Apple Configurator Version 2.18 10A23.)
2w
Supervised devices show wifi setup screen on restart
When an iOS 26.0 device is prepared in supervised mode, wifi connection screen is showing when the device is restarted. This wifi connect appears always on restart. I have tried using Apple Configurator GUI and Command line (cfgutil) command. In both cases, The behavior Wifi screen is showing up on restart for supervised mode. Cfgutil command: cfgutil -C {Certificate} -K {Key} prepare --supervised --name {NAME} --host-cert {Certificate} --skip-all Note: In non-supervised mode and other iOS, the wifi screen is not showing. Apple Configurator version: 2.18 iOS version: 26.0 Device model: iPhone 11 and above. Anyone else facing this issue? Any help is super appreciated.
1
0
389
2w
MapKit JS Look Around not pointing camera towards the lat/lng entered
We are using MapKit JS Look Around and initializing it like this: window.lookAround = new mapkit.LookAround( document.getElementById('container'), new mapkit.Coordinate(listingLocation[1], listingLocation[0]), {openDialog: false}) ; This results in a Look Around scene being displayed correctly but the camera heading is not pointing towards the lat/lng that is passed to initialization. The example lat/lng that we're using is: lat=30.004195, lng=-95.59973 This lat/lng corresponds to the address: 11943 Laurel Meadow Dr, Tomball, TX 77377. The camera is pointing to the other side of the street to house number 11946. If you look for that address in Apple Maps the Look Around points to the correct house. Is there a way to either specify the heading so that Look Around points in the correct heading? Sample link: https://s.hartech.io/zFP2KnsCbsP
2
0
85
2w
Reply to MapKit JS Look Around not pointing camera towards the lat/lng entered
That sample code doesn't show how to create a place from a lat/lng or lookup a place by address, so I'm not sure if it would help my use-case. Even though lat/lng is a 2D point with no heading information, the point were the camera is vs. the requested point creates a line that the camera should be pointing to. The Apple Maps app does this automatically. We're also using Look Around in our iOS app and the heading is calculated there automatically from the same lat/lng we're providing to MapKit JS. See screenshots below: Native app Look Around MapKit JS Look Around
2w
Incorrect position rendering of WGS84 coordinate in MKMapView: Discrepancy between Apple Maps (Hong Kong) and Amap (Mainland China)
I am encountering a coordinate rendering issue using MKMapView in my iOS app. I have a GPS coordinate in WGS84 format, which corresponds to a location in Hong Kong. When my device is physically located in Hong Kong, MKMapView displays the map with the Apple Maps label, and the WGS84 coordinate is rendered at the correct position. However, when the device is in Mainland China, MKMapView switches to display Amap (Gaode Maps) branding, and the same WGS84 coordinate is rendered at an incorrect position. I understand that Amap in Mainland China uses the GCJ-02 coordinate system, while Apple Maps typically uses WGS84. This discrepancy suggests a potential coordinate system mismatch, but I cannot definitively confirm which map type (and corresponding coordinate system) MKMapView is actually using in different regions. My key questions are: How can I programmatically or visually confirm the underlying map type (Apple Maps vs. Amap) and its coordinate system within MKMapView? Is there a way
4
0
140
2w
Reply to Incorrect position rendering of WGS84 coordinate in MKMapView: Discrepancy between Apple Maps (Hong Kong) and Amap (Mainland China)
First of all, never use comments for replies. Apparently they don't trigger notifications, for people who use them. But they also don't get noticed at all. WGS 84 is a large and complex standard, among many similar large and complex standards designed for dealing with coordinates on the earth. However, because WGS 84 is such a broad standard, it isn't going to have much practical meaning in more specific contexts like a map display. When it does have a specific meaning, it will typically have some kind of qualifier. It is usually better to refer to EPGS identifiers. Apple Maps is a good example. The Apple Maps display uses EPGS:3857, AKA WGS 84 / Pseudo-Mercator. But most government and professional mapping systems like ArcGIS use EPGS:4326, AKA WGS 84. You can easily see the difference between these two systems in an image or map. The above references to CLLocationCoordinate2d using WGS 84 is also true, but the significance there is related more to where a particular lat/long coordinate is
2w
As iOS developers, what’s the biggest pain point you’d like Apple to fix?
I’ve observed several areas in iOS where user experience could be enhanced, such as keyboard flexibility, animation speed, biometric options, cache management, background uploads, navigation reliability, and automation features. Addressing these aspects would not only improve usability but also align iOS more closely with diverse user needs across regions and use cases. What enhancements would you consider most valuable?
3
0
125
2w