I think if the data is so sensitive you don't want them appearing even in Xcode 15's console, then best to avoid logging in the first place? Where else would you see the variable? (Hopefully development doesn't involve actual PII in the first place.... ;))

@eskimo In Xcode 15, shouldn't your first log line above print out the actual value (same as the second) when logging in Xcode 15's console? If it doesn't, then we have to mark data as globally public just do debug.

Thanks! Reading....

I think the behavior should be that you can see the private data in the Xcode console, not the word <private> or a blank. If it shows up as <private> in Xcode, it's useless for debugging, right? While working on that app, you want to see the values AND have them hidden outside of Xcode, right?

This worked for me, too. Only I did an "Archive" build, kept the iCloud development option ("Distribute to your Team" option), then exported it to a folder. Just moving it to Applications made the iCloud Drive folder visible.

Did you try setting defaults write com.apple.dt.XCBuild EnableSwiftBuildSystemIntegration 0, then clean and build using Xcode 13.2.*?

I had to clean the project's build folder, then build again for it to take effect.

Note that Xcode seems to make appropriate suggestions/completions for the code you yourself have authored. It's just the standard frameworks that don't seem to work. Might it have something to do with upgrading one Xcode over another that resulted in the failure to deploy/index the standard frameworks?

Jinx! I can confirm that. Works for me, too.