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

Update Expo to SDK 51 #226

Closed
h1divp opened this issue Jun 21, 2024 · 0 comments
Closed

Update Expo to SDK 51 #226

h1divp opened this issue Jun 21, 2024 · 0 comments
Assignees
Labels
Frontend 🖥 Issues corresponding to the frontend/client. Medium You should have some familiarity with our codebase to work on this issue URGENT Used for issues that must be fixed ASAP.

Comments

@h1divp
Copy link
Collaborator

h1divp commented Jun 21, 2024

In recent months expo has updated its SDK twice, as well its corresponding apps both available on iOS and Android, which we use for development and testing.

The problem is, these apps cannot be reverted to previous versions which use our current SDK (49). Therefore, anyone who tries to test Echo will not be able to even if they follow all correct procedures for setting up the app for development. Therefore two full SDK updates will be needed (yes, sequentially) with necessary package upgrades. The fixing of this issue is vital for continuing easy development and onboarding to Echo.

Current workaround

Currently the only known workaround to develop the app is done by installing an SDK 49 version of the Expo mobile app on a simulated android phone, in android studio. Maybe you can find a way to use this on a regular android phone, but I believe the certificate for the version has expired and is not able to be installed on most devices.

Task

Please follow expo documentation and update the SDK version of our frontend app sequentially. Update all necessary NPM packages to their required versions. Once you have the app working in the most current version, please take note of any bugs from the upgrade and mention them in the PR. These may be created as subsequent issues.

@h1divp h1divp added Frontend 🖥 Issues corresponding to the frontend/client. Medium You should have some familiarity with our codebase to work on this issue URGENT Used for issues that must be fixed ASAP. labels Jun 21, 2024
@h1divp h1divp self-assigned this Jun 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Frontend 🖥 Issues corresponding to the frontend/client. Medium You should have some familiarity with our codebase to work on this issue URGENT Used for issues that must be fixed ASAP.
Projects
Development

No branches or pull requests

2 participants