Unable to set shadowOffset through reanimated
See original GitHub issue<Animated.View
style={[
styles.playBtn,
{
shadowOffset: {
height: interpolate(progress, {
inputRange: [0, 1],
outputRange: [5, 10],
extrapolate: Extrapolate.CLAMP,
}),
width: 0,
},
},
]}
/>
the results
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Reanimated 2 failed to create a worklet, maybe you forgot to ...
I have found this issue on this link. These are the steps that I have followed for having my project up and running...
Read more >In Naruto, can someone who gets reanimated use the multi ...
Simply put, no. People who make shadow clones control how much chakra each one gets. However, splitting it evenly is an excellent way...
Read more >Shadow Atrium | Don't Starve Wiki - Fandom
It is dropped by killing a level 3 Shadow Piece and its only purpose is to revive the Odd Skeleton to spawn a...
Read more >Fixing Reanimate Shadow : r/Shadowverse - Reddit
The problem is the mechanism of the hidden graveyard. That fact that cards can get put in there (through Burial Rite) and taken...
Read more >react-native-reanimated/plugin - You.com | The Search Engine You ...
When I import Animated in my file, no matter I use it somewhere or not, every time it says that Reanimated 2 failed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is related to the wrong handling of nested styles internally.
Repro:
PS. @nasmuris - if you use useRef like that:
useRef(new Animated.Value(0)).current;
it won’t give you much value, because it’s creating and disposing newAnimated.Value
per rerender. Check outuseValue
Fixing this bug requires changing a lot of internal implementation (same problem as in transform node). We discussed it internally and decided to not fix this one - we’re focusing on getting v2 stable in where this problem don’t exist.
We’re open for small PRs though.