Post not yet marked as solved
I tried some more ideas, but still not working.
First of all, I added a dummy property to the "worker" object which does the work whose progress I need to display. The dummy property is published and observed by the List view, and updated every time any of the doneness values are updated. So now my body() method runs, and I also put the value of this dummy property and the value of foo.doneness in the title of each 'ProgressView'.
Result: Now my body() method runs whenever any progress is updated, and the value of the dummy property in each progress view's title updates as expected. But, although the foo.doneness values are definitely being updated (I print the new values to the console in the "worker"), the very same calls, foo.doneness, inside that body() method, as seen in the progress view's title, are stuck at 0.0. In other words, this body() is stuck at the initial value snapshot, definitely not observing any changes.
I also tried adding a willSet to Foo.willChange, manually sending objectWillChange as shown below, but this does not help either:
@Published var doneness: Double = 0 {
willSet {
objectWillChange.send()
}
}
Thank you, Timothy.
Done. Please refer to FB7829688.
Post marked as Apple Recommended
alarouche, you must (1) install the Xcode 12 beta and then (2) select it. For example, if you have installed Xcode-beta into /Applications,
sudo xcode-select -s /Applications/Xcode-beta.app
After performing these two steps, then the command shown in the WWDC video
xcrun safari-web-extension-converter /path/to/my/extension/folder
will work.
For me, using macOS 10.15.6 beta on a MacBook Air, the answer by @teddy06550 was close, but the actual example was simpler. Weird. Teddy's second command failed:
Air2:~ jk$ sudo tmutil deletelocalsnapshots 2020-06-15-002518.local
Password:
2020-06-15-002518.local is not a valid disk
So instead I did what it implied I needed to do:
Air2:~ jk$ sudo tmutil deletelocalsnapshots /
Deleted 2 Time Machine local snapshots for volume group containing disk '/'
com.apple.TimeMachine.2020-06-15-002518.local
com.apple.TimeMachine.2020-06-22-183122.local
and, voila…
Air2:~ jk$ tmutil listlocalsnapshots /
Snapshots for volume group containing disk /:
Air2:~ jk$
No more local backups.
Side note: Before doing this I had 89 GB available, 73.33 GB purgeable and the installer said I had only 16 GB available and needed 34 GB more. After doing this, I have 159 GB available, 73.33 GB purgeable and the installer says I have 86 GB available and it is ready to go. Well, indeed 159-73=86. So it looks like the space used by Time Machine and the space used by "purgeable" are different issues.
By the way, think I know how I got so much in Time Machine local backups. During the last few months, I have created a half dozen or so screencast videos using Screenflow, which is an ( excellent) document-based app. Some of them may have been left dangling because I did not want to save them and force quit. That may or may not have made the problem worse.
Anyhow, thanks very much to Teddy for the tmutil tip. I think this is a bug – that Time Machine local backups can use such a huge amount of space with absolutely zero visibility. Am I wrong or should I file a bug? Or maybe is this fixed a Big Sur?
Post not yet marked as solved
One more thing (for code copy-and-pasters): Ensure that the type declared in the code for the outlet or action matches the type of the object in the storyboard 😐
