This is still correlated with po not working, right? po not working happens only for our project, and only in parts of it (reproducable). "Parts of it" means in some files po does not work 100%, in others it works 100%. The same project and files do not show the error and po works using Xcode 12. For new project, the LLDB error is there (but not for new project created on newly created user) error: invalid target, create a target using the 'target create' command but po works for new projects. probably worth opening a DTS tech support incident so that DTS’s tools expert can allocate time to look at this in depth OK, will do. Thanks!

Just to confirm, both your main user account and your temporary test account were admin accounts, right? Yes, correct. Do you have any .lldbinit files in play? No. At least nothing we manually / intentionally configured. Also keep in mind: this happens reproducable for the complete team in Xcode 13.x and not in Xcode 12.x.

If you create a new user (System Preferences > Users & Groups), log in as that user, run Xcode there, and use it to create and run a new test app, do you still see the problem? No. Does not show the problem.

Which same console output? The invalid target message? Yes. error: invalid target, create a target using the 'target create' command Is that still the case after your ‘deep clean’? Yes. As said also shows up on vanilla iOS "Single View App" (I also have another issue which I assume is caused by the same root. But lets not mix topics. Will create new ticket in case it persists after this is solved. (thx for taking care and sorry for delayed answer. Did not get any notification which I expected)

Very deep cleaning (rm derived data, caches, ++) fixes the missing BackgroundTask console output. So whats left is that Xcode 13 LLDB does not print objects in most places of out code. Reproducible for the complete team. error: invalid target, create a target using the 'target create' command // ... (lldb) po someObject error: <EXPR>:3:1: error: cannot find 'someObject' in scope While Xcode 12.x works as expected. Due to the fact the internet did not explode yet, I assume this is not a general Xcode issue but something related to our Xcode Project. Any hint highly appreciated o/

We could work around this error by replacing #import "SomeSucessfullyUsedDependency.h" with #import <SomeSucessfullyUsedDependency.h> in /Path/To/OurApp/OurApp-Bridging-Header.h. But now we get a different error using po someObject: Looking for "@rpath/BackgroundTasks.framework/BackgroundTasks", error: dlopen failed for unknown reasons. Failed to find framework for "BackgroundTasks" looking along paths: /Users/me/Library/Developer/Xcode/DerivedData/OurApp-cmnmsqemuyxojlavehflywtxguqr/Build/Products/Debug-iphonesimulator/BackgroundTasks.framework/ Looking for "/Users/me/Library/Developer/Xcode/DerivedData/OurApp-cmnmsqemuyxojlavehflywtxguqr/Build/Products/Debug-iphonesimulator/BackgroundTasks.framework/" ,    error: dlopen failed for unknown reasons. error: <EXPR>:3:1: error: cannot find 'someObject' in scope

@eskimo: I have updated the question. Was partly wrong. If you create a new test app from one of the built-in templates, does it have the same problem? A new, plain iOS app shows the same console output. using the debugger (po ...) works though.

The issue was caused by the used iOS device running 12.5.1. Using a iOS 14.x device fixes the described issue. It still can not connect sucessfully but that is a new issue. Sorry for the noise and for talking to myself. (I do not understand why that is though)

Deleted. ignore.

Sorry for hijacking this thread. I am fighting with SimpleTunnel sample as well. I have managed to make it build and run. I did not do any other (config.plist, Entitlements, whatever) changes. Do I need to change the servers config.plist? Is there anything more I have to do? Create and save certificate or such? The issue I am heaving is that when switching the "VPN" swith on to enable it: targetManager.connection.startVPNTunnel() is called and does not throw NSNotification.Name.NEVPNStatusDidChange informs us new state is "connecting" NSNotification.Name.NEVPNStatusDidChange informs us new state is "disconnected" The tunnel_server is running on my MacBook. SimpleTunnel.app on iPhone (device). Thanks and sorry again!