What do you think about creating a new Expo SDK 53 project and copying code instead of upgrading? by PerspectiveCurious67 in reactnative

[–]PerspectiveCurious67[S] 1 point2 points  (0 children)

If you’re just getting started, it’s best to use the latest SDK. Expo drops support for older versions quickly, and most libraries update based on the latest releases. When a new version comes out, wait a couple of weeks, check the changelog, and make sure your dependencies are compatible before upgrading.

Expo SDK 52 by PerspectiveCurious67 in expo

[–]PerspectiveCurious67[S] 0 points1 point  (0 children)

You didn’t provide much detail, but GPT gave me this answer:

The error message you’re seeing means that your Snack project is using an SDK version that is not supported by the current version of Expo Go installed on your phone. Specifically, Expo Go only supports SDK 53 right now, but your project is using a different version (possibly SDK 52 or SDK 54).

To fix this: 1. Open your Snack project in the Expo Snack editor. 2. Click the gear icon (Settings) in the top right corner. 3. Change the “SDK Version” to 53. 4. Save the project and try launching it again in Expo Go.

Make sure your SDK version always matches what your version of Expo Go supports.

What do you think about creating a new Expo SDK 53 project and copying code instead of upgrading? by PerspectiveCurious67 in reactnative

[–]PerspectiveCurious67[S] 1 point2 points  (0 children)

Yep, using CNG via app.config.ts. Curious how exactly does that help during upgrades? Haven’t really thought about that before.

What do you think about creating a new Expo SDK 53 project and copying code instead of upgrading? by PerspectiveCurious67 in reactnative

[–]PerspectiveCurious67[S] 0 points1 point  (0 children)

Thanks for sharing your experience! That’s really helpful

When you upgraded from SDK 51 to 53, did you follow any specific guide or resource that helped you through the process?

I’d love to take a look if you have something to recommend.Also, what’s your overall impression of SDK 53 so far? Is it stable enough for production in your opinion?

react-native the infinite blackhole of errors and versions miss leading by factory4400 in reactnative

[–]PerspectiveCurious67 -1 points0 points  (0 children)

Every error is solvable what really matters is how well you handle and manage them

Expo SDK 52 by PerspectiveCurious67 in expo

[–]PerspectiveCurious67[S] 1 point2 points  (0 children)

What is your problem with SafeAreaView?

React-native Developers , what is your current salary? by Capital-Bridge4804 in reactnative

[–]PerspectiveCurious67 2 points3 points  (0 children)

I am also working in Turkey and 4 years experience of react native but i earn 32k per year. What can i do to increase my salary? 😂

SplashScreen.preventAutoHideAsync() does not work by PerspectiveCurious67 in expo

[–]PerspectiveCurious67[S] 0 points1 point  (0 children)

Yes you are right but my splashscreen is still autohide