“apple pencil battery life”

Thanks for the reply! I have also tested AVAudioSession with .playback + .mixWithOthers on watchOS. That works for mixing my metronome with Spotify while the metronome app is in the foreground, which matches the behavior I already see on iPhone. However, on watchOS the metronome stops once the app goes to the background, while longFormAudio keeps it alive but then conflicts with Spotify. So this seems to be a watchOS-specific limitation rather than a general AVAudioSession limitation on Apple platforms. It would be very useful if watchOS supported a way to combine background audio persistence (longFormAudio) with cooperative mixing behavior (mixWithOthers) for lightweight apps like metronomes, cues, or coaching audio. Is there any way I can formally request this feature other than the FB22273077 I have already submitted?

Thanks for the confirmation. I’ve retagged your thread with ReplayKit because that’s the only option for this sort of thing on iOS [1]. Coming back to your original questions: [quote='818940021, tylermclovin, /thread/818940, /profile/tylermclovin'] Permission Clarity [/quote] I don’t think you’ll be able to make progress on this. Broadcast extensions were designed for… well… broadcasting, and the user experience reflects that. [quote='818940021, tylermclovin, /thread/818940, /profile/tylermclovin'] Can a Broadcast Extension reliably stay active in the background … ? [/quote] Honestly, I’m not sure. I think this is something worth prototyping before you invest heavily in this project. [quote='818940021, tylermclovin, /thread/818940, /profile/tylermclovin'] App Store Guidelines [/quote] I don’t work for App Review and can’t offer any advice on that front. You could ask them here on the forums, over in the App Store Distribution & Marketing > App Review subtopic. However, I think it’d be best for you to c

[quote='880623022, timboudreau, /thread/818192?answerId=880623022#880623022, /profile/timboudreau'] that would … probably run afoul of one or another App Store policy [/quote] I don’t work for App Review, and thus can’t give definitive answers about their policies. My only advice is that you peruse the App Review Guidelines. At a technical level, on macOS it is possible for an app extension to communicate with an app or launchd agent or daemon that you control, even in the presence of sandboxing. If you want the server side of this to be an app, the best option is for that app to listen on a Unix domain socket that’s located in an app group container. If you want it to be a launchd job, prefix the named XPC endpoint with an app group ID. Both of these are documented in App Groups Entitlement. For more on the XPC side of this, see the various links in XPC Resources. Specifically, XPC and App-to-App Communication has a bunch of backstory you’ll need. And please don’t use Mach messaging directly! [quote='8806240

[quote='880481022, b0xch, /thread/819180?answerId=880481022#880481022, /profile/b0xch'] Is ppq.apple.com really up & running? [/quote] In general, yes. Consider the thread I mentioned earlier. It grew to 10 pages overnight. And the issue even made the front page of AppleInsider [1]. We’re seeing nothing like that right now. Which isn’t to deny your experience. However, whatever’s happening on your device is very likely related to your specific environment, and hence the advice in my previous response on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] https://appleinsider.com/articles/26/03/10/a-now-resolved-apple-server-outage-stopped-developers-from-verifying-apps

Speaking for myself only, I need a proper crash report before I can offer any insight into this. If you can post one here, using the instructions I linked to above, I’d be happy to take a look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880466022, jzilske, /thread/817599?answerId=880466022#880466022, /profile/jzilske'] it's not a WebView where I suspect the traffic comes from [/quote] Ah, OK, thanks for setting my straight. [quote='880467022, jzilske, /thread/817599?answerId=880467022#880467022, /profile/jzilske'] How would I go about setting that up? [/quote] Which bit? To get the source information from mitmproxy, view the request, switch to the Detail tab, and look at the Client Connection section. Getting process information from the packet trace is a small extension of the RVI process described in Recording a Packet Trace: Set up RVI per the Set Up iOS Packet Tracing section. When you get to the tcpdump command, add the -k option to cause it to dump each packet’s metadata. And tcpdump naturally logs the port numbers in each packet, so you can look for outgoing packets whose source port matches the port number you get from the proxy. Having said that, this won’t help given your clarification that the connection is not coming from

[quote='880483022, chapo213, /thread/818938?answerId=880483022#880483022, /profile/chapo213'] I am trying to verify a helper binary/dylib inside my product that can be updated separately from the main binary. [/quote] Is this an executable or a dynamic library? Or do you need this test to support both? And by “inside my product” do you mean that it’s located within an app’s bundle? Or that it’s logically part of your product, but is stored in some other location on disk? And while I’ll have a lot more to say about your overall issue once I better understand it, I want to nip this one in the bud: [quote='880483022, chapo213, /thread/818938?answerId=880483022#880483022, /profile/chapo213'] Does extracting a team-id … automatically verifies that the anchor is apple? [/quote] No. You can’t trust the information you get back from SecCodeCopySigningInformation unless you’ve validated the code signature. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskim

It’s hard to offer insight into this without more info. Do you have an Apple crash report for this? If so, please post it here. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I've been working with SpeechAnalyzer.start(inputSequence:) on macOS 26 and got streaming transcription working. A few things that might help: Make sure the AVAudioFormat you use to create AnalyzerInput buffers exactly matches what bestAvailableAudioFormat() returns. Even subtle mismatches (e.g., interleaved vs non-interleaved, different channel layouts) can cause the nilError without a descriptive message. I found that feeding buffers that are too small (< 4096 frames) occasionally triggers this error. Try using larger chunks â I settled on 8192 frames per buffer. The bufferStartTime parameter needs to be monotonically increasing and consistent with the actual audio duration. If there are gaps or overlaps in the timestamps, the stream mode can fail silently or throw nilError. Instead of replaying a WAV file as chunked buffers, I'd suggest testing with live audio from AVCaptureSession first. In my experience, live capture â AnalyzerInput works more reliably than simulated streaming from a file, possibly be