Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MatchedGeometryEffectClipShapeModifierExample buggy behavior

Open
#984 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
swift
Domain
frontend

Research direction

Run ./setup.sh to use Apple's AttributeGraph backend, then set MatchedGeometryEffectClipShapeModifierExample as the root view and reproduce the transition. Compare it with MatchedGeometryEffectModifierExample and trace the clipShape overload and .clipRect rendering path. Done means the clipped content matches SwiftUI's compositing order during the transition and finishes aligned with the destination frame.

Written by the indexing model from the issue text.

Description

area: animation area: rendering contrib: help wanted impact: visual-diff type: bug

Description

MatchedGeometryEffectClipShapeModifierExample does not render the same transition in OpenSwiftUI as it does in SwiftUI. The standard MatchedGeometryEffectModifierExample now behaves correctly, so the remaining problem appears specific to the clipShape overload and .clipRect rendering path.

Reproduction

Due to jcmosc/Compute#60, set up the project with Apple's AttributeGraph backend:

./setup.sh

Do not use ./setup.sh --compute, because the example currently crashes with the Compute/IAG backend.

Then use the clip-shape example as the root view:

struct ContentView: View {
    var body: some View {
        MatchedGeometryEffectClipShapeModifierExample()
    }
}

Run the Example app with OpenSwiftUI.

Expected behavior

The clipped content transitions between the source and destination frames with the same compositing order as SwiftUI, then finishes exactly at the destination frame.

Actual behavior

The transitioning clipped content remains visually on top throughout the animation, and its final rendered position does not align with the destination endpoint.

Dominant language
Swift
Stars
2.5k
Forks
84
Avg merge
2h 8m
Merged PRs (30d)
62

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenSwiftUIProject/OpenSwiftUI

All issues in OpenSwiftUIProject/OpenSwiftUI

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.