Post

Replies

Boosts

Views

Activity

Xcode Memory Usage
Last week I bought an M4 Pro Mac mini with 24GB RAM to use as my “beta testing” machine. I don’t want to use my main machine for beta OS testing, so figured this config would be perfect for that. However, there have been several times when running Xcode 26 on macOS Tahoe, along with a simulator or two, that memory pressure has gone up into the “yellow” and keeps increasing. I am surprised that 24GB doesn‘t seem like enough RAM. I don’t have giant projects or use anything else on this machine. It’s pretty simple stuff. Maybe this is to be expected with betas: memory leaks, non-optimized code, etc. I’m considering returning the machine while I can. What do others find is a good amount of RAM for fairly modest development needs?
1
0
56
4w
MacOS 15.4 removes rsync —log-file option?
I installed MacOS Sequoia 15.4 and now my backup script no longer works. My script is using rsync in this way: rsync -avz —delete —log-file=“$LOG_FILE” “$SRC_DIR” “$DEST_DIR” This has been working fine for a very long time. After updating to 15.4, this produces the error “rsync: unrecognized action —log-file=/users/admin/logs/backuplog_xxx.log”. The log file path is correct (and hasn’t changed). Interestingly, the man page for rsync no longer shows the —log-file as an option. I know I can use: rsync -avz —delete “$SRC_DIR” “$DEST_DIR” > “$LOG_FILE”` or even rsync -avz —delete “$SRC_DIR” “$DEST_DIR” > “$LOG_FILE” 2>&1` to also capture stderr. However, I liked the output from the built-In log option. Does anyone know why this might have been removed or if there is a way to get it back? Thanks.
7
2
938
Apr ’25
Initial Setup of Xcode Cloud won't grant Github access
I'm trying to set up Xcode Cloud for the first time. When I go through the "Get Started" flow and get to "Grant Access to Your Source Code" step, when I click the "Grant Access" button, I get "This Operation Could Not Be Completed." It has the correct URL to my Github repo. Github is working fine in Xcode itself: I can push and pull changes and view repo history. I've tried: restarting Xcode rebooting the Mac Removing the Github account from Xcode and adding it back Creating a new Github personal token and removing the Github account from Xcode and using the new token to add it back I've looked through my Github settings and don't see anything that might cause an issue. I filed FB16511549 to report this. The error dialog in Xcode automatically filled the feedback fields, and says: "API Invalid status code: 500. XcodeCloudCombineAPI.XCCResponseError:1" I'm running Xcode 16.2 (16C5032a) on an M4 MacBook Pro running Sequoia 15.3.1 (24D70). Does anyone have any insights or ideas of other things to try? Thanks.
4
3
687
Feb ’25