Close Menu
geekfence.comgeekfence.com
    What's Hot

    Wilkie refers gambling concerns to anti-corruption commission

    August 13, 2026

    Lumen ready for AI traffic rush – with programmable fabric and “more fiber than anyone”

    August 13, 2026

    With a feel for physics, AI models simulate a wider range of real-world scenarios | MIT News

    August 13, 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 – Using @Environment inside a ViewModifier causes a deep SwiftUI crash — is my theme setup fundamentally wrong?
    iOS Development

    ios – Using @Environment inside a ViewModifier causes a deep SwiftUI crash — is my theme setup fundamentally wrong?

    AdminBy AdminNovember 28, 2025No Comments3 Mins Read10 Views
    Facebook Twitter Pinterest LinkedIn Telegram Tumblr Email
    ios – Using @Environment inside a ViewModifier causes a deep SwiftUI crash — is my theme setup fundamentally wrong?
    Share
    Facebook Twitter LinkedIn Pinterest Email


    I use a custom AppTheme type and inject it via a custom EnvironmentKey. Views can access the theme using @Environment(\.appTheme) or override it explicitly.

    While this work fine in most cases it somhow causes mysterios crashed deep inside SwiftUI internal code. The crash does not happen inside my code and Xcode does not show a meaningful stack trace.

    The crash only happens when using the environment value inside the modifier (see demo code below). Using @Environment(\.appTheme) directly inside views works perfectly.

    The theme does not change dynamically and is a plain struct. I only want globally accessible style definitions.

    So the question is: Is there anything fundamentally wrong with using a custom theme via @Environment inside a ViewModifier?

    I cannot tell whether:

    • my general theme architecture is flawed,
    • I’m accidentally triggering some SwiftUI limitation regarding Environment inside modifiers,
    • or this is a SwiftUI bug.

    I’m not trying to implement dynamic theme switching or anything complex — I only want a central place for styles that I can access across the app without manually passing the theme down everywhere.

    Before trying to redesign everything, I want to know whether this pattern is supposed to work, or whether SwiftUI has a known limitation here.

    Any insights appreciated.

    Code:

    // Abstract AppTheme build on tokens
    struct AppThemeTextTokens {
        var primary: Color
        var font: Font
    }
    
    struct AppTheme {
        var text: AppThemeTextTokens
        //...
        
        static let `default` = AppTheme(...)
    }
    
    
    // Concrete, app specifix app theme
    extension AppTheme {
        static let theme = AppTheme(
            text: .init(primary: .primary, font: .largeTitle)
        )
        
        //...
    }
    
    
    // App Theme EnvironmentKey
    private struct AppThemeKey: EnvironmentKey {
        static var defaultValue: AppTheme = AppTheme.default
    }
    
    extension EnvironmentValues {
        var appTheme: AppTheme {
            get { self[AppThemeKey.self] }
            set { self[AppThemeKey.self] = newValue }
        }
    }
    
    
    // Modifier to apply theme to Text views
    struct AppThemeTextModifier: ViewModifier {
        let theme: AppTheme?
        @Environment(\.appTheme) private var envTheme   // <-- This somehow causes the crash
    
        func body(content: Content) -> some View {
            let theme = theme ?? envTheme               // <-- Crash
            // let theme = theme ?? PTAppTheme.theme    // <-- No Crash
            
            return content
                .font(theme.text.font)
                .foregroundColor(theme.text.primary)
        }
    }
    
    extension View {
        func textAppTheme(_ theme: AppTheme? = nil) -> some View {
            modifier(AppThemeTextModifier(theme: theme))
        }
    }
    
    
    // Inject theme to @Environment
    struct RootView: View {
        let theme = PTAppTheme.theme
        
        var body: some View {
            SomeSubViews()
                .environment(\.appTheme, theme)
        }
    }
    
    // Theme usage via @Environment
    struct DeepDownSubview: View {
        @Environment(\.appTheme) private var theme
        
        var body: some View {
            Text("Hello World")
                .textAppTheme()
        }
    }
    



    Source link

    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email

    Related Posts

    What’s New in Xcode 27

    July 30, 2026

    ios – iCloud Dashboard returns “Internal Error” when querying records across all containers

    July 27, 2026

    ios – How to resolve the “Failed to build cache” build error in Xcode on macOS running in Docker in the docurr/macos project?

    July 22, 2026

    ios – Do Critical Alert (Apple) sounds play one at a time, or can two overlap?

    July 17, 2026

    ios – Bizarre animation issue in SwiftUI

    July 12, 2026

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

    July 7, 2026
    Top Posts

    Understanding U-Net Architecture in Deep Learning

    November 25, 202584 Views

    The Next Paradigm in Efficient Inference Scaling – The Berkeley Artificial Intelligence Research Blog

    May 16, 202647 Views

    Is it too late to start learning AI and machine learning in my 30s or 40s?

    April 9, 202647 Views
    Don't Miss

    Wilkie refers gambling concerns to anti-corruption commission

    August 13, 2026

    Independent MP Andrew Wilkie has taken the fight over gambling reform to the National Anti-Corruption…

    Lumen ready for AI traffic rush – with programmable fabric and “more fiber than anyone”

    August 13, 2026

    With a feel for physics, AI models simulate a wider range of real-world scenarios | MIT News

    August 13, 2026

    Monitoring beyond SNMP: Turning your network into a sensor

    August 13, 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

    Wilkie refers gambling concerns to anti-corruption commission

    August 13, 2026

    Lumen ready for AI traffic rush – with programmable fabric and “more fiber than anyone”

    August 13, 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.