![]() ![]() Are you sure ? All your simulators will be DELETED and new ones willīe created ! ( You can use ` SNAPSHOT_FORCE_DELETE` to skip this confirmation ) The only thing you need to do is install Fastlane and run the following command. It sounds scary, but Fastlane has an action named reset_simulators that do all the hard lifting for you. Solutionįor me, the solution for this error is to nuke all the simulators and recreate them. While Android Studio is decent by way of being IntelliJ, I’d trade it away without question to be able to write Swift+UIKit on Android.Sponsor and reach thousands of iOS developers. Overall it’s smoother than my experience with Android dev has been, where you’ve gotta bring in a boatload of third party dependencies because Android Framework is so poor compared to UIKit, not to mention wrestling with Java baggage (even if you write in Kotlin) and things like ProGuard silently carving out large chunks of functional app code in your prod builds, causing crashes that didn’t exist in testing. I can reliably sit down at the beginning of the work day and hammer through stuff with no issue, and on an M1 Pro machine it’s all quite snappy and responsive. With that setup, it’s been pretty smooth. For the last 3-4 years all dependencies have been handled with SwiftPM. deeply nested blocks, long optional chains, etc). I wonder how much of it comes down to exactly how Xcode is used.įor the past several years I’ve been writing pure code UIKit without XIBs/storyboards and have avoided SwiftUI for anything with mentionable complexity, writing Swift in a style that avoids code smells that make SourceKit grumpy (e.g. Not saying you don't have issues, I'm just trying to help narrow down what may be the issue, there's three bullet points we don't really touch at work which could be the problem. I've seen literally no difference in any of our apps and we have 50+ apps in our catalog at the moment, enormous apps too and all launch super fast. Launching an Xcode project with SPM is SLOW. Works fine for us using Azure and we're pretty much the complete opposite of Indie. Remote dependency resolving is horrific and unusable outside of Indie development. ![]() We have build scripts that run separate from SPM so this isn't something we have an issue with. ![]() We don't use these so maybe this is the root cause?Īgain, something we don't use so maybe this is part of the issue.īasic build settings with SPM? Nope. SPM with test plans? Add 4-10 mins to CI. If you're having those issues something sounds wrong, I don't experience any of it. Take note that this list is live and based on most frequent questions in posts will be updated with "quicklinks". There's too many to list them all, however here's a convenient link to all programming guides at There is also dedicated subreddit for learning Objective-C: /r/learnobjectivec. ![]()
0 Comments
Leave a Reply. |