Post not yet marked as solved
The actual issue is that Xcode 13 does stop at breapoints, but using the debugger (po someObject) does not print but gives us an error:
warning: Swift error in scratch context: error:
/Path/To/OurApp/OurApp-Bridging-Header.h:14:9:
error: 'SomeSucessfulyUsedDependency.h' file not found
This issue happens on parts of our code, other parts work fine. This is reproducible.
The same project works fine with Xcode 12
Starting with Xcode 13, when running our app in DEBUG config on sim
or device (both iOS 15, but we have tested sims <iOS15 too), the
first line in console is:
error: invalid target, create a target using the 'target create' command
It looks like Xcode 13 is unable to create a target in LLDB. But maybe the console output is misleading and unrelated.
That obviously make debugging a none-nice process ...
Any help appreciated.
Post not yet marked as solved
I have fetched the Apple Sample code for SimpleTunnel project and modified it to build and run under current Xcode and Swift 5.
I am trying to establish a VPN tunnel app<->tunnel_server using the default configurations (default config.plist, default "Demo VPN" setting in "PacketTunnel" section of app).
My issue is that PacketTunnel Network Extension get terminated due to not having suitable Entitlements, at least this is how I read the log in Console:
-CMSessionMgr- CMSessionMgrHandleApplicationStateChange: CMSession: Client com.mycompany.com.example.apple-samplecode.SimpleTunnel.PacketTunnel with pid '3348' is now Terminated. Background entitlement: NO LongFormVideoApp: NO
I did follow this forum post to create appID and provisioning profile and I tripple checked I am using this profile for the "PacketTunnel" target.
Dumping the profile, that looks OK to me:
<key>Entitlements</key>
<dict>
<key>com.apple.developer.networking.networkextension</key>
<array>
<string>app-proxy-provider</string>
<string>content-filter-provider</string>
<string>packet-tunnel-provider</string>
<string>dns-proxy</string>
<string>dns-settings</string>
</array>
...
Post not yet marked as solved
@eskimo:
Your helpful code of Socket API Helper does not compile on Swift 5 any more.
Reasons:
1: Cannot convert value of type 'UnsafePointer' to expected argument type 'UnsafeMutablePointer'
2: Cannot pass immutable value as inout argument: 'pointee' is a get-only property
And update would be super helpful and make my day.
Thx!
PS: I was forced to choose at least one tag and could not find a suitable one. Thus Xcode. Sorry.
Post not yet marked as solved
We want our testers to be able to:1) replace an installed Tesflight version of our app (test-version) when installing the App Store released version of our app (app_store-version) without loosing their data (all inside the app bundle, Core Data and such, Keychain data, User Defaults).2) vice versaReplace an installed app_store-version with an test-version without loosing the above mentioned data.The only information I found is in the Testflight documentation: "...If you already have the live version of the app installed on your device, the beta version of the app will replace the live version. When you’ve downloaded the beta app, you’ll see an orange dot next to its name that identifies it as a beta. ..."I did not find any information regarding the opposite case (... if you already have a test-version installed, the app_store-version will replace it...) nor if the above mentioned data is kept when replacing the app.Apple Developer Support told me that they do not have this knowledge and suggested to ask here :-/My Questions are:1) Is is possible to replace a Tesflight version of our app (test-version) with a App Store released version of our app (app_store-version) without loosing the above mentioned data?2) Is is possible to replace a App Store released version of our app (app_store-version) with a Tesflight version of our app (test-version)without loosing the above mentioned data?3) If 1+2 is possible, which parameters are taken into account to replace/ not replace an app? (BundleID & BundleVersion?)
pEpee.