Change Details

- Build the app in Android Studio, install on emulator - ``` cd native yarn dev --scheme comm ``` - Press the `a` (or `shift+a` for device select) key in Metro console to open the deeplink. The Comm app should open and skip the Expo launcher screen. Manifest correctness was checked in Android Studio using "merge view": {F336770} Darker is the main manifest, while lighter blue is the debug one.

- Build the app in Android Studio, install on emulator - ``` cd native yarn dev --scheme comm ``` - Press the `a` (or `shift+a` for device select) key in Metro console to open the deeplink. The Comm app should open and skip the Expo launcher screen. Manifest correctness was checked in Android Studio using "merge view": {F336770} Darker is the main manifest, while lighter blue is the debug one. It is also possible to check if Expo's scheme utility uri-scheme detects it correctly: ``` $ npx uri-scheme list --manifest-path ./android/app/src/debug/AndroidManifest.xml › Android: Schemes for config: ./android/app/src/debug/AndroidManifest.xml › comm:// ```

- Build the app in Android Studio, install on emulator - ``` cd native yarn dev --scheme comm ``` - Press the `a` (or `shift+a` for device select) key in Metro console to open the deeplink. The Comm app should open and skip the Expo launcher screen. Manifest correctness was checked in Android Studio using "merge view": {F336770} Darker is the main manifest, while lighter blue is the debug one. It is also possible to check if Expo's scheme utility uri-scheme detects it correctly: ``` $ npx uri-scheme list --manifest-path ./android/app/src/debug/AndroidManifest.xml › Android: Schemes for config: ./android/app/src/debug/AndroidManifest.xml › comm:// ```