“We are unable to process your request”

Which bit? I was unaware that I could simply run both mitmproxy as well as rvictl and tcpdump at the same time. However I did just that; inspecting the trace file (in Wireshark) revealed the following (bundle name redacted): [Process Information: com.apple.WebKit(1114) [(1111)]] [Id: 1114] [Name: com.apple.WebKit] But I guess you are right in that this does not tell me anything I did not already know. Furthermore I do not see any TLS handshake messages after the server sent its certificate along with the Finished message which confirms that there might be some sort of pinning going on.

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?

[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='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 co

Dear Quinn, In February 2021, when an Entitlement was added to Team ID WEJZZZZZZZ, I received the following email from Apple and learned how to add the Entitlement to a provisioning profile: Hi, Does Apple add entitlement to my team ? (== App ID: WEJZZZZZZZ) Yes, the entitlement was actually added to your “team”. That gives you the ability to add the entitlement to any app that’s managed by your “team”. Here is the configuration information you can use to check the current status and/or configure your own project: -To use the entitlement, you need to codesign your app with a provisioning profile that includes it. In the Apple developer portal website, you’ll need >to do the following: In the “Provisioning Profiles” section, click the “+” and to create a new profile In the “What type of provisioning profile do you need?” section, select “iOS App Development” Walk through the creation process and directly after the “Select devices.” section, you should see a new section titled “Do you need additiona

> I have a custom hardware board that I want to communicate serially with from an iPad. Should I use the DriverKit route or the MFi route? Depends on exactly what your needs are and the hardware you're working with. Starting with MFi, the biggest advantage is that the software side (ExternalAccessory framework) is far simpler to use and includes support for background access (DriverKit does not). The main downside is that it requires a certain amount of custom hardware and the certification process. Comparing it with DriverKit is... complicated. The software side of DriverKit is FAR more complicated. To start with, the DriverKit API is a somewhat odd derivative of the IOKit kernel API. For someone who's familiar with IOKit, it's similar enough to be understandable, but for a new developer, the learning curve can be quite significant. None of this is helped by the fact that DriverKit is poorly documented[1], to the point that my standard advice to new developers is to study the IOKit kernel API (wh

Do I need to submit the code-level support like everyone else too? These are my request Id 7P8645AYBX 3JW6U957WD 8B2943ZAUY

Your code that wraps UIActivityViewController with UIViewControllerRepresentable and presents it in SwiftUI looks good to me. I've tried running the code on my iOS simulator (iOS 26.2 23C54) and here is the behavior I see: When sharing one single item, the code demonstrates the behavior as I described. When sharing two items (by using var shareItems: [Any] { [textItem1, textItem1] }), the Save as field isn't editable, and so there is indeed no way to specify the file names. Also, two files are generated, one for each item. So it's not that the way you present UIActivityViewController has anything wrong; it's that UIActivityViewController doesn't allow you to specify the file names when sharing multiple items. I don't see any way that can change the behavior because the UI of UIActivityViewController is system-provided. Please feel free to file a feedback report to request the feature you would like to have. For now, you might consider sharing one single item, if that is appropriate to your use case.

Thanks for the post, hope some RealityKit experts jump quickly on this thread. However I wanted to be the first to tell you: Welcome to RealityKit and Metal! Transitioning into 3D graphics and procedural generation is exciting. Here comes my simple disclaimer. I’m not an expert at RealityKit, however I got before the tips that made my simple tests extremely successful and I would like to share those with you, if you require more in detail I would open up this thread to any RealityKit expert that wants to jump in here. When you add hundreds or thousands of individual rocks, trees, and bushes as separate RealityKit Entity objects, you are overwhelming the CPU. Even if the meshes are simple, RealityKit has to calculate the transform, bounding box, and physics for every single entity, every single frame, and then send individual instructions to the GPU. To fill dense background spaces without killing performance, you need to shift the workload. So, instead of creating 1,000 separate Entity bushes, you sh