Feature react native tracer provider

.github/workflows/android.unit-test.yml

@@ -0,0 +1,54 @@
+name: Android Unit Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [18.x]
+        jdk-version: ["17"]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Install Node (${{ matrix.node-version }})
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: "npm"
+
+      - name: Enables corepack
+        run: corepack enable
+
+      - uses: dorny/paths-filter@v2
+        id: changed_files
+        with:
+          list-files: shell
+          filters: |
+            android:
+            - 'packages/**/gradle.properties'
+            - 'packages/**/*.gradle'
+            - 'packages/**/*.kt'
+            - 'packages/**/*.java'
+
+      - name: Install Root Node Modules
+        run: yarn install
+        if: steps.changed_files.outputs.android == 'true'
+
+      - name: Install JDK ${{ matrix.jdk-version }}
+        uses: actions/setup-java@v4
+        with:
+          distribution: 'adopt'
+          java-version: ${{ matrix.jdk-version }}
+        if: steps.changed_files.outputs.android == 'true'
+
+      - name: Run Android Unit Tests
+        run: yarn run android:test $(./scopes-from-file-changes.ts ${{ steps.changed_files.outputs.android_files }})
+        if: steps.changed_files.outputs.android == 'true'

.prettierignore

@@ -1,3 +1,4 @@
 node_modules
 build
 dist
+Pods

DEVELOPING.md

@@ -34,7 +34,7 @@ yarn lint
 yarn test
 ```
 
-## Manual integration testing
+## Manual integration testing (TODO update after changes to integration testing workflow)
 
 The [example app](examples/react-native-test-suite/) allows you to test out the React Native Embrace SDK in a representative app.
 
@@ -74,7 +74,7 @@ pushd ios; pod install; popd;
 yarn ios --mode=Release
 ```
 
-## Testing against new Embrace Android SDK versions
+## Testing against new Embrace Android SDK versions (TODO update after changes to integration testing workflow)
 
 You can test Embrace Android SDK changes by altering the dependency in the core package's [build.gradle](./packages/core/android/build.gradle).
 And then either publish a local artifact or if you need CI to pass - publish a beta:
@@ -94,7 +94,7 @@ And then either publish a local artifact or if you need CI to pass - publish a b
 4. Set the correct `embrace-android-sdk` version in `examples/react-native-test-suite/node_modules/embrace-io/android/build.gradle`
 5. Run the app in the normal way
 
-## Testing against new Embrace iOS SDK versions
+## Testing against new Embrace iOS SDK versions (TODO update after changes to integration testing workflow)
 
 ### Local artifact
 
@@ -111,6 +111,12 @@ You can test local changes to the iOS SDK by updating the example app's `podspec
 3. In `examples/react-native-test-suite/ios/Podfile`, add the following line `pod 'EmbraceIO-DEV'`
 4. In `examples/react-native-test-suite/ios`, run the `pod update` command
 
+## Updating native SDK dependencies
+
+1. Bump the Android (SDK + Swazzler)/iOS dependencies to the latest available stable versions in `./yarn.config.cjs`
+2. Run `yarn constraints --fix` to propagate this change to all package.json files
+3. Run `yarn build` to update build files to the latest versions
+
 ## Automated integration testing
 
 Automated integration testing is being actively developed to replace some of the manual testing outlined above, see [here](./integration-tests/README.md) for more details.
@@ -132,4 +138,4 @@ unreleased changes on `main` and a patch release will be cut from that new branc
 7. Run an example app and point to the latest released packages to confirm basic behaviour
 8. Update and publish the [Changelog](https://github.com/embrace-io/embrace-docs/blob/main/docs/react-native/changelog.md) for the release
 
-NOTE: If you make a mistake while publishing you can remove the specific version w/ `npm unpublish <package-name>@<version>`, see [Unpublishing a single version of a package](https://docs.npmjs.com/unpublishing-packages-from-the-registry#unpublishing-a-single-version-of-a-package)
+NOTE: If you make a mistake while publishing you can remove the specific version w/ `npm unpublish <package-name>@<version>`, see [Unpublishing a single version of a package](https://docs.npmjs.com/unpublishing-packages-from-the-registry#unpublishing-a-single-version-of-a-package)

integration-tests/README.md

@@ -6,33 +6,33 @@ verifications on the payloads that would have been sent to Embrace.
 The harness uses WebdriverIO's [Testrunner](https://webdriver.io/docs/testrunner/) to spin up a [Appium](http://appium.io/docs/en/latest/intro/) client and server to perform the device automation. [Mockserver](https://www.mock-server.com/#what-is-mockserver) is
 launched for the suite run so that requests sent from the device can be inspected.
 
-```bash
-npm install
-```
+    ```bash
+    npm install
+    ```
 
 For any future updates the [Appium Installer](https://webdriver.io/docs/appium) provides a handy setup wizard:
 
-```bash
-npx appium-installer
-```
+    ```bash
+    npx appium-installer
+    ```
 
 ## Run tests
 
 Make sure the test apps have the latest local @embrace-io/react-native changes:
 
-```bash
-npm run update-local-embrace
-```
+    ```bash
+    npm run update-local-embrace
+    ```
 
 Make sure the test apps are installed on the device/emulator before running tests. Note that building the debug variant
 of the app may interfere with the tests as the debug menu gets in the way of UI elements.
 
 Android can run in release mode:
 
-```bash
-cd basic-test-app
-npx expo run:android --variant release
-```
+    ```bash
+    cd basic-test-app
+    npx expo run:android --variant release
+    ```
 
 For ios it doesn't apply the `--variant release` mode, so we can do it through xcode:
 
@@ -41,17 +41,17 @@ For ios it doesn't apply the `--variant release` mode, so we can do it through x
 - Under the Run section, change the Build Configuration from Debug to Release.
 - Press Cmd + R to build and run the app in release mode.
 
-or simple run 
+or simply run 
 
-```bash
-npx expo run:ios --configuration Release
-```
+    ```bash
+    npx expo run:ios --configuration Release
+    ```
 
 Run the test suite:
 
-```bash
-npm test
-```
+    ```bash
+    npm test
+    ```
 
 ## Debugging tips
 
@@ -60,11 +60,11 @@ npm test
 To help figure out the selectors to use for grabbing UI elements it can be useful to interact with Appium using
 the Appium Inspector. First install the Appium server and drivers globally:
 
-```bash
-npm install -g appium
-appium driver install uiautomator2 # android / ios
-appium driver install xcuitest # ios
-```
+    ```bash
+    npm install -g appium
+    appium driver install uiautomator2 # android / ios
+    appium driver install xcuitest # ios
+    ```
 
 Then install [Appium Inspector](https://github.com/appium/appium-inspector)
 
@@ -73,12 +73,30 @@ Then install [Appium Inspector](https://github.com/appium/appium-inspector)
 You can invoke the Mockserver and watch its output directly to get a look at the payloads it is receiving at different
 endpoints (Note this may include some binary output that doesn't play nice with your terminal):
 
-```bash
-npx tsx helpers/invoke_embrace_server.ts
-```
+    ```bash
+    npx tsx helpers/invoke_embrace_server.ts
+    ```
 
 ## CI
 
 TODO for the moment the utility here is to be able to run tests locally during development, as a next task need to hook this up to
 CI tools to verify a passing suite for new releases. Likely this means updating or creating a new `wdio.conf.ts` that
 can be configured to point to a remote environment. See what capabilities are available for that [here](https://appium.io/docs/en/2.1/guides/caps/)
+
+## Troubleshooting
+
+
+### Appium gives 500 during test run
+
+"Could not proxy command to remote server. Original error: Error: socket hang up"
+
+Try:
+    ```bash
+    # Android
+    adb uninstall io.appium.uiautomator2.server
+    adb uninstall io.appium.uiautomator2.server.test
+
+    # iOS
+    xcrun simctl uninstall booted io.appium.uiautomator2.server
+    xcrun simctl uninstall booted io.appium.uiautomator2.server.test
+    ```

integration-tests/artifacts/.gitignore

@@ -1 +1 @@
-*.tgz
+*-local.tgz

integration-tests/basic-test-app/README.md

@@ -70,11 +70,12 @@ Use the following when creating `./ios/Embrace-Info.plist`:
 Then build:
 
    ```bash
-    npx expo run:ios
+   pushd ios; pod install; popd
+   npx expo run:ios
    ```
 
 ## Pull in local @embrace-io/react-native changes
 
 Because RN doesn't support symlinked packages whenever any changes are made under
 packages/core (or any other local package that the test app depends on) they need to be copied into
-the app's node_modules/, there is a script in integration-tests that manages this
+the app's node_modules/, there is a script in integration-tests that manages this

integration-tests/basic-test-app/android/app/src/main/AndroidManifest.xml

@@ -11,7 +11,7 @@
       <data android:scheme="https"/>
     </intent>
   </queries>
-  <application android:name=".MainApplication" android:label="@string/app_name" android:icon="@mipmap/ic_launcher" android:roundIcon="@mipmap/ic_launcher_round" android:allowBackup="true" android:theme="@style/AppTheme">
+  <application android:name=".MainApplication" android:label="@string/app_name" android:icon="@mipmap/ic_launcher" android:roundIcon="@mipmap/ic_launcher_round" android:allowBackup="true" android:theme="@style/AppTheme" android:networkSecurityConfig="@xml/network_security_config">
     <meta-data android:name="expo.modules.updates.ENABLED" android:value="false"/>
     <meta-data android:name="expo.modules.updates.EXPO_UPDATES_CHECK_ON_LAUNCH" android:value="ALWAYS"/>
     <meta-data android:name="expo.modules.updates.EXPO_UPDATES_LAUNCH_WAIT_MS" android:value="0"/>

integration-tests/basic-test-app/android/app/src/main/res/xml/network_security_config.xml

@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="utf-8"?>
+<network-security-config>
+    <base-config cleartextTrafficPermitted="true" />
+</network-security-config>

integration-tests/basic-test-app/app/(tabs)/_layout.tsx

@@ -17,7 +17,8 @@ export default function TabLayout() {
       <Tabs.Screen
         name="index"
         options={{
-          title: "Home",
+          title: "HOME",
+          tabBarAccessibilityLabel: "HOME",
           tabBarIcon: ({color, focused}) => (
             <TabBarIcon
               name={focused ? "home" : "home-outline"}
@@ -27,14 +28,12 @@ export default function TabLayout() {
         }}
       />
       <Tabs.Screen
-        name="explore"
+        name="second"
         options={{
-          title: "Explore",
+          title: "SECOND SCREEN",
+          tabBarAccessibilityLabel: "SECOND SCREEN",
           tabBarIcon: ({color, focused}) => (
-            <TabBarIcon
-              name={focused ? "code-slash" : "code-slash-outline"}
-              color={color}
-            />
+            <TabBarIcon name={"radio"} color={color} />
           ),
         }}
       />