Thank you so much for the clarification! Just to make sure I fully understand: you're suggesting that the correct approach is to continuously loop over readDatagrams() until it either returns an error like NEAppProxyFlowError.aborted or no datagrams. Within each iteration, I should add a new Task (or handle them concurrently) for processing the datagrams, while keeping the overall flow open and tracking task state if needed. Is that correct?

Thank you for your response, it was incredibly helpful in organizing my approach to flow lifecycle management. I also wanted to share that the main issue appeared to stem from how the flow was being opened. Initially, I was using: try await flow.open(withLocalFlowEndpoint: flow.localFlowEndpoint) After updating to: try await flow.open(withLocalFlowEndpoint: nil) …the same code began working as expected on iOS versions > 18.4.1. Really appreciate all your help throughout the investigation!

[quote='875486022, DTS Engineer, /thread/815033?answerId=875486022#875486022'] Hmmm, that’s a minimum failing example, right? That is, you wrote this code specifically to reproduce the crash, right? [/quote] Yes, that's correct! I used the wrong term earlier. The snippet is a minimum failing example, written specifically to reproduce the crash as simply as possible.

[quote='875671022, DTS Engineer, /thread/815033?answerId=875671022#875671022'] Given that you can reproduce this so easily, I recommend that you file a bug about it now. When doing that: Make sure to enable additional VPN logging, per the VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page. After reproducing the problem, grab a sysdiagnose and attach it to your bug report. Once you’re done, post your bug number here. My plan is then to grab the crash report from your sysdiagnose log and dig a bit deeper. [/quote] Sounds good, thank you! Filed report: FB21933607 In addition to the sysdiagnose with the VPN logging profile enabled, I also attached a Minimum Failing Example similar to the code sample in the first message.