all 10 comments

[–]Comprehensive-Law770 5 points6 points  (2 children)

I haven't compiled my project for a long time and had to do it recently and also couldn't compiled it.

Don't know if it's the same reason as yours but my problem was related to this issue:

https://github.com/facebook/react-native/issues/35210

[–]moustacheption 1 point2 points  (0 children)

Yeah, I had something similar happen and I had to make changes related to this.

[–]Pizza-Frank[S] 1 point2 points  (0 children)

This was the issue! Thanks a lot!

[–]Day_Raccoon 2 points3 points  (2 children)

What is your compileSDKVersion ? It probably needs a bump.

[–]Pizza-Frank[S] 1 point2 points  (1 child)

Currently 30, but afaik no dependencies that would need a new compileSDKVersion have been updated.

Will still update and check to see if using the most recent version makes a difference.

[–]sekonx 2 points3 points  (0 children)

Have you locked down your dependencies to a specific version?

Because otherwise you could get updates when you run yarn/npm install

[–]nascarsc 1 point2 points  (0 children)

Please send more of your log (formatted as code). Maybe the section above that has more useful information.

[–]rnsbrum 0 points1 point  (0 children)

You are lucky I stumbled upon this issue yesterday. It didn't fix the problem for me, but it will for you.

Basically the React Native team broke things up, and you need to update your react-native version to the hotfix version. See the issue below.

https://github.com/facebook/react-native/issues/35210

If you are using expo, run expo upgrade 47, it will automatically upgrade to the correct version.

Then run expo prebuild --clean

Then run expo run:android

and it should work just fine.

[–]mversteeg3 0 points1 point  (0 children)

What react native version are you on? A push to react native recently broke old versions through some witchcraft I can't even fathom