Until iOS 13.4 I was using a property observer to update the UserDefaults for a @Published Bool value @Published var mutedAudio: Bool = UserDefaults.standard.bool(forKey: "mutedAudio") {
didSet { UserDefaults.standard.set(self.mutedAudio, forKey: "mutedAudio") }
}With the first beta of iOS 13.4 didSet() is not called anymore if I use in SwiftUI the toggle() method and I must use a logical negation:Button(action: {
// self.settings.mutedAudio.toggle() doesn't work in iOS 13.4
self.settings.mutedAudio = !self.settings.mutedAudio // workaround
}) {
Image(systemName: settings.mutedAudio ? "speaker.slash.fill" : "speaker.2.fill").resizable().frame(width: 24, height: 24)
}Is there a better solution than waiting for the next iOS 13.4 beta? 🙂
gui_dos
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
Italy
Post
Replies
Boosts
Views
Activity
As a diabetic user and programmer I am experiencing a new serious bug in the iOS 14.5 beta: when invalidating an ISO 15693 session, no sound is played and the temporary confirmation alert is shown only when you define an error with invalidate(errorMessage: String).
Abbott’s LibreLink app, which lets you scan the FreeStyle Libre glucose sensor, for example, doesn’t let you know when a successful scan has been completed.
Anyone can confirm?