Forced update 39~41?

Please provide the following:

  1. SDK Version: 39
  2. Platforms(Android/iOS/web/all): all
  3. Add the appropriate “Tag” based on what Expo library you have a question on.

I developed a project 1 year ago on SDK 39, today it is not only fully deprecated but the documentation is no longer available, I need to add a new functionality, and I’m trying to update the expo, react, all packages, refactor the entire application and fixing all the bugs, a new feature that should have taken 1~2 days of my life became 15~20 days because I would have to update everything.

The question is why? what does it cost to keep the documentation longer? the documentation is nothing less than HTML, the same applies to the mobile app “Expo go”, I’m having to download an APK from the internet to be able to test it, what’s the problem with putting a greater compatibility of SDK’s in the APP?
1 YEAR is too little for an in-house app to be deprecated and need to be completely refactored. and I’m talking about 1 app… can you imagine people who have 5~20 apps published, and need to add something to them? without documentation.

documentation is in public repo you can access older versions any time

what’s the problem with putting a greater compatibility of SDK’s in the APP?

keeping multiple versions of the same library in one app is very complicated and costly to maintain, and if there are architectural changes introduced sometimes we need to make changes to all supported sdk to keep it working.

1 YEAR is too little for an in-house app to be deprecated and need to be completely refactored

why would you need to completely refactor? Migrating from sdk to sdk is relatively easy, I recommend doing it regularly not just once a year. Even in case of significant architectural changes from user perspective it’s usually just replacing one package with another. There are sometimes not trivial breaking changes, but in most cases it’s required to e.g. support new android/ios version or some new policy in store.

I don’t recommend that, but if you want to stay on one SDK with eas it will be possible to just build custom dev client and use it instead of expo go, (SDK 39 was before EAS build existed, so you still need to update this time).