Close Menu
geekfence.comgeekfence.com
    What's Hot

    Why Discipline Beats Vision

    July 8, 2026

    Why AI Coding Agents Still Need Clear Specs – O’Reilly

    July 8, 2026

    How the FCC can protect IoT innovation in the 900 MHz band (Reader Forum)

    July 8, 2026
    Facebook X (Twitter) Instagram
    • About Us
    • Contact Us
    Facebook Instagram
    geekfence.comgeekfence.com
    • Home
    • UK Tech News
    • AI
    • Big Data
    • Cyber Security
      • Cloud Computing
      • iOS Development
    • IoT
    • Mobile
    • Software
      • Software Development
      • Software Engineering
    • Technology
      • Green Technology
      • Nanotechnology
    • Telecom
    geekfence.comgeekfence.com
    Home»iOS Development»ios – Why does the view’s internal state is not updated for first mutation when doing it via an Computed Binding
    iOS Development

    ios – Why does the view’s internal state is not updated for first mutation when doing it via an Computed Binding

    AdminBy AdminMay 28, 2026No Comments2 Mins Read3 Views
    Facebook Twitter Pinterest LinkedIn Telegram Tumblr Email
    ios – Why does the view’s internal state is not updated for first mutation when doing it via an Computed Binding
    Share
    Facebook Twitter LinkedIn Pinterest Email


    Attaching the demo code:

    import SwiftUI
    
    struct BufferTest: View {
        @Binding var text: String
        @State private var buffer: String = ""
    
        @State private var presentModificationSheet: Bool = false
    
        var bufferedBinding: Binding {
            Binding {
                text
            } set: {
                buffer = $0
                if text != buffer {
                    presentModificationSheet = true
                }
            }
        }
    
        var body: some View {
            Text("Binding: \(text)")
    //        Text("Buffer: \(buffer)")
    
            InternalModder(binding: bufferedBinding)
                .sheet(isPresented: $presentModificationSheet) {
                    TerminalSheet(text: $text, buffer: buffer)
                }
    
        }
    
        struct InternalModder: View {
            @Binding var binding: String
    
            var body: some View {
                Button("Set") { binding = "New Value" + (1...10).randomElement()!.formatted() }
            }
        }
        
        struct TerminalSheet: View {
            @Binding var text: String
            var buffer: String
            
            var body: some View {
                Text("Binding: \(text)")
                Text("Buffer: \(buffer)")
                Button("Update") { text = buffer }
            }
        }
    }
    
    @available(iOS 17.0, *)
    #Preview {
        @Previewable @State var text = ""
    
        BufferTest(text: $text)
    }
    

    Here, when pressing the button “Set” for first time, the sheet is presented but does not have the updated buffered value. However, mutations after that takes place correctly.

    If we uncomment the

    Text("Buffer: \(buffer)")
    

    within BufferTest’s body, then the updates are taking place correctly.

    Why does this happen ? and if it is the intended behavior, mutating like this isn’t recommended ?

    Also the straightforward way to solve this is via onChange modifier:

    .onChange(of: buffer) { new in
        if new != text {
            presentModificationSheet = true
        }
    }
    



    Source link

    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email

    Related Posts

    security – How and where mnemonic/private keys are generated/stored in IOS for mobile non-custodial wallet

    July 7, 2026

    JSON All the Way Down

    July 3, 2026

    ios – HKStatisticsCollectionQuery initialResultsHandler returns nil results for one specific user — read auth granted, data exists, survives reinstall

    July 2, 2026

    Installing simulator runtimes from the command line – Donny Wals

    June 29, 2026

    SwiftText Learns to Write | Cocoanetics

    June 28, 2026

    uitabbarcontroller – UITabBar unselectedItemTintColor ignored iOS 26

    June 27, 2026
    Top Posts

    Understanding U-Net Architecture in Deep Learning

    November 25, 202560 Views

    Hard-braking events as indicators of road segment crash risk

    January 14, 202631 Views

    Redefining AI efficiency with extreme compression

    March 25, 202628 Views
    Don't Miss

    Why Discipline Beats Vision

    July 8, 2026

    Guest post by Dane Hudson, who is a former 25-year global CEO. Discipline Beats Vision:…

    Why AI Coding Agents Still Need Clear Specs – O’Reilly

    July 8, 2026

    How the FCC can protect IoT innovation in the 900 MHz band (Reader Forum)

    July 8, 2026

    The Download: worms fight pollution, and geoengineering faces reality

    July 8, 2026
    Stay In Touch
    • Facebook
    • Instagram
    About Us

    At GeekFence, we are a team of tech-enthusiasts, industry watchers and content creators who believe that technology isn’t just about gadgets—it’s about how innovation transforms our lives, work and society. We’ve come together to build a place where readers, thinkers and industry insiders can converge to explore what’s next in tech.

    Our Picks

    Why Discipline Beats Vision

    July 8, 2026

    Why AI Coding Agents Still Need Clear Specs – O’Reilly

    July 8, 2026

    Subscribe to Updates

    Please enable JavaScript in your browser to complete this form.
    Loading
    • About Us
    • Contact Us
    • Disclaimer
    • Privacy Policy
    • Terms and Conditions
    © 2026 Geekfence.All Rigt Reserved.

    Type above and press Enter to search. Press Esc to cancel.