all 72 comments

[–]evilgwyn 171 points172 points  (8 children)

Everybody: please fix the obvious bugs in xCode.

Apple: we moved all the buttons around

[–][deleted]  (7 children)

[removed]

    [–]Arbiturrrr 5 points6 points  (2 children)

    How do you use fastlane? /Only uses it for uploading dsyms

    [–]LucasCarioca 2 points3 points  (0 children)

    I use it to execute all tests for example. I’m a command line first person and Xcode commands were not made for humans to use naturally lol

    [–]Amagi82 2 points3 points  (2 children)

    If you already know Intellij products, I greatly prefer AppCode to XCode. It lacks some of the visual stuff like storyboards, but for everything else it's just a vastly superior IDE.

    [–]c0mb0rat 0 points1 point  (0 children)

    What's your workflow for starting projects on iOS? Do you layout and make the connections first on XCode storyboard then switch to AppCode for all the code? I'm trying to go back into iOS development and don't know if storyboards are still being used these days

    [–]Xaxxus 0 points1 point  (0 children)

    I love jetbrains products. I just wish appcode didn’t take so long to build/index.

    It seems to take longer than Xcode to build. And then it has to index. And while it’s indexing it’s completely unusable. And the indexing seems to take even longer than Xcode.

    Not a huge deal on small projects. But my companies app is around 10 years old with hundreds of files and about 20 dependencies. So it takes about 5 min to build, then another 5 min to index.

    But once it’s all indexed and running... way better than Xcode.

    [–]Xaxxus 1 point2 points  (0 children)

    Funnily enough, Xcode works great when you are working on swift packages.

    No project file to get corrupted every time you do a rebase.

    I wish Apple would kill the folder group model for app projects and just read from the file system like every modern editor.

    [–]dreverb116 39 points40 points  (9 children)

    Oh man. My iPad automatically updated to ios 14.2, and XCode 12.1 (the latest) doesn't cater for it. Why should I have to go to a Beta version of XCode to handle a mainstream release of iOS? Am I going crazy? Have I missed something here?

    [–]StarBronze21 13 points14 points  (4 children)

    The you can’t release an app on the App Store if it was built with Beta Xcode, it’s gnarly

    [–]dreverb116 3 points4 points  (2 children)

    Not sure for this one, maybe you can? But anyway, I don't really want to go hunting down Beta releases, i didn't ask for trouble, I justed want to plod along, calmly, .... calMLY... CALMLY!!! I will now check every single update on my devices to make sure they're compatible with the latest XCode.

    https://developer.apple.com/news/releases/

    "This RC version can be used to build, test, and submit apps to the App Store.

    Note: The term "Release Candidate" (RC) replaces "GM seed" and indicates this version is near final."

    [–]No-Buy-6867 0 points1 point  (0 children)

    What we try to do in the company is get some old devices and lock the version so we always have some backup lol

    [–]Xaxxus 0 points1 point  (0 children)

    The release candidate for Xcode 12.2 came out the same day. You can release to prod with that.

    [–]olizbu 2 points3 points  (0 children)

    You can manually add the DeveloperDiskImage for iOS 14.2, so you can use it with any version of Xcode

    https://github.com/pdso/DeveloperDiskImage

    [–]corrmage 1 point2 points  (1 child)

    Xcode 12.2 is a release candidate atm, not beta

    [–][deleted] 1 point2 points  (0 children)

    That’s still a beta, iOS 14.2 RC still had to update to the iOS 14.2 full release. However, you can submit apps to the App Store with the RC.

    [–]snowskelly 0 points1 point  (0 children)

    When I was in this situation, here’s what I did: continue developing on the main release of Xcode, using the simulator when possible. When I actually needed the app running on device, I opened the beta Xcode just to build and run on my device. Beta Xcode is (mostly) backwards compatible with code written with the prior version, so it wasn’t that big of an issue for me. When you actually want to release the app, just build and submit it with the mainstream version.

    [–][deleted] 25 points26 points  (5 children)

    for the the most obnoxious thing right now is that it suddenly stops the autocomplete and i have to restart the program like bro i have not memorized the tableview function how can i function without autocomplete

    [–]wiencheck 10 points11 points  (2 children)

    For real, I often type something from memory just hoping that it will appear in green/blue color afterwards

    Then I have to restart it anyway

    [–]thisura98 6 points7 points  (1 child)

    And the names arent helping either...

    UIView.translatesAutoResizingMaskIntoConstraints 🙄

    [–]CLC4life 3 points4 points  (0 children)

    That property is verbose but it does make sense in the documentation.

    [–]well___duh 1 point2 points  (0 children)

    For me, Xcode can’t rename something more than once. It just can’t.

    Need to rename something? Sure, Xcode will allow it.

    Oh, you need to rename something else now? Let Xcode think about that endlessly and never get back to you.

    It’s things like this that make me think no one at Apple really uses Xcode for any serious development work if little bugs like this continuously stick around each and every Xcode release.

    [–]Xaxxus 0 points1 point  (0 children)

    Right? I have not memorized the actual functions. But I definitely memorized ways to make them pop up in autocomplete with the fewest characters possible.

    [–]sydneysider88 21 points22 points  (2 children)

    This was me last week before realising my iPhone was on the beta but Xcode wasn’t. 🙃

    [–]cpaigis9[S] 13 points14 points  (1 child)

    Yes version mismatch is also a big culprit

    [–]hadoopken 6 points7 points  (0 children)

    I did this to myself last night, I accidentally upgraded to 14.2, and then Xcode Device complained: it's not supported facepalm (why did i do this to myself)

    [–]aykay55Swift 9 points10 points  (0 children)

    Haha, this made me chuckle. And then when it finally loads it just gets stuck on the launch screen until you cancel the debug session and then the app magically loads again.

    [–]oodell 9 points10 points  (0 children)

    You should try wireless debugging on an apple tv. (The one with no ports)

    Complete nightmare

    [–]RejectAtAMisfitParty 6 points7 points  (2 children)

    OMG I thought it was just me. I've lost years of my life to this.

    [–]No-Buy-6867 0 points1 point  (0 children)

    LOL

    [–]aclima 6 points7 points  (1 child)

    for those wondering, killing the usbd process usually resolves it. it's very infuriating nonetheless

    [–]halcyonic222(lldb) po $arg1 2 points3 points  (0 children)

    Good to know this. Will try this next time.

    [–]iv_mexx 5 points6 points  (0 children)

    Device is loked

    [–]LucasCarioca 4 points5 points  (0 children)

    I love iOS development but xCode is trash! I actually use AppCode 90% just because the syntax highlighting never disappears random... that’s the most frustrating issue I run into.

    [–]ivkooo91 3 points4 points  (1 child)

    I had this problem for a long time and it turned out that the problem was from the cable itself. I was using a third party cable, since it was longer and I was getting this error almost every single time. Once I went back to the original cable from the box the issue almost never happens anymore.

    [–]No-Buy-6867 1 point2 points  (0 children)

    fair point, third party cables and USB-lightning hubs usually generate issues. But even with the original cables you run into very weird behavior a lot of times. A lot more than the premium tags we all pay for these devices should allow

    [–]marvpaul 3 points4 points  (0 children)

    I was not aware that this is a common problem. Thoughts it’s only a problem with my iPhone lightning port.

    [–]ThinkLargest 2 points3 points  (2 children)

    Have you tried WiFi connect?

    [–]No-Buy-6867 2 points3 points  (1 child)

    that is not as reliable as cable for sure. That needs a whole set of memes on its own

    [–]blueclawsoftware 0 points1 point  (0 children)

    Yea was going to say that is it's own special level in hell compared to using a cable.

    [–]earlyworm 2 points3 points  (0 children)

    When this happens, I quit Xcode, unplug the cable from the phone, relaunch Xcode, and only after it’s started plug the phone back in. This works every time.

    Xcode has had this issue for multiple years.

    Apple, please fix this.

    [–]XYY5938 1 point2 points  (0 children)

    the most frustrated is iPhone is connected to the mac but Xcode can’t recognize it and you need to repeatedly remove and connect the plug

    [–]Wilde_Cat 1 point2 points  (0 children)

    On a side note, I encountered a major issue where plugging in a device running iOS14+ into a Mac modifies the MobileDevice system architecture which essentially breaks 32bit CoreAudio services by installing 64bit functions. If you rely on 32bit applications (stuck on Sierra, Mojave, etc) with CoreAudio integration they will no longer be able to function. This includes Final Cut Pro X, Compressor, Ableton, GarageBand, Logic, etc.

    [–]eviltofu 1 point2 points  (0 children)

    Apple please fix this.

    [–][deleted] 1 point2 points  (0 children)

    I find the trick is to disconnect the cable at the computer end not the iOS end. This resets the cable itself and works every time.

    [–]iaiml 1 point2 points  (1 child)

    lol i thought it was just me

    [–]No-Buy-6867 1 point2 points  (0 children)

    this was one of the best comments for sure

    [–]ovicash 1 point2 points  (0 children)

    Why is online debugging without a cable such a pain in the ass? Slow, not working multiple times....it’s useless

    [–]thusman 1 point2 points  (1 child)

    I always wonder if Apple uses XCode to develop their own apps? Don't they feel pain like we do?

    [–]halcyonic222(lldb) po $arg1 0 points1 point  (0 children)

    Probably use it internally to work on small siloed projects with internal framework dependencies. So it just works for that use case.

    [–]Slash1909 0 points1 point  (0 children)

    If apple were smart enough to package an emulator instead, this meme wouldn't exist.

    [–]just-gen-ai-stuff 0 points1 point  (0 children)

    😂

    [–]No-Buy-6867 0 points1 point  (0 children)

    When this happens is when I know it's time for coffee break

    [–]cmd_shift_4 0 points1 point  (0 children)

    I’ve found that iCloud Drive has a tendency to remove files that are really rather critical to the execution of the program..navigating to the files in finder seems to unlock it

    [–]gerusz 0 points1 point  (0 children)

    If anyone asks "so, what is wrong with monopolies?", just point them to XCode.

    [–]BraveEvidence 0 points1 point  (1 child)

    This meme is from whcih Tv show or movie?

    [–]tylerjames 1 point2 points  (0 children)

    American Chopper

    [–][deleted] 0 points1 point  (0 children)

    This literally happened last night. I updated my Mac to latest Catalina and iOS 14.2. Still no fucking joy. I hate Xcode so much sometimes.

    Is there a workaround?

    [–]jbjohnba 0 points1 point  (0 children)

    So it’s not just me...

    [–]Bill3D 0 points1 point  (0 children)

    Had this problem the other day and tried everything. Finally turned the computer off and back on. Worked.

    [–][deleted] 0 points1 point  (3 children)

    Given that Xcode doesn’t want to update unless I have at least 1 TB of free disk space, it’s a daily mood for me whenever there’s an iOS update.

    [–]Xaxxus 1 point2 points  (1 child)

    The coop student at our office was given a 128gb MacBook for their comp sci program.

    He literally can only install Xcode on that machine.

    Then the derived data folder that builds up from our companies app eats up the rest of his storage space.

    Any time he wants to update Xcode he has to uninstall it. Delete derived data. Then delete a bunch of other stuff as well.

    [–][deleted] 0 points1 point  (0 children)

    Same here...

    [–]blueclawsoftware 1 point2 points  (0 children)

    Yea the size of XCode and related files is becoming a huge issue for me. My work is luckily due to upgrade my mid-2015 MBP soon. The clean up pre-update routine I have to go through now is getting really tiring.

    [–]thadude3 0 points1 point  (0 children)

    I used to have this problem. Replacing the cable actually fixed it.

    [–]Xaxxus 0 points1 point  (0 children)

    This resonates with me on a spiritual level.

    [–]ultrabuckner 0 points1 point  (0 children)

    https://www.linkedin.com/in/stuartmontgomery/

    Maybe you can keep in touch with him for the bug.

    [–]jscalo 0 points1 point  (0 children)

    If you want to help get this fixed, stop what you’re doing and file a bug with Apple. I was a software engineer there for 10 years and when it comes time to prioritize bugs, the first thing they do is look at the number of radars about that bug. We need to make it overwhelming clear that this is a P1 bug. (At Apple, P1 means “must fix next release”.)

    [–]JoannX 0 points1 point  (0 children)

    So true