Streamlining expo go build

[Ruthvik-1411]

Context:

• To test the feasibility of the application, an apk version of the app was built using dummy data to simulate and test app usage. For this, eas build was used and some modifications to the files like app.json, eas.json and package.json was done.

Issue:

1. Before the eas build and during development phase, to quickly build and test the app in native environment, expo go was used. Simple npx expo start would start the build and using the expo go app, the app would start on the device after bundling.
2. Now, after the eas build was done, running npx expo start would start a development build instead of a expo go build. To start a development build another development build app is required and process got complicated.
3. In the options after npx expo start, there is another option to start as "expo go" build. When used, an expo go build was built and using the app, we have to scan the QR. Previously, clicking on link displayed in app would start the process.
   • But after scanning the app, it would take to another local server site to select the build type to access, as development or expo go.
4. This has made the process more complicated and adds too many unnecessary steps. Had to scan the QR and choose the build again.

[Ruthvik-1411]

Debugging:

1. Related stackoverflow thread: /why-does-my-expo-app-run-in-expo-go-but-not-as-a-development-build
2. Expo build docs: Side effects of expo build

Solution:

• For development phase to go back to initial steps, modify all effected files
  • app.json - revert back to pre eas build version
  • eas.json - delete or remove the file, can be added when eas build next time
  • package.json - remove the expo-dev-client installation

This has resolved the issue and changes have been made in another PR.