“show when run”

Hello @klinee101 This is interesting, thanks for filing the report. I'll make sure it has the correct eyes on it. Do you see the same issue with Menu ? When I run your code, the display times are the same as Menu, and is not nearly as long as what is shown in your gif. Generally updates are provided in Feedback Assistant, but I encourage you to test new releases as they come and update us here along the way.  Travis

The console shows the following error: proto_: Event {sessionError:(PARSE_ERROR)}

We keep the app running in the background using WKExtendedRuntimeSession (with self-care background mode). The audio session is configured with .playback category, .longFormAudio policy, and .mixWithOthers + .duckOthers options, and activated while the app is in the foreground. For audio playback we use AVAudioPlayer(data:) with in-memory WAV data for metronome ticks, and AVSpeechSynthesizer for voice counts. We also run a continuous near-silent AVAudioPlayer loop to keep the audio session active between beeps. Two specific questions: Is WKExtendedRuntimeSession the correct mechanism for this use case, or should we use something else? (We can't use HKWorkoutSession since users run this alongside other workout apps.) Does .longFormAudio work correctly with .mixWithOthers, or are those contradictory?

Thanks for bringing this to the forums. Lemme start out by linking to iOS Background Execution Limits. You’ve probably already seen it, but it sets the stage (hey hey) for other folks following this thread. There are two parts to this: What’s technically possible? What will be accepted by App Review? I can’t addresse the second part. I don’t work for App Review and thus can’t speak on their behalf. My general advice is that you consult their published guidelines and, if you still have questions, contact them directly. With that out of the way, let’s return to the technical stuff. I want to start by recapping some of the points from TN2277 Networking and Multitasking: Networking works fine in the background as long as your app doesn’t get suspended. If your app does get suspended, normal networking will just stop. For things to continue, you need some sort of special affordance, the canonical example of that being a URLSession background session. There’s no special affordance for UDP. So, your question is equi

We have the same problem. This is happening as soon as we get the fresh code from Git and updates ur local environment. Other wise if we run the code on the local without any fresh pull nothing is affected.

I want to make sure I understand your requirements here. You don’t expect to be running any helper code within the guest, right? So you want to discover the IP address (well, addresses) that the guest OS assigned to the shared interface without any cooperation from the guest? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com