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

The library is not working with the latest expo SDK 46 #80

Open
jimmy123A opened this issue Oct 21, 2022 · 27 comments
Open

The library is not working with the latest expo SDK 46 #80

jimmy123A opened this issue Oct 21, 2022 · 27 comments
Assignees
Labels
bug Something isn't working

Comments

@jimmy123A
Copy link

No description provided.

@jimmy123A jimmy123A added the bug Something isn't working label Oct 21, 2022
@alexZajac
Copy link
Owner

Hey! Can you provide more information to the bug? We have an issue template 👀

@jimmy123A
Copy link
Author

Just make a new expo project with the latest sdk's and u'll see this error msg pops:

TypeError: _ReanimatedModule.default.configureProps is not a function

@igorcesarcode
Copy link

@alexZajac

image

@alexZajac
Copy link
Owner

Thanks for flagging it! I currently have no capacity to fix it, anyone up for a PR?

@igorcesarcode
Copy link

@alexZajac

I found this PR that might be a solution to the problem but as I'm very new to react native I don't know where to start to help with a PR.

Later I will try to follow the description of the PR and give a feedback

software-mansion/react-native-reanimated#3441

@eliusxpol
Copy link

eliusxpol commented Nov 13, 2022

The issue is SDK 46 expects reanimated version ~2.9.1. The current package uses an earlier version of reanimated.
It's very odd that in the v1.0.28 the reanimated version is "react-native-reanimated": "2.1.0" and in the v1.0.25 we have "react-native-reanimated": "^2.9.1".
In v1.0.25 when we run yarn why react-native-reanimated we have this:

=> Found "[email protected]"
info Has been hoisted to "react-native-reanimated"
info This module exists because it's specified in "dependencies".
info Disk size without dependencies: "26.39MB"
info Disk size with unique dependencies: "26.62MB"
info Disk size with transitive dependencies: "34.55MB"
info Number of shared dependencies: 42
=> Found "react-native-skeleton-content#[email protected]"
info This module exists because "react-native-skeleton-content" depends on it.
info Disk size without dependencies: "38.87MB"
info Disk size with unique dependencies: "39.07MB"
info Disk size with transitive dependencies: "46.99MB"
info Number of shared dependencies: 40

@Narottam04
Copy link

Is there any solution to it? I am facing same error when I upgrade my expo SDK from 44 to 45 or 47.

@MarcHbb
Copy link

MarcHbb commented Nov 19, 2022

Same issue with expo 46

@Narottam04
Copy link

This PR helped me solve this problem.
software-mansion/react-native-reanimated#3441

Adjusted resolutions in package.json of react-native-reanimated package. There are also instructions for yarn in pr.

"resolutions": { "react-native-reanimated": "^2.9.1" },

@tyrauber
Copy link

Thanks @Narottam04. I found I needed to provide a resolution for expo-linear-gradient as well as it was already used as a dependency:

  "resolutions": {
    "react-native-reanimated": "^2.12.0",
    "expo-linear-gradient": "~12.0.1"
  }

@alexZajac
Copy link
Owner

Hi all! Is there anything to update on this packages or can we close this?

@Jorundur
Copy link

Jorundur commented Dec 6, 2022

@alexZajac Would it be possible to move the these dependencies in the package.json

    "expo-linear-gradient": "^11.4.0",
    "react-native-reanimated": "2.10.0",

to peerDependencies rather than keep them in dependencies? And also not lock the react-native-reanimated version but rather use ^ instead?

Locking the version always requires Expo users who already have react-native-reanimated to add the resolutions field which is not ideal.

@jakrim
Copy link

jakrim commented Jan 15, 2023

Looking forward to a resolution here (no pun intended) -> resolution in package.json isn't working, getting this error:
TypeError: undefined is not an object (evaluating 'cppVersion.match')

@AndresdoSantos
Copy link

I still can't use it.

I have these dependencies.

"react-native-gesture-handler": "~2.8.0",
"react-native-reanimated": "~2.12.0",
"react-native-skeleton-content": "^1.0.28"

And this resolutions.

"resolutions": {
    "react-native-reanimated": "^2.9.1",
    "expo-linear-gradient": "^12.0.1"
},

And I try to use it like this...

<SkeletonContent
    containerStyle={{ flex: 1, width: 300 }}
    isLoading={!seller}
    layout={[{ key: '1', width: 220, height: 20, marginBottom: 6 }]}
>
    <Header regular="OLÁ" bold={seller!.name} />
</SkeletonContent>

It shows me the following error.

_ReanimatedModule.default.configureProps is not a function

@alex-martino
Copy link

+1 hitting this on latest expo (48)

@reft
Copy link

reft commented Jul 19, 2023

+1 expo 49 uses react-native-reanimated@~3.3.0. Is this package dead?

I was able to use resolutions ^2.14.4 in expo 48 but this solution no longer works because of the major bump on react-native-reanimated in expo 49.

@MarcHbb
Copy link

MarcHbb commented Jul 19, 2023

Just use moti to create your skeleton, it's easy to use. I've drop this package to use moti.
And perform easier animation than reanimated
https://moti.fyi/

@xxcisxxc
Copy link

+1 expo 49 not worked with the above solutions. expo 48 works by the way

@BrajBliss
Copy link

Any fix other than downgrading expo?

@PivaRos
Copy link

PivaRos commented Aug 5, 2023

I have the same issue ):

@max-dealing
Copy link

Same issue here

@tyrauber
Copy link

Echoing @MarcHbb, Moti Skelton is the way to go. Moti is well maintained and supports reanimated v3. Not a 100% drop-in replacement, but an easy migration.

@patrickacioli
Copy link

Guys, instead of just typing "Same issue here", just try to contribute to community and solve that.

@alexZajac
Copy link
Owner

Hi all,

I have some news to share regarding this GitHub repository.

Due to my current capacity constraints, I have made the decision to transfer ownership. This will allow fresh perspectives and new energy to take charge.

If you are interested to take ownership, please reach out!

I also want to express my gratitude for your comments/contributions to the repository!

Thanks!!

@GuidoGagliardini
Copy link

similar behavior in expo SDK 49. I report the error I get.
ERROR TypeError: _ReanimatedModule.default.createNode is not a function (it is undefined), js engine: hermes

@mhr996
Copy link

mhr996 commented Dec 9, 2023

Update this sht or delete it, why are you wasting our time?

@alexZajac
Copy link
Owner

Hi all,

I have some news to share regarding this GitHub repository.

Due to my current capacity constraints, I have made the decision to transfer ownership. This will allow fresh perspectives and new energy to take charge.

If you are interested to take ownership, please reach out!

I also want to express my gratitude for your comments/contributions to the repository!

Thanks!!

Hey, as I said here I don't have the bandwidth at the moment to maintain it.
I started this project years ago to learn and I cannot allocate time to it right now.
If you have the solution ready, I would love to review and merge the PR for everyone else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests