Yes, I have just struck this problem. Just as you noted, this worked fine on Xcode 12 betas 1 and 2.
DDP
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Auckland, New Zealand
Post
Replies
Boosts
Views
Activity
In the DailyScrum extension, you need the code:
mutating func update(from data: Data) {
title = data.title
attendees = data.attendees
lengthInMinutes = Int(data.lengthInMinutes)
theme = data.theme
}
This appears in the "Passing Data with Bindings" section downloadable completed code, but I think it may be missing from the step-by-step instructions (or I missed seeing it).
Feedback filed in support of continuing Xcode Server. Perhaps others would like to do the same.
I like Xcode Server and it is particularly useful for non-App Store Mac applications, especially if they have sensitive (eg health) in-house only data, stored on local network repos. A big screen display of build and test status is nice and reassuring. Also, if needed you can hammer your local infrastructure with impunity, which does not sound feasible for Xcode Cloud via GitHub.
Would be great for the OP bug to be fixed too. Moving from git submodules to Swift packages is great, with many upsides and reduction in churn. It's a shame to lose CI functionality as a result.