apple pencil battery life

Hello Kanazawa Kenta, The Enterprise APIs aren't available to individuals; however, your university may qualify for research purposes. Please work with your university's administration to contact us to create an Enterprise Apple Developer Account for research purposes. See the Get in touch button.

I'd really like to have a way to integrate with Spotlight in the interim. Understood. I supported Spotlight importers back in the day, and as part of that I created infrastructure to make the whole task easier. I never got around to shipping that as sample code that because I expected CSImportExtension would come online and make it redundant. It seems like I was overly optimistic )-: My code was written in Objective-C, but I spent yesterday converting it to Swift [1]. There are two parts to this: QCFPlugIn — This is a generic mechanism for building different types of CFPlugIn implementations [2]. QSpotlightPlugIn — A type-specific subclass that handles Spotlight. QCFPlugIn.txt QSpotlightPlugIn.txt To use this, subclass QSpotlightPlugIn: private final class MySpotlight: QSpotlightPlugIn { override func importFrom(_ url: URL, type contextTypeUTI: UTType, updating attributes: NSMutableDictionary) throws { … your code here … } } and then invoke the infrastructure from your entry point: @_cdecl(MySpotlightFactory)

Welcome to the forum. Do you hope anyone here to know ??? You'd better contact Apple support.

could any of the following override this setting? My understanding is: Using certain third-party SDKs that might have their own encryption. -> YES The presence of specific Apple frameworks like CryptoKit or CommonCrypto, even if not used for non-exempt purposes. -> YES Standard HTTPS calls made through WKWebView. -> NO A temporary bug or caching issue in App Store Connect. -> Always possible, but unlikely.

@Claude31 All devices, physical and simulated. The code I provided consistently doesn't work. @Tomato I found a workaround involving measuring the screen aspect ratio to determine whether a device is an iPhone SE or not. Not the most elegant solution, but does the job. Your answer is interesting because I've always assumed that Apple didn't allow developers to access specific information like device name, etc. due to privacy concerns, so it never really occurred to me to just look up the model name and go from there. This is really useful information to me as it will allow me to tweak UI on a per-device basis, and more. Thank you!

[quote='860800022, reglot, /thread/802423?answerId=860800022#860800022, /profile/reglot'] this fires when AVSpeechSynthesisVoice is initialized inside of an asynchronous context. [/quote] Yeah, that’s the sort of thing I saw expecting. And with that hint I was able to reproduce this trivially: Using Xcode 26.0 on macOS 26.0, create a new project from the macOS > App template, choosing SwiftUI as the UI. Add this code to the VStack in ContentView.swift: Button(Test) { Task { let voice = AVSpeechSynthesisVoice(language: nil) print(voice) } } Choose Product > Run. Click the Test button. I’m not sure whether I’d consider that a bug or not, but it definitely warrants deeper consideration from the engineering team responsible for that code. Please file a bug about this, making sure to include a reference to this forums thread and also attach a sysdiagnose log taken shortly after reproducing the issue. I’d appreciate you posting your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Deve

Well, that’s interesting. I again tried replicating this problem and everything worked for me. But then I tried again in an macOS > App target and I did see the problem. At that point I started digging… It turns out that I made a mistake in my previous post: [quote='860660022, DTS Engineer, /thread/802686?answerId=860660022#860660022'] I created a new project from the macOS > Command Line Tool template. [/quote] I didn’t use the macOS > Command Line Tool template, but rather I used my own personal template. Once I retesting with the built-in macOS > Command Line Tool template, I saw the problem immediately. And that give me a working and a non-working case to compare. And doing that I found that this behaviour is gated by the Member Import Visibility build setting. That’s set in the built-in template and not set in my personal template. And with it set I see the error compiling DataController and with it unset I don’t. This build setting is a product of a recent Swift Evolution change, namely SE-0