mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

171K
active users

#xcode

12 posts11 participants2 posts today

All I want for :
- documentation
- an that can build my code without internal inconsistency errors
- a debugger that can po my values
- a view debugger that can actually capture a view hierarchy

I know the real problem is I'm probably Naming It Wrong™️ or whatever, but I really wish had an option to wrap the filenames in the Navigator rather than truncating them. I'm not worried about running out of vertical space in this scrollable list! And, oddly, the data obfuscation is not particularly valuable to me!

#Xcode experts: let's say I finally "managed" to reproduce a very rare crash that occurs to some GlanceCam Users and that I did put some notes in the crash dialog before sending it to Apple, both for reference and to actually confirm it was MY report.

Apple does not strip that message, right? Right??

And if they don't, where do I find it?
I'm not able to retrieve it in the Organizer or in the actual .crash files.

A while ago I did an #Xcode project config change that I like doing to prevent Debug builds from overwriting the Release version. This way I can use Release for personal use with non-test data.

The config change is: add a project-level variable PRODUCT_NAME_SUFFIX, set to "Dev" on DEBUG builds only. That variable suffixes PRODUCT_NAME, effectively propagating to Bundle Identifier, which results in a separate install. I also ensure that code in DEBUG refers to the Dev bundle ID variant, and it all works great.

BUT, it silently breaks SwiftUI previews, with no build errors nor runtime errors visible in the Swift Previews console - just the Canvas showing up blank. Is anybody out there familiar with this issue?

Fun fact: in my current MacOS app, if I set an accentColor to any of the macOS System Colors the app never appears (at least while debugging)

says it's running and the logs show all the usual SwiftData spam. I see the app in the dock but it has to be killed and the offending color setting removed.

Universal System Colors work fine.

I'm not even calling for the accentColor in my code when this happens. It's only defined in the asset catalog

Cool

I have an #Xcode Cloud CI Script that tags builds if they go to AppStoreConnect. It does that in an `ci_post_xcodebuild.sh` by finding out the build number, tagging, and sending the tag with a `git push --tags https://${GIT_AUTH}@github.com/nxtbgthng/[REDACTED].git`

The GIT_AUTH PTA is working, and set correctly, I checked.

Today it began failing with this:

fatal: unable to access 'github.com/nxtbgthng/[REDACTED': The requested URL returned error: 403… (1/3)

SwiftUI experts: How do you debug a feature that uses SwiftUI?

In UIKit I print the current view controller and with lldb I can manipulate the views to figure out what the problem is. This seems not to work in SwiftUI. How do you find the line of code that is problematic to fix an issue?

#swiftui#uikit#ios