fetchLastDisconnectError crashed

Question

Created Nov ’22

Replies 3

Boosts 0

Participants 2

Since fetchLastDisconnectError is available from iOS 16, the App I'm working on recently released including this API, but there are many crashes occurred from it. Based on my investigation, it looks like it crashed if it is called when the VPN configuration was not installed yet (NEVPNStatus == .invalid). Apple document doesn't mention any requirements to call this API. So, I'm not sure how to call it correctly and safely. I created a bug report already and am waiting for their feedback.

Could anyone who has experienced and solved this advice for the issue?

Thanks.

Screen Shot 2022-11-18 at 4.40.16 PM.png

Boost

Answer 1

DTS Engineer OP

Apple

Nov ’22

I created a bug report already

What was the bug number?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

dexjkim OP

Nov ’22

Here is the bug number. - FB11804282 Thanks.

0

Answer 3

DTS Engineer OP

Apple

Nov ’22

Here is the bug number. - FB11804282

Thanks for filing that.

I took a look and there’s no crash report attached to the bug. That makes it hard to offer any insight into this. Please do the following:

Enable extra logging per the VPN (Network Extension) for iOS instructions on our Bug Reporting > Profiles and Logs page.
Reproduce the problem outside of Xcode, so your app crashes.
Then trigger a sysdiagnose log.
Finally, attach that to your bug report.

For more hints and tips about filing bugs, see Bug Reporting: How and Why? .

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0