hey! Got something to talk about for #macOS or #iOS? Or one of Apple’s other platforms? Submit a talk to our awesome conference in #Naarm #Melbourne!
Instruments tip: to keep Instruments in the Dock, take the following steps:
1. In Xcode choose Xcode > Launch Developer Tool > Instruments to launch Instruments.
2. Right-click on Instruments in the Dock and choose Options > Keep in Dock.
If you want to learn more about Instruments, I’m writing a book on Instruments that shows you how to interpret the data and find the code causing problems. Learn more about the book at the following link:
The following article provides an introduction to using Instruments's flame graphs:
https://swiftdevjournal.com/posts/instruments-flame-graph-intro/
If you’re trying to test JSON decoding in a Swift Playground, it crashes the playground’s LLDB RPC server in Xcode 16.3 every time. Works fine in Xcode 16.2 I wasted a lot of time yesterday on this, but now I’m installing 16.2
Forum post and feedback links here: https://developer.apple.com/forums/thread/778850
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
To the Xcode haters:
Your favorite IDE is also terrible in different ways. You just have Stockholm / Bloomberg Terminal syndrome.
Advanced build insights from your Xcode projects are coming to Tuist. Understanding your builds over time and across branches is the first step towards optimizations:
https://docs.tuist.dev/en/guides/develop/insights
Figured out how to call Rust functions from within Swift. Small steps to cooler things.
Does anyone know how to make #Xcode 's debugger not take 100 years to start up? I often build and run an app from Xcode and then stop running it just so that I can cancel the debugger and not wait for it to start up. Then I just check my change manually in the app itself.
The following article shows how to use Instruments to see how many times your SwiftUI views redraw:
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
PSA: don't upgrade macOS 15.4 if you need #Xcode 16.2[1] - debugger crashing https://developer.apple.com/forums/thread/775563
[1] Xcode 16.3 Swift has changes that may make the project no longer compile.
There are some issues with URLSession in the simulator, so I would expect an RC3 coming as well:
The following article provides an introduction to Instruments flame graphs:
https://swiftdevjournal.com/posts/instruments-flame-graph-intro/
