apple pencil battery life

1) The circumstances: iPADOS~>18, USB still-imaging-gadget, 1-3 gadgets might connect simultaneously via USB-hub, proprietary DExt, UserClient App in developers' iPADs or in TestFlight. = 1 variation A) UserClientApp has attribute [Background modes][Enable external communications]. = 1 variation B) active USB-hub vs passive. = 1 variation C) ConsoleApp logs iPAD vs ConsoleApp is not started. = 1 the term zombie below assume issue: == after plug-in ConsoleApp logs IOUsbUserInterface::init, ::start; == UserClient never receives respective callback from IOServiceAddMatchingNotification == further IOKit APIs teardown, restart and re-enumeration of connected gadgets doesn't reveal the zombie (while it sees another simultaneous gadget); == unplug of the gadget logs IOUsbUserInterface::stop. =2) The situation when UserClient is in foreground: ~ everything is fine. Note in MAC OS everything (same DExt and UserClient-code) works fine in background and in foreground. =3) The situation when UserClient is in backgroun

Hey team, I have an app in CarPlay where i was pushing the CPNowPlayingTemplate as follows: self.interfaceController.pushTemplate(CPNowPlayingTemplate.shared(), animated: true) This used to work perfectly, but suddenly I have started to get this error NSInvalidArgumentException: Unsupported object passed to pushTemplate:animated:completion:. Allowed classes: {( CPActionSheetTemplate, CPAlertTemplate, CPVoiceControlTemplate, CPTabBarTemplate, CPListTemplate, CPInformationTemplate, CPContactTemplate, CPMapTemplate, CPGridTemplate, CPSearchTemplate )} How is this possible? Even on Apple docs, it says to pushTemplate Refer https://developer.apple.com/download/files/CarPlay-Developer-Guide.pdf https://developer.apple.com/documentation/carplay/cpnowplayingtemplate/

Hello Apple Developer Team, I’m currently using Apple MapKit JS as the main map provider for our logistics, telematics, and HR platform TADMIN, and we are extremely satisfied with its reliability, accuracy, and visual quality. We would now like to expand our Apple integration by migrating our backend reverse geolocation services to Apple as well. However, our current usage requirements significantly exceed the standard 25,000 daily service request limit. At this stage, we already need between 250,000 and 350,000 reverse geocoding requests per day, and this number will continue to grow rapidly. Our TADMIN Tracking product processes live GPS data from connected vehicle telematics boxes, and each vehicle sends an average of 1.5 pings per minute in normal mode. We currently manage around 140 vehicles and are already in discussions with new customers that will add over 1,000 additional vehicles to the platform soon. As our customer base continues to expand, we expect this growth

Hello, If you add a ManipulationComponent to a RealityKit entity and then continue to add instructions, sooner or later you will encounter a crash with the following error message: Attempting to move entity “%s” (%p) under “%s” (%p), but the new parent entity is currently being removed. Changing the parent/child entities of an entity in an event handler while that entity is already being reassigned is not supported. CoreSimulator 1048 – Device: Apple Vision Pro 4K (B87DD32A-E862-4791-8B71-92E50CE6EC06) – Runtime: visionOS 26.0 (23M336) – Device Type: Apple Vision Pro The problem occurs precisely with this code: ManipulationComponent.configureEntity(object) I adapted Apple's ObjectPlacementExample and made the changes available via GitHub. The desired behavior is that I add entities to ManipulationComponent and then Realitiykit runs stably and does not crash randomly. GitHub Repo Thanks Andre

revenuecat is asking for the in app subscriptions to be approved first in order for the pay wall to display and function properly, but apple support keeps flagging them as developer action needed and complaining that they can't access in app subscriptions. what do I do?

Hello Apple Team, We’re building a CloudKit-enabled Core Data app and would like clarification on the behavior and performance characteristics of Binary Data attributes with “Allows External Storage” enabled when used with NSPersistentCloudKitContainer. Initially, we tried storing image files manually on disk and only saving the metadata (file URLs, dimensions, etc.) in Core Data. While this approach reduced the size of the Core Data store, it introduced instability after app updates and broke sync between devices. We would prefer to use the official Apple-recommended method and have Core Data manage image storage and CloudKit syncing natively. Specifically, we’d appreciate guidance on the following: When a Binary Data attribute is marked as “Allows External Storage”, large image files are stored as separate files on device rather than inline in the SQLite store. How effective is this mechanism in keeping the Core Data store size small on device? Are there any recommended size thresholds or

I'm encountering an issue with navigation title behavior in watchOS SwiftUI. When using a String for the navigation title, long titles automatically scroll as expected. However, when switching to Text with custom foreground color, the scrolling behavior is lost. Important Observation: The system Settings app on watchOS successfully displays navigation titles with blue color while maintaining scroll behavior. This suggests it should be technically possible - am I missing some implementation approach? struct ContentView: View { var body: some View { NavigationStack { NavigationLink(Go Next) { LinkView() } } } } struct LinkView: View { enum NavigationTitleMode: String { case string case text } @State private var titleMode: NavigationTitleMode = .string let title: String = Watch UI Test Navigation Title var body: some View { switch titleMode { case .string: content .navigationTitle(title) case .text: content .navigationTitle { Text(title) .foregroundStyle(.blue) } } } var content: some View { VStack { Text(Mode:

I have an AppleTV app which I released in 2016. I've updated it and released a new version every year without much hassle. This year, with tvOS 17.2, the layered app icon isn't working right. This is a two-layer image made with PNGs. When it's selected, it looks right and the layers move correctly: But when it's not selected, the background layer disappears: Screenshots are from the simulator but it also happens on the device. It's inconsistent; sometimes it's the front layer that disappears. Occasionally both layers work, but I can't tell why. I've spent a day trying everything. Very frustrated. The icon previews correctly in Xcode and in Parallax Viewer. The image sizes are correct: 400 x 240 for Small, 800 x 480 for Small@2x, 1280 x 768 for Large. The back layer is a non-transparent PNG. I tried adding a Large@2x set. Didn't help. Originally I had a three-layer image with no middle layer PNG. I deleted the empty middle layer, but that didn't help. All the PNG files are from GnuIMP. Same color space, even.

I am constantly running out of storage on my iPhone 16 Pro. I keep having to move my photos and videos to my laptop and delete them from my phone, and I’m constantly needing to offload apps and manually clear caches in some apps to free up storage. I finally got sick of having this cycle every two weeks so looked into it more closely. I’m finding that iOS consumes 32 GB, and then another system reserve category is consuming an additional 23 GB. Meaning the system reserved files are consuming half of the storage on this phone and effectively making it a 64 GB model. I understand the system will need to consume some capacity for itself and that iOS is getting larger, but nearly 50% of the capacity of the phone is insane. Looking closer into the categories, I’m seeing that iOS has taken it upon itself to also permanently provision 10% of the storage capacity for reserve update space. Already another instance of “why am I having to lose so much of my functional capacity to an occasional process?” but I can unders