Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shared element transition doesnt work with border radius #6244

Open
jamesheavey opened this issue Jul 9, 2024 · 2 comments
Open

Shared element transition doesnt work with border radius #6244

jamesheavey opened this issue Jul 9, 2024 · 2 comments

Comments

@jamesheavey
Copy link

jamesheavey commented Jul 9, 2024

Description

The shared element transition doesnt work correctly when transitioning from an element with border radius 100 to an element also with radius 100

Link to previous discussion with video

@MatiPl01 @piaskowyk

Steps to reproduce

add a shared element block as below on 2 screens and transition between them

<Animated.Image
    source={{ imageurl }}
    style={{
      width: "100%",
      height: "100%",
      borderRadius: 100
    }}
    sharedTransitionTag={`tag`}
/>

Snack or a link to a repository

https://github.com/MatiPl01/reanimated-set-border-radius-issue

Reanimated version

3.6.1 - 3.13.0

React Native version

0.73.1 - 0.74.3

Platforms

iOS

JavaScript runtime

None

Workflow

None

Architecture

None

Build type

None

Device

None

Device model

No response

Acknowledgements

Yes

@github-actions github-actions bot added Platform: iOS This issue is specific to iOS Missing repro This issue need minimum repro scenario labels Jul 9, 2024
Copy link

github-actions bot commented Jul 9, 2024

Hey! 👋

The issue doesn't seem to contain a minimal reproduction.

Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?

@github-actions github-actions bot added Missing info The user didn't precise the problem enough and removed Missing info The user didn't precise the problem enough labels Jul 9, 2024
@MatiPl01
Copy link
Member

MatiPl01 commented Jul 9, 2024

While I was preparing the repro for the issue, I made this observation. If someone needs a workaround, please look at the proposed temporary solution in the linked discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants