[iOS][Android] Upgrade react-navigation to v6 (#19452)

# Why

Closes ENG-4149.
Closes ENG-4150.
Closes ENG-4160.

The react-navigation v5 doesn't work with the react-native 0.70. So, I've migr

[iOS][Android] Upgrade react-navigation to v6 (#19452)

# Why

Closes ENG-4149.
Closes ENG-4150.
Closes ENG-4160.

The react-navigation v5 doesn't work with the react-native 0.70. So, I've migrated NCL and Home to use v6.

# How

- Bumped versions of related packages.
- Went through the migration guide.
- Disable react-native-screens integration on Android in Home.

> Note:
I'm aware of [proposed fix](https://github.com/expo/expo/pull/16333) which fixes integration between screens and navigation on Android. However, I'm not sure if that change is safe. That's why, for now, `react-native-screens` were disabled.

# Test Plan

- expo-go - home ✅
- expo-go - NCL ✅
- bare-expo - NCL ✅

show more ...

Revert "[ncl] Upgrade `@react-navigation` to v6 (#18055)" (#18088)

This reverts commit 429c2b9a30e278e71fb24325904e270e0c2fe235.

# Why

fix test-suite ci failures. the root cause is that our wo

Revert "[ncl] Upgrade `@react-navigation` to v6 (#18055)" (#18088)

This reverts commit 429c2b9a30e278e71fb24325904e270e0c2fe235.

# Why

fix test-suite ci failures. the root cause is that our workspace is not super healthy to support different react-navigation. the bare-expo has a navigator directly reference to NCL but its react-navigation version references to workspace, i.e. react-navigation@5.

the react-navigation@5 from bare-expo cannot understand [react-navigation@6 options in NCL](https://github.com/expo/expo/commit/429c2b9a30e278e71fb24325904e270e0c2fe235#diff-5feeb01132a342be8b3a58513838ca4bf972e7d4acb4b2509112de13cba19c51R61-R62) and causes error.

# How

`git revert 429c2b9a30e278e71fb24325904e270e0c2fe235`

# Test Plan

test suite ci pass

show more ...

[ncl] Upgrade `@react-navigation` to v6 (#18055)

[ncl] lazy load components and improve startup (#12503)

* lazy load screens

* fix up test suite

* load less icons

* lint fix

* Update AppNavigator.js

* fix tsc

* Create debugging.w

[ncl] lazy load components and improve startup (#12503)

* lazy load screens

* fix up test suite

* load less icons

* lint fix

* Update AppNavigator.js

* fix tsc

* Create debugging.web.ts

* updated pods

show more ...

Migrate to react-navigation v5 (#8857)

* Migrate apps/ to use react-navigation v5

* Update GeofencingScreen.tsx

* Update GeofencingScreen.tsx

* Updated useFocusEffect

* Update MediaLibra

Migrate to react-navigation v5 (#8857)

* Migrate apps/ to use react-navigation v5

* Update GeofencingScreen.tsx

* Update GeofencingScreen.tsx

* Updated useFocusEffect

* Update MediaLibraryScreen.tsx

* Update GeofencingScreen.tsx

* Updated onFocus methods

* Update BackgroundLocationMapScreen.tsx

* Fix tab loading

* Update ExpoComponents.ts

* Updated Media Library

* fix bare-expo routing in e2e

* Update TaskManagerScreen.tsx

* Improve linking configuration

* Update MainNavigator.tsx

* Updated prop signature

* Update MainNavigator.tsx

Co-authored-by: Brent Vatne <[email protected]>

show more ...

[chore] Fix lint and typescript errors in NCL (#8861)

* Fix lint errors

* Revice web unimplemented views

* Delete useDimensions.ts

* Remove unused screen object properties

* Convert to f

[chore] Fix lint and typescript errors in NCL (#8861)

* Fix lint errors

* Revice web unimplemented views

* Delete useDimensions.ts

* Remove unused screen object properties

* Convert to functional components

* Fix TypeScript errors

* Fix subscription bug

show more ...

[ncl] Fix native-component-list assets not loaded in bare-expo (#7342)

* [bare-expo] Fix native-component-list assets not loaded in bare-expo

* [bare-expo] Fix asset errors on API tab

[ncl] Fix Roboto's download link to specific commit (#8302)

# Why

Just recently the Roboto font has been moved inside the `google/fonts` repository from where we download the Roboto font when ope

[ncl] Fix Roboto's download link to specific commit (#8302)

# Why

Just recently the Roboto font has been moved inside the `google/fonts` repository from where we download the Roboto font when opening NCL. This has resulted in an error.

# How

Replaced the `master` pointer to a specific commit so that this situation does not happen again.

# Test Plan

Loaded NCL with this change successfully.

show more ...

[bare-expo][ncl] Add native-component-list to bare-expo (#6868)

# Why

Make it easier to test things on both workflows at the same time.

# How

- Added `native-component-list` as a dependency

[bare-expo][ncl] Add native-component-list to bare-expo (#6868)

# Why

Make it easier to test things on both workflows at the same time.

# How

- Added `native-component-list` as a dependency of `bare-expo`.
- Updated `app.json` config for web as now we need to tell babel to transpile files from NCL.
- Resolved some issues caused by the fact that NCL was intended for use in managed workflow.
- Added new bottom tab bar navigator for switching between TestSuite, Expo APIs and Expo Components.
- Removed `standalone-ncl` app - it's useless now.

# Test Plan

- [x] Test bare-expo on mobile
- [x] Test bare-expo on web
- [x] Test native-component-list on mobile
- [x] CI tests are passing

I haven't tested whether every NCL screen works inside BareExpo, hopefully we will be fixing them separately once we use those screens.

# Demo


# Proposals for improvements in the future

- Create `managed-expo` app that is actually the same as `bare-expo` but for managed workflow. That would make it really easy to debug every thing in both workflow at once.
- Add the possibility to exclude `native-component-list` when running on the CI - with NCL it takes a bit more time to load the page.
- I noticed the first tests (Basic) are taking much more time than subsequent ones and I guess it's because the first `page.goto` call triggers webpack to start bundling the app and until then we don't receive any response. Maybe we should open that page at the root path before running tests and give it as much time as it needs to and thus prevent timeouts in the first tests ��

show more ...