Migrating to EAS build cannot get App to start.

I am trying to migrate to the EAS build system but encounter a runtime error when starting the app. The build completes without any errors. However when starting the app it immediately fails.

I have error logs from sentry and adb logcat which indicate there is a module failing during initialization. When building the application locally using expo run:android I get the exact same behavior but no extra clues as to where the problem actually is.

I have run the app locally with a dev client build hoping to get a better stack trace. I received the same start up error with some additional information regarding a missing project ID when creating the AuthSession proxy. I worked around this issue to get the dev client build working locally and then built this version through EAS. However the app still did not start.
Error cannot use AuthSession proxy because the Project ID is not defined

I have created a repo to reproduce the issue which includes my package.json.

Here is my environment infromation:
Expo CLI 5.0.3 environment info:
OS: Linux 5.13 Ubuntu 21.10 21.10 (Impish Indri)
Shell: 5.1.8 - /bin/bash
Node: 16.13.0 - /usr/local/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 8.3.2 - /usr/local/bin/npm
babel-preset-expo: 8.5.1 => 8.5.1
expo: ^43.0.0 => 43.0.5
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
eas-cli: 0.45.1
expo-cli: 5.0.3
Expo Workflow: managed

Any help would be much appreciated.

Fixed this issue by including the following in my app.json. I noticed the difference in app.json structure when I created a new expo project and comparing.