Recent searches
Search options
#xcode
11 posts11 participants1 post today
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:
swift-dev-journal.kit.com
#programming with #xCode on a #MacMini - is there a way to use my #Neo2 #ISOKeyboard layout on a simulated iPhone? That QWERTZ remapping happening in the simulator is driving me crazy, and I can't for the life of me remember where apple hides the @ sign on their native keyboards, either.
Android studio offers no such problems, by the way. It maps all keys like the main Mac system does, and everything runs fine.
(written on Android with Neo2 screen keyboard)
A few days ago it was reported that Xcode 16.3 had an issue with HTTP/3. Is this still a thing, or has a workaround be found? I’m still running on 16.2 and hesitate to upgrade due to the networking problem other devs reported.
#Xcode
If you try to save some data via share sheet in an iPad app running on MacOS and select save to file it will crash. Copying the data from the share sheet works fine. I believe its a system error.
Works fine on iPhone/iPad.
Fun things to not be doing on a Saturday night.
Latest #Xcode, etc
The following article provides an introduction to using Instruments's flame graphs:
https://swiftdevjournal.com/posts/instruments-flame-graph-intro/
swiftdevjournal.com · Instruments Flame Graph Introduction | Swift Dev Journal
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
developer.apple.comPiece of code in Playground that r… | Apple Developer Forums
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.
With every new #Xcode release there is a question of whether you did something to your code to make things so slow or is it just a new Xcode issue.
I’ve had cases in the past where I've made code changes and things have sped up so I'm not beyond being at fault but…
Builds are so slow I'm expecting the “I'm just a poor little compiler running on what amounts to a supercomputer, please make this easier for me" error.
And all I did was resize an image in my assets
So tedious.
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.
Juggling between two half-broken #Xcode releases (16.2 on macOS 15.4 and 16.3) at the moment is an absolute nightmare. The next beta or bugfix release can't come soon enough…
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
docs.tuist.devInsights · Develop · Guides · TuistGet insights into your projects to maintain a product developer environment.
Continued thread
Figured out how to call Rust functions from within Swift. Small steps to cooler things.
dear god what have they done to the debugger for on device debugging? I don't think it could be any slower.
Developing with #Xcode is increasing unstatisfying and stressful because the bugs prevent one from mentally reaching a flow state. Eg, the debugger fails to print a value which blows your thought process about your code and replace it with figuring out how to work around Apple’s shortcomings. If you’re lucky you might be able to catch the tail of your thought before it floats away, if not you have to expend effort recreating it.
#Xcode autocomplete suggests me some random GH link. Here could be your advertisement I guess...
