shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

271
active users

#xcode

2 posts2 participants0 posts today

Very rewarding to be at the point where new features build on foundational code I've already written

Added export of maps as images and copying a map to the clipboard in about 2 hours.

That may not seem all that quick but consider you are starting with #Xcode -> New Project and think about how much goes into getting to what feels like magic where you press Cmd-C and boom, there is an image of the map on the clipboard.

Random Xcode shortcut discovery: if you're using a string catalog (e.g. Localizable.xcstrings) and you have a call to something that takes a String.LocalizationValue or LocalizedStringKey (e.g. String(localized:) or any SwiftUI component like Text() that takes a localized key argument), command-clicking on the string constant will jump you directly to the corresponding entry in the string catalog. 🤯 #Xcode #SwiftUI

Cool, I just discovered that #Xcode Simulator will read restrictions that you set on your mac from an MDM. You'll have to restart the ”device” for changes to take effect, but still less hassle than enrolling a physical device.

Help!!!
Does anyone know how to address ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols]
My is being rejected from AppStore Connect since Xcode 16.3, and now even switching back to 16.2 or older branches it will give me the same issue.

Not sure what this is exactly…

Any guidance is greatly appreciated
#Xcode #Swift #Apple #iOSDev

Continued thread

The biggest thing stopping the #mac from being a good source for #gaming is actually the difficulty it takes in developing games that can run on the mac and run well. #Apple likes to tote there capabilities,but what they don't say is that #developing for the mac takes twice as long as to develop the same for windows, not to mention that on an accessibility scale, it is not easy to use #XCode to directly code on the mac, trust me, I've tried and i found it way easier to use #VSCode to make even basic programs whereas for the mac, using XCode to do the exact same thing is like 10 times slower and harder to do for the same amount of work simply because of navigation alone with #VoiceOver.

If you have any previews in your #Xcode projects that are using the `return someView{}` syntax the latest update will return an error for this.

The error is that you are not returning a `some SwiftUI.View` type regardless if the view you are returning is in fact a SwiftUI.View.

I've not refactored my code around this yet but if you have this sort of pattern you may want to hold off on updating

(devlog) the placeholder. that bugged me for a while

the culprit is to separate representations. both are used as a source of truth for different parts of the system. the UI deals with ui-representation; everything else relies on text-representation. that is a common design in wysiwyg/richtext editor.

of all code editors I'm aware, i find #xcode editor placeholder the most beautiful, and I plan to copy that ux