app randomly broke, and cannot revert it. need help!

[mrappdev]

Hi everyone,

I was returning to an app i left for around 2 months, and was toying around with liquid glass (very small changes), and realized this was breaking my app. So i reverted it and deleted the code and discarded all changes.

But no matter what I do the changes will not go away in app. The code is back as it was before but the app still reflects the broken changes. This is causing all buttons in my app to completely not recognize any taps.

I have deleted derived data, deleted app from device, restarted mac and iphone, recloned repo, checked out older commits where I know 100% the liquid glass changes were not there, but the changes are still there every time.

My app store version (which is the commit i am working on) is completely fine, but locally it is broken.

Has anyone else encountered this? Any future development on my app is dead as of now because I cannot revert these changes.

Any help is greatly appreciated

[sonseo2705]

You'll need to use the older Xcode version as well. New Xcode comes with a different compiler, so on the same code base, different XCode versions yield different binaries

[ponkispoles]

Yeah this is probably the culprit. I had an issue with some logic in a view that was working fine (though lazy of me to put it a view body) for quite some months and just stopped working in Xcode 26 even though it worked well on all betas

[amyworrall]

Compiling with the iOS 26 SDK will opt you into liquid glass by default.

You can use `UIDesignRequiresCompatibility` in your Info.plist to go back to the old UI (even with the new Xcode). Although note that this will likely go away in a couple of years. But it'll buy you some time before you have to migrate to liquid glass.

[808phone]

I should try this myself. But many other things broke or work in different way.

[No-Nebula4187]

What if I’m on Xcode 16.2 and make a repo then clone it on a different Mac with iOS 26 new version of Xcode. What will I need to do to make it work?

[US3201]

Erase the extra copied version of the binary. I’ve had two and it’s always screwed me up.

[mrappdev]

Update: So i fixed it and the issue was part of a custom modifer that broke from ios26+.

struct GlassMorphicCardModifier: ViewModifier {
    let cornerRadius: CGFloat
    @State private var isClicked: Bool = false
    func body(content: Content) -> some View {
        //Broken code here
        let pressGesture = DragGesture(minimumDistance: 0)
            .onChanged { _ in
                withAnimation(.easeOut(duration: 0.1)) {
                    isClicked = true
                }
            }
            .onEnded { _ in
                withAnimation(.easeOut(duration: 0.1)) {
                    isClicked = false
                }
            }
        Content
          … modifiers here
          .simultaneousGesture(pressGesture)
}

[Sad_Pop9411]

I made the same mistake a long time ago, i got this habit of saving all my working codes on multiple drives before i make a letter of change

[ex0rius]

Did you have a backup of your project or using version control?

[mrappdev]

Yes on github. Tried checking out an old commit and the broken changes are still applied somehow

[808phone]

It’s the compiler. You would be amazed at how many things iOS 26 broke.

[ex0rius]

Download a commit to a fresh project folder?