Repository: alttester/AltTester-Unity-SDK (language: python)

Issue:
1156-change required from doc in master

[Documentation - FAQ] Include workaround for case where using only Input Manager (Old) with AltTester
<!-- Short summary -->

## Description
<!-- Describe shortly: What does this feature do? Why is it needed? --> 
There is a case where users don't want to use the Input System (New) in their project so they get errors after importing the AltTester package.

**Solution**: We need to include in the FAQ section of the documentation the workaround for them to be able to use `AltTester Unity SDK` in their project when they don't want to use the Input System (New)  :
- **delete**:
    - `Assets\AltTester\AltServer\NewInputSystem.cs` 
    - `Assets\AltTester\AltServer\AltKeyMapping.cs`
- **comment** in `Assets\AltTester\AltServer\AltPrefabDrag.cs`  the entire `#else` statement
    ![image](https://user-images.githubusercontent.com/62327834/218444762-92ff2751-fc68-42c0-8f12-647891299987.png)

- **comment** in `Assets\AltTester\AltServer\Input.cs` :
    - all imports for `using UnityEngine.InputSystem.UI`
    - all `if` lines that contain `InputSystemUIInputModule` and the curly brackets inside these `if` statements making sure to leave the code inside the brackets uncommented
        ![image](https://user-images.githubusercontent.com/62327834/218435800-3973092c-3020-4d45-94bc-e7df7ed26fe8.png)
- in `Assets\AltTester\AltServer\AltMockUpPointerInputModule.cs` do the same as the above

## Mocks
<!-- Ex.: add mocks related to how the UX should look like with this feature. --> 

## Additional info
<!-- Add any additional info that could be of help like links to docs, resources etc. -->
- Workaround for https://github.com/alttester/AltTester-Unity-SDK/issues/1102
- should include some code examples for the commented code


Discussion / hints:

Fix patch:
diff --git a/.github/workflows/push.yml b/.github/workflows/push.yml
index fb37735a0..ae6582d74 100644
--- a/.github/workflows/push.yml
+++ b/.github/workflows/push.yml
@@ -17,23 +17,23 @@ jobs:
       docs: ${{ steps.filter.outputs.docs }}
       scenes: ${{steps.filter.outputs.scenes}}
     steps:
-    - uses: actions/checkout@v2
-    - uses: dorny/paths-filter@v2
-      id: filter
-      with:
-        filters: |
-          java:
-            - 'Bindings~/java/**'
-          python:
-            - 'Bindings~/python/**'
-          csharp:
-            - '**.cs' 
-          editor:
-            - '**.cs'
-          docs:
-            - 'Docs/**'
-          scenes:
-            - 'Assets/AltTester/Examples/Scenes/**'
+      - uses: actions/checkout@v2
+      - uses: dorny/paths-filter@v2
+        id: filter
+        with:
+          filters: |
+            java:
+              - 'Bindings~/java/**'
+            python:
+              - 'Bindings~/python/**'
+            csharp:
+              - '**.cs' 
+            editor:
+              - '**.cs'
+            docs:
+              - 'Docs/**'
+            scenes:
+              - 'Assets/AltTester/Examples/Scenes/**'
 
   build-docs:
     runs-on: ubuntu-latest
@@ -282,16 +282,15 @@ jobs:
         with:
           name: TestPythonAndroidInBrowserstackArtifact
           path: "**/*.log"
-      
+
       - name: Unset Browserstack Flag
         if: always()
         run: |
           export RUN_ANDROID_IN_BROWSERSTACK="false"
-        
+
   deploy-dev-docs:
     runs-on: ubuntu-latest
     needs: build-docs
-
     if: github.ref == 'refs/heads/development'
 
     steps:
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 56c61cf80..76195c6ae 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -1,18 +1,19 @@
 name: release
 
 on:
+  workflow_dispatch:
   release:
     types: [published]
 
 jobs:
   publish-pip-package:
-    runs-on: ubuntu-18.04
+    runs-on: [self-hosted, macOS]
 
     steps:
       - uses: actions/checkout@v3
       - uses: actions/setup-python@v4
         with:
-          python-version: '3.10'
+          python-version: "3.10"
 
       - name: Install dependencies
         run: |
@@ -26,7 +27,7 @@ jobs:
           python3 -m twine upload dist/*
 
   publish-nuget-package:
-    runs-on:  ubuntu-18.04
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v3
 
@@ -39,10 +40,10 @@ jobs:
         run: |
           cd "Bindings~/dotnet"
           dotnet pack AltDriver/AltDriver.csproj -c release
-          dotnet nuget push AltDriver/bin/release/AltTester-Driver.2.0.0.nupkg --api-key $NUGET_DEPLOY_KEY --source https://api.nuget.org/v3/index.json
+          dotnet nuget push AltDriver/bin/release/AltTester-Driver.2.0.1.nupkg --api-key $NUGET_DEPLOY_KEY --source https://api.nuget.org/v3/index.json
 
   create-unity-package:
-    runs-on: ubuntu-18.04
+    runs-on: [self-hosted, macOS]
     steps:
       - name: Create Unity Package
         run: |
@@ -54,6 +55,23 @@ jobs:
           cp $AUT public/AltTester/AltTester.unitypackage
           cp $AUT public/AltTester/AltTester_2_0_0.unitypackage
           cp SampleScenes.unitypackage public/AltTester/SampleScene.unitypackage
+      - uses: actions/upload-artifact@v3
+        with:
+          name: AltTester
+          path: public/AltTester
+
+  upload-unity-package:
+    runs-on: ubuntu-latest
+    needs: create-unity-package
+
+    steps:
+      - uses: actions/checkout@v3
+
+      - uses: actions/download-artifact@v3
+        with:
+          name: AltTester
+          path: public/AltTester
+
       - name: Upload AltTesterPackage
         uses: garygrossgarten/github-action-scp@release
         with:
@@ -63,20 +81,25 @@ jobs:
           port: ${{ secrets.PORT_LIVE_ALTTESTER }}
           username: ${{ secrets.USERNAME_ALTTESTER }}
           password: ${{ secrets.PASSWORD_DEV_ALTTESTER }}
-      - name: Delete Public
-        if: always()
-        run: rm -r public
 
   create-jar-archive:
-    runs-on: ubuntu-18.04
+    runs-on: ubuntu-latest
     steps:
       - name: Setup Java JDK
         uses: actions/setup-java@v3.5.1
         with:
-              distribution: temurin
-              java-version: 11
+          distribution: temurin
+          java-version: 11
 
       - uses: stCarolas/setup-maven@v4.4
+      - name: Create jar
+        run: |
+          ls
+          mkdir -p public/AltTesterJAR || true
+          ls
+          cd "Bindings~/java"
+          mvn clean compile assembly:single
+          mv target/alttester-jar-with-dependencies.jar ../../public/AltTesterJAR/AltTester-Driver.jar
 
       - name: Create jar
         run: |
@@ -85,6 +108,23 @@ jobs:
           mvn clean compile assembly:single
           mv target/alttester-jar-with-dependencies.jar ../../public/AltTesterJAR/AltTester-Driver.jar
 
+      - uses: actions/upload-artifact@v3
+        with:
+          name: AltTesterJAR
+          path: public/AltTesterJAR
+
+  upload-java-jar:
+    runs-on: ubuntu-latest
+    needs: create-jar-archive
+
+    steps:
+      - uses: actions/checkout@v3
+
+      - uses: actions/download-artifact@v3
+        with:
+          name: AltTesterJAR
+          path: public/AltTesterJAR
+
       - name: Upload AltTester Jar
         uses: garygrossgarten/github-action-scp@release
         with:
@@ -94,12 +134,9 @@ jobs:
           port: ${{ secrets.PORT_LIVE_ALTTESTER }}
           username: ${{ secrets.USERNAME_ALTTESTER }}
           password: ${{ secrets.PASSWORD_DEV_ALTTESTER }}
-      - name: Delete Public
-        if: always()
-        run: rm -r public
 
   java-release:
-    runs-on: ubuntu-18.04
+    runs-on: ubuntu-latest
     steps:
       - name: Check out Git repository
         uses: actions/checkout@v2
@@ -119,4 +156,4 @@ jobs:
           nexus_username: ${{ secrets.nexus_username }}
           nexus_password: ${{ secrets.nexus_password }}
           directory: Bindings~/java/
-          maven_args: -f pom-release.xml -DskipTests
+          maven_args: -f pom-release.xml -Dmaven.test.skip=true
diff --git a/Assets/AltTester/Examples.meta b/Assets/AltTester/Examples.meta
new file mode 100644
index 000000000..2988c1522
--- /dev/null
+++ b/Assets/AltTester/Examples.meta
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: b40ab3f47f6dd874da501c024c38a4db
+folderAsset: yes
+DefaultImporter:
+  externalObjects: {}
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
diff --git a/Assets/AltTester/Examples/Test.meta b/Assets/AltTester/Examples/Test.meta
new file mode 100644
index 000000000..772547d5b
--- /dev/null
+++ b/Assets/AltTester/Examples/Test.meta
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: d6d41ec8d20fbc04b84a60312dea3a77
+folderAsset: yes
+DefaultImporter:
+  externalObjects: {}
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
diff --git a/Assets/AltTester/Examples/Test/Editor.meta b/Assets/AltTester/Examples/Test/Editor.meta
new file mode 100644
index 000000000..67dc780b1
--- /dev/null
+++ b/Assets/AltTester/Examples/Test/Editor.meta
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: c808e452010aaf1458f343664cf14730
+folderAsset: yes
+DefaultImporter:
+  externalObjects: {}
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
diff --git a/Assets/AltTester/Examples/Test/Editor/Driver.meta b/Assets/AltTester/Examples/Test/Editor/Driver.meta
new file mode 100644
index 000000000..941c008a1
--- /dev/null
+++ b/Assets/AltTester/Examples/Test/Editor/Driver.meta
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: 574d1c3b6c3f47247bfe5ab30f2f8cb8
+folderAsset: yes
+DefaultImporter:
+  externalObjects: {}
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
diff --git a/Bindings~/java/pom-release.xml b/Bindings~/java/pom-release.xml
index cfb1964c9..f6f3db55f 100644
--- a/Bindings~/java/pom-release.xml
+++ b/Bindings~/java/pom-release.xml
@@ -23,8 +23,8 @@
         <developer>
             <name>Robert Poienar</name>
             <email>robert.poienar@altom.com</email>
-            <organization>Altom</organization>
-            <organizationUrl>http://altom.com/</organizationUrl>
+            <organization>AltTester</organization>
+            <organizationUrl>https://alttester.com/</organizationUrl>
         </developer>
     </developers>
 
@@ -167,7 +167,7 @@
     </profiles>
 
     <build>
-        <finalName>${artifactId}</finalName>
+        <finalName>${project.artifactId}</finalName>
         <plugins>
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
diff --git a/Bindings~/python/README.md b/Bindings~/python/README.md
index e8fd4b755..9aa71e748 100644
--- a/Bindings~/python/README.md
+++ b/Bindings~/python/README.md
@@ -14,8 +14,8 @@ Check out the [Get Started](https://alttester.com/docs/pro/sdk/pages/get-started
 
 ## Development
 
-* Code Style: [PEP-0008](https://www.python.org/dev/peps/pep-0008/)
-* Docstring style: [Google Style Docstrings](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html).
+-   Code Style: [PEP-0008](https://www.python.org/dev/peps/pep-0008/)
+-   Docstring style: [Google Style Docstrings](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html).
 
 ### Running Tests
 
diff --git a/Docs/source/pages/contributing.md b/Docs/source/pages/contributing.md
index b8bc886cc..c4da0f026 100644
--- a/Docs/source/pages/contributing.md
+++ b/Docs/source/pages/contributing.md
@@ -15,32 +15,32 @@ If you’re unable to find an open issue addressing the problem, open a [new iss
 
 Try to:
 
-* Use as little code as possible that still produces the same problem.
-* Provide all parts needed to reproduce the problem (code and model if needed).
-* Test the code you’re about to provide to make sure it reproduces the problem.
+-   Use as little code as possible that still produces the same problem.
+-   Provide all parts needed to reproduce the problem (code and model if needed).
+-   Test the code you’re about to provide to make sure it reproduces the problem.
 
 ## How to suggest a feature or enhancement?
 
 If you find yourself wishing for a feature that doesn’t exist in AltTester Unity SDK:
 
-* Ensure the enhancement was not already reported by searching all issues.
-* Open a [new issue](https://github.com/alttester/AltTester-Unity-SDK/issues/new?assignees=&labels=&template=feature-request.md&title=). Be sure to include a clear description of the feature you would like to see, as much relevant information as possible:
-  * Why you need it?
-  * How should it work?
+-   Ensure the enhancement was not already reported by searching all issues.
+-   Open a [new issue](https://github.com/alttester/AltTester-Unity-SDK/issues/new?assignees=&labels=&template=feature-request.md&title=). Be sure to include a clear description of the feature you would like to see, as much relevant information as possible:
+    -   Why you need it?
+    -   How should it work?
 
 ## Contributing changes
 
 When you create a pull request take in consideration the following:
 
-* Respect the project structure
-* If it is a new feature like a new command try to make it for all three languages (Java, C# and Python) and also add tests
-* If it is a bugfix then write a test to show that the bug is no longer reproducible
+-   Respect the project structure
+-   If it is a new feature like a new command try to make it for all three languages (Java, C# and Python) and also add tests
+-   If it is a bugfix then write a test to show that the bug is no longer reproducible
 
 ### Preparing your Fork
 
-* Click ‘Fork’ on GitHub, creating e.g. `yourname/AltTester-Unity-SDK`.
-* Clone your forked repository: `git clone git@github.com:yourname/AltTester-Unity-SDK`.
-* `cd AltTester-Unity-SDK`
+-   Click ‘Fork’ on GitHub, creating e.g. `yourname/AltTester-Unity-SDK`.
+-   Clone your forked repository: `git clone git@github.com:yourname/AltTester-Unity-SDK`.
+-   `cd AltTester-Unity-SDK`
 
 For a more detailed tutorial check out the [GitHub Documentation](https://docs.github.com/en/get-started/quickstart/contributing-to-projects#forking-a-repository)
 
@@ -48,10 +48,10 @@ For a more detailed tutorial check out the [GitHub Documentation](https://docs.g
 
 After forking a project and applying your local changes, complete the following steps to create a pull request from your fork to contribute back to the main project:
 
-* In GitHub go to **Your Repositories** and open your forked repository.
-* Click on **Contribute** and then **Open a pull request**.
-* In the *Compare:* drop-down list box, select your branch in your forked repository (*head repository*) as the source branch.
-* In the *Base:* drop-down list box, select the `development` branch from the `AltTester-Unity-SDK` repository  (*base repository*) as the target branch.
-* Click **Create pull request** and assign a user to review your changes.
+-   In GitHub go to **Your Repositories** and open your forked repository.
+-   Click on **Contribute** and then **Open a pull request**.
+-   In the _Compare:_ drop-down list box, select your branch in your forked repository (_head repository_) as the source branch.
+-   In the _Base:_ drop-down list box, select the `development` branch from the `AltTester-Unity-SDK` repository (_base repository_) as the target branch.
+-   Click **Create pull request** and assign a user to review your changes.
 
 For a more detailed tutorial check out the [GitHub Documentation](https://docs.github.com/en/get-started/quickstart/contributing-to-projects).
diff --git a/Docs/source/pages/faq-troubleshooting.md b/Docs/source/pages/faq-troubleshooting.md
index 49833d343..12706531a 100644
--- a/Docs/source/pages/faq-troubleshooting.md
+++ b/Docs/source/pages/faq-troubleshooting.md
@@ -113,7 +113,6 @@ To use the Input from AltTester Unity SDK you have to reference <strong>AltTeste
 <summary> I downloaded the AltTester package v1.7.2 from the documentation on MacOS. I got a warning pop-up about the input system where I chose 'Yes' because I am using the New Input System. After reopening Unity Editor, <strong>AltTester Unity SDK is missing.</strong></summary>
 <br>
 
-
 After reopening Unity Editor, add again the AltTester package in your project.
 <br>
 
@@ -126,10 +125,11 @@ After reopening Unity Editor, add again the AltTester package in your project.
 
 You get this error because you don't have the Input System (New) package. If you only want to use the Input Manager (Old) in your project, follow this steps:
 <br>
-- <strong>delete</strong>:
-    - `Assets\AltTester\AltServer\NewInputSystem.cs`
-    - `Assets\AltTester\AltServer\AltKeyMapping.cs`
-- <strong>comment</strong> in `Assets\AltTester\AltServer\AltPrefabDrag.cs` the entire `#else` statement
+
+-   <strong>delete</strong>:
+    -   `Assets\AltTester\AltServer\NewInputSystem.cs`
+    -   `Assets\AltTester\AltServer\AltKeyMapping.cs`
+-   <strong>comment</strong> in `Assets\AltTester\AltServer\AltPrefabDrag.cs` the entire `#else` statement
 
     ```
     #if ENABLE_LEGACY_INPUT_MANAGER
@@ -138,8 +138,11 @@ You get this error because you don't have the Input System (New) package. If you
             // eventData.pointerDrag.gameObject.transform.position = UnityEngine.InputSystem.Mouse.current.position.ReadValue();
     #endif
     ```
-- <strong>comment</strong> in `Assets\AltTester\AltServer\Input.cs`:
-    - all imports for using `UnityEngine.InputSystem.UI`
+
+-   <strong>comment</strong> in `Assets\AltTester\AltServer\Input.cs`:
+
+    -   all imports for using `UnityEngine.InputSystem.UI`
+
         ```
         #if ALTTESTER && ENABLE_LEGACY_INPUT_MANAGER
 
@@ -155,7 +158,8 @@ You get this error because you don't have the Input System (New) package. If you
         // using UnityEngine.InputSystem.UI;
         using UnityEngine.Scripting;
         ```
-    - all `if` lines that contain `InputSystemUIInputModule` and the curly brackets inside these `if` statements making sure to leave the code inside the brackets uncommented
+
+    -   all `if` lines that contain `InputSystemUIInputModule` and the curly brackets inside these `if` statements making sure to leave the code inside the brackets uncommented
         ```
         // if (EventSystem.current.currentInputModule != null && EventSystem.current.currentInputModule.GetType().Name != typeof(InputSystemUIInputModule).Name)
                 // {
@@ -168,7 +172,7 @@ You get this error because you don't have the Input System (New) package. If you
                 // }
         ```
 
-- <strong>comment</strong> in `Assets\AltTester\AltServer\AltMockUpPointerInputModule.cs` the same as the above
+-   <strong>comment</strong> in `Assets\AltTester\AltServer\AltMockUpPointerInputModule.cs` the same as the above
 
 </details>
-<br>
\ No newline at end of file
+<br>
diff --git a/Docs/source/pages/get-started.md b/Docs/source/pages/get-started.md
index a752dda2c..62bae3f4f 100644
--- a/Docs/source/pages/get-started.md
+++ b/Docs/source/pages/get-started.md
@@ -38,7 +38,7 @@ To instrument your Unity application with AltTester Unity SDK you first need to
 
 ### Resolve dependencies
 
-- Newtonsoft.Json
+-   Newtonsoft.Json
 
 In order for AltTester Unity SDK to work you need dependency for Newtonsoft.Json. Add `"com.unity.nuget.newtonsoft-json": "3.0.1"` to your project `manifest.json`, inside `dependencies`.
 
@@ -50,19 +50,17 @@ In order for AltTester Unity SDK to work you need dependency for Newtonsoft.Json
 }
 ```
 
-- Input System
+-   Input System
 
 AltTester Unity SDK has support for Input System starting with version 1.7.1. To enable Input System in AltTester Unity SDK you need to add `"com.unity.inputsystem"` to your `manifest.json`, inside `testables.`
 
 ```json
 {
-    "testables": [
-        "com.unity.inputsystem"
-  ]
+    "testables": ["com.unity.inputsystem"]
 }
 ```
 
-- Editor Coroutines
+-   Editor Coroutines
 
 In order for AltTester Unity SDK to work with your project you need the dependency for Editor Coroutines. Add `"com.unity.editorcoroutines": "1.0.0` to your project `manifest.json`, inside `dependencies`.
 
@@ -73,6 +71,7 @@ In order for AltTester Unity SDK to work with your project you need the dependen
     }
 }
 ```
+
 <!--
 To instrument your Unity application with AltTester Unity SDK you first need to import the AltTester package into Unity.
 
@@ -151,7 +150,6 @@ Steps:
 
 The AltServer Module is incorporated in AltTester Desktop. In order to start it, all you have to do is to open AltTester Desktop.
 
-
 ## Run your app in Unity or on desired platform
 
 Before running your tests you need to start the instrumented Unity application. Upon startup, your instrumented Unity app should display a popup with the message: "Waiting for connections on port: {Port}". The popup disappears when your app has successfully connected to the tests.
@@ -283,10 +281,10 @@ AltTester package contains AltDriver class used to connect to the instrumented a
             - `.NET <https://dotnet.microsoft.com/en-us/download>`_ installed.
             - Instrumented build.
             - The AltTester Desktop installed on your PC.
-         
+
         **Connection:**
             Starting with version ``2.0.0``, the AltTester Desktop must be running on your PC while the tests are running.
-            
+
             1. The AltTester Desktop app is running.
             2. The instrumented build is running.
             3. Configure the IP of the build in order to match the IP of the machine (PC) the Desktop app is running on.
@@ -297,14 +295,14 @@ AltTester package contains AltDriver class used to connect to the instrumented a
             - To be able to run our test scripts, we should use a testing framework. For this tutorial, we will use the `NUnit testing framework <https://nunit.org/>`_.
             - In order to use ``NUnit``, you should start by creating an NUnit project. To do this, you need to create an empty folder (this will be the project folder) and open it in Visual Studio Code. `Open a terminal <https://code.visualstudio.com/docs/terminal/basics>`_ (we preferred git bash) and run the command below. This command will create a basic NUnit project for you:
             .. code-block:: console
-                
+
                 dotnet new nunit
-            
+
             - To be able to interact with the game through your tests, you need AltDriver. To add the AltDriver to your testing project, all you need to do is to use the following command in your terminal:
             .. code-block:: console
-                
+
                 dotnet add package AltTester-Driver --version x.y.z
-            
+
             **Note** that the ``x.y.z`` is the version of AltDriver you want to install.
 
         **Writing tests:**
@@ -314,7 +312,7 @@ AltTester package contains AltDriver class used to connect to the instrumented a
         **Running the tests:**
             - To run your test, open a terminal window in the project folder and paste the following command:
             .. code-block:: console
-                
+
                 dotnet test
 
         Example test file:
@@ -344,10 +342,10 @@ AltTester package contains AltDriver class used to connect to the instrumented a
             - `Java <https://www.java.com/download/ie_manual.jsp>`_ installed.
             - Instrumented build.
             - The AltTester Desktop installed on your PC.
-         
+
         **Connection:**
             Starting with version ``2.0.0``, the AltTester Desktop must be running on your PC while the tests are running.
-            
+
             1. The AltTester Desktop app is running.
             2. The instrumented build is running.
             3. Configure the IP of the build in order to match the IP of the machine (PC) the Desktop app is running on.
@@ -396,10 +394,10 @@ AltTester package contains AltDriver class used to connect to the instrumented a
             - `Python <https://www.python.org/downloads/>`_ installed.
             - Instrumented build.
             - The AltTester Desktop installed on your PC.
-         
+
         **Connection:**
             Starting with version ``2.0.0``, the AltTester Desktop must be running on your PC while the tests are running.
-            
+
             1. The AltTester Desktop app is running.
             2. The instrumented build is running.
             3. Configure the IP of the build in order to match the IP of the machine (PC) the Desktop app is running on.
@@ -410,16 +408,16 @@ AltTester package contains AltDriver class used to connect to the instrumented a
             - You can use any IDE you want. As a suggestion, we prefer `Visual Studio Code <https://code.visualstudio.com/>`_  and `PyCharm <https://www.jetbrains.com/pycharm/download/>`_.
             - To actually run the tests we need a test framework. One of the most popular python testing frameworks is `pytest <https://pypi.org/project/pytest/>`_ which is easy to download because you just need to use the following command in your terminal:
             .. code-block:: console
-                
+
                 pip install pytest
-            
+
             - To be able to interact with the game through your tests, you need AltDriver. It contains all the methods you need such as ``tap()``, ``wait_for_object()``, ``find_object()`` and so on. To add the `AltDriver <https://pypi.org/project/AltTester-Driver/>`_ to your testing project, all you need to do is to use the following command in your terminal:
             .. code-block:: console
 
                 pip install AltTester-Driver
 
             The following setup steps are not mandatory, but if you choose to use them, you will act like a pro.
-            
+
             - Install `assertpy <https://pypi.org/project/assertpy/>`_ - for easy and nice assertions.
             - Most of the time on a project, you will have to provide some reports with the results of your tests. In order to provide them, you can use ``pytest-html-reporter`` which generates nice and detailed reports with the results of your tests. To install ``pytest-html-reporter`` use the following command:
             .. code-block:: console
@@ -434,20 +432,20 @@ AltTester package contains AltDriver class used to connect to the instrumented a
             - Running tests using pytest can be easily done using the commands for cmd.
             - Run **all the tests**: navigate through the cmd in the folder that contains the tests folder and use the following command:
             .. code-block:: console
-            
+
                 pytest tests/
             - Run **a specific test file**: navigate into the tests folder and use the following command:
             .. code-block:: console
-                
+
                 pytest test_name.py
 
             - Run a **specific test method** from a file: navigate into the tests folder and use the following command:
             .. code-block:: console
-            
+
                 pytest test_name.py -k name_of_test_you_wanna_run
             - For running tests with the HTML reporter, all you have to do is to add this extra argument   to your running command:
             .. code-block:: console
-                
+
                 --html-report=./report/report.html.
             This will generate a report under the `report` folder.
 
diff --git a/Packages/packages-lock.json b/Packages/packages-lock.json
index cd84abf2c..0f9345521 100644
--- a/Packages/packages-lock.json
+++ b/Packages/packages-lock.json
@@ -1,7 +1,7 @@
 {
   "dependencies": {
-    "com.unity.collab-proxy": {
-      "version": "1.3.9",
+    "com.unity.editorcoroutines": {
+      "version": "1.0.0",
       "depth": 0,
       "source": "registry",
       "dependencies": {},
@@ -9,45 +9,29 @@
     },
     "com.unity.ext.nunit": {
       "version": "1.0.6",
-      "depth": 0,
+      "depth": 1,
       "source": "registry",
       "dependencies": {},
       "url": "https://packages.unity.com"
     },
-    "com.unity.ide.rider": {
-      "version": "2.0.7",
-      "depth": 0,
-      "source": "registry",
-      "dependencies": {
-        "com.unity.test-framework": "1.1.1"
-      },
-      "url": "https://packages.unity.com"
-    },
-    "com.unity.ide.visualstudio": {
-      "version": "2.0.7",
+    "com.unity.inputsystem": {
+      "version": "1.4.4",
       "depth": 0,
       "source": "registry",
       "dependencies": {
-        "com.unity.test-framework": "1.1.9"
+        "com.unity.modules.uielements": "1.0.0"
       },
       "url": "https://packages.unity.com"
     },
-    "com.unity.ide.vscode": {
-      "version": "1.2.3",
-      "depth": 0,
-      "source": "registry",
-      "dependencies": {},
-      "url": "https://packages.unity.com"
-    },
-    "com.unity.inputsystem": {
-      "version": "1.0.2",
+    "com.unity.nuget.newtonsoft-json": {
+      "version": "3.0.2",
       "depth": 0,
       "source": "registry",
       "dependencies": {},
       "url": "https://packages.unity.com"
     },
     "com.unity.test-framework": {
-      "version": "1.1.24",
+      "version": "1.1.30",
       "depth": 0,
       "source": "registry",
       "dependencies": {
@@ -58,7 +42,7 @@
       "url": "https://packages.unity.com"
     },
     "com.unity.textmeshpro": {
-      "version": "3.0.1",
+      "version": "3.0.4",
       "depth": 0,
       "source": "registry",
       "dependencies": {
@@ -66,95 +50,30 @@
       },
       "url": "https://packages.unity.com"
     },
-    "com.unity.timeline": {
-      "version": "1.4.7",
-      "depth": 0,
-      "source": "registry",
-      "dependencies": {
-        "com.unity.modules.director": "1.0.0",
-        "com.unity.modules.animation": "1.0.0",
-        "com.unity.modules.audio": "1.0.0",
-        "com.unity.modules.particlesystem": "1.0.0"
-      },
-      "url": "https://packages.unity.com"
-    },
     "com.unity.ugui": {
       "version": "1.0.0",
-      "depth": 0,
+      "depth": 1,
       "source": "builtin",
       "dependencies": {
         "com.unity.modules.ui": "1.0.0",
         "com.unity.modules.imgui": "1.0.0"
       }
     },
-    "com.unity.modules.ai": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.androidjni": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.animation": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.assetbundle": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.audio": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.cloth": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.physics": "1.0.0"
-      }
-    },
-    "com.unity.modules.director": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.audio": "1.0.0",
-        "com.unity.modules.animation": "1.0.0"
-      }
-    },
     "com.unity.modules.imageconversion": {
       "version": "1.0.0",
-      "depth": 0,
+      "depth": 1,
       "source": "builtin",
       "dependencies": {}
     },
     "com.unity.modules.imgui": {
       "version": "1.0.0",
-      "depth": 0,
+      "depth": 1,
       "source": "builtin",
       "dependencies": {}
     },
     "com.unity.modules.jsonserialize": {
       "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.particlesystem": {
-      "version": "1.0.0",
-      "depth": 0,
+      "depth": 1,
       "source": "builtin",
       "dependencies": {}
     },
@@ -178,40 +97,9 @@
         "com.unity.modules.imageconversion": "1.0.0"
       }
     },
-    "com.unity.modules.subsystems": {
-      "version": "1.0.0",
-      "depth": 1,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.jsonserialize": "1.0.0"
-      }
-    },
-    "com.unity.modules.terrain": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.terrainphysics": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.physics": "1.0.0",
-        "com.unity.modules.terrain": "1.0.0"
-      }
-    },
-    "com.unity.modules.tilemap": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.physics2d": "1.0.0"
-      }
-    },
     "com.unity.modules.ui": {
       "version": "1.0.0",
-      "depth": 0,
+      "depth": 1,
       "source": "builtin",
       "dependencies": {}
     },
@@ -235,111 +123,6 @@
         "com.unity.modules.imgui": "1.0.0",
         "com.unity.modules.jsonserialize": "1.0.0"
       }
-    },
-    "com.unity.modules.umbra": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.unityanalytics": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.unitywebrequest": "1.0.0",
-        "com.unity.modules.jsonserialize": "1.0.0"
-      }
-    },
-    "com.unity.modules.unitywebrequest": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.unitywebrequestassetbundle": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.assetbundle": "1.0.0",
-        "com.unity.modules.unitywebrequest": "1.0.0"
-      }
-    },
-    "com.unity.modules.unitywebrequestaudio": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.unitywebrequest": "1.0.0",
-        "com.unity.modules.audio": "1.0.0"
-      }
-    },
-    "com.unity.modules.unitywebrequesttexture": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.unitywebrequest": "1.0.0",
-        "com.unity.modules.imageconversion": "1.0.0"
-      }
-    },
-    "com.unity.modules.unitywebrequestwww": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.unitywebrequest": "1.0.0",
-        "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
-        "com.unity.modules.unitywebrequestaudio": "1.0.0",
-        "com.unity.modules.audio": "1.0.0",
-        "com.unity.modules.assetbundle": "1.0.0",
-        "com.unity.modules.imageconversion": "1.0.0"
-      }
-    },
-    "com.unity.modules.vehicles": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.physics": "1.0.0"
-      }
-    },
-    "com.unity.modules.video": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.audio": "1.0.0",
-        "com.unity.modules.ui": "1.0.0",
-        "com.unity.modules.unitywebrequest": "1.0.0"
-      }
-    },
-    "com.unity.modules.vr": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.jsonserialize": "1.0.0",
-        "com.unity.modules.physics": "1.0.0",
-        "com.unity.modules.xr": "1.0.0"
-      }
-    },
-    "com.unity.modules.wind": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {}
-    },
-    "com.unity.modules.xr": {
-      "version": "1.0.0",
-      "depth": 0,
-      "source": "builtin",
-      "dependencies": {
-        "com.unity.modules.physics": "1.0.0",
-        "com.unity.modules.jsonserialize": "1.0.0",
-        "com.unity.modules.subsystems": "1.0.0"
-      }
     }
   }
 }
diff --git a/README.md b/README.md
index c7f2a5622..076a0de5d 100644
--- a/README.md
+++ b/README.md
@@ -6,12 +6,12 @@ AltTester Unity SDK is an open-source UI driven test automation tool that helps
 
 Our documentation is available here:
 
-* https://alttester.com/docs/pro/sdk/
+-   https://alttester.com/docs/pro/sdk/
 
 ## Support
 
-* Join our Discord Server: https://discord.gg/Ag9RSuS
-* Join our Google Group for questions and discussions: https://groups.google.com/a/altom.com/g/alttesterforum
+-   Join our Discord Server: https://discord.gg/Ag9RSuS
+-   Join our Google Group for questions and discussions: https://groups.google.com/a/altom.com/g/alttesterforum
 
 ## Development Setup
 
diff --git a/UserSettings/Search.settings b/UserSettings/Search.settings
new file mode 100644
index 000000000..9e26dfeeb
--- /dev/null
+++ b/UserSettings/Search.settings
@@ -0,0 +1,1 @@
+{}
\ No newline at end of file


Test patch:
diff --git a/Docs/source/pages/alttester-with-appium.md b/Docs/source/pages/alttester-with-appium.md
index 816561620..c5fdee55f 100644
--- a/Docs/source/pages/alttester-with-appium.md
+++ b/Docs/source/pages/alttester-with-appium.md
@@ -13,27 +13,25 @@ No registration is needed and you can either download the latest version of the
 
 We've created an example python project which can be found [here](https://github.com/alttester-test-examples/Python-Android-with-Appium-AltTrashCat-) which hopefully can get you started on your own projects. Using it will also automatically install the requirements needed for running the tests. More details about it [below](#alttester-unity-sdk-with-appium-example).
 
-
 ## Why use Appium together with AltTester Unity SDK
 
 There's a couple of reasons/scenarios for which you would want to use both of these frameworks:
 
-* By itself, AltTester Unity SDK cannot launch an app on a device. If you want to run tests in a pipeline, or by using [cloud services](./alttester-with-cloud), you can either create a script which will start your app, or you can use Appium before the tests execution;
-* AltTester Unity SDK cannot perform some types of actions, such as interacting with any native popups your app might have, or putting the app in the background and resuming it. In any of these cases you can use Appium to do the things that AltTester Unity SDK can't.
-
+-   By itself, AltTester Unity SDK cannot launch an app on a device. If you want to run tests in a pipeline, or by using [cloud services](./alttester-with-cloud), you can either create a script which will start your app, or you can use Appium before the tests execution;
+-   AltTester Unity SDK cannot perform some types of actions, such as interacting with any native popups your app might have, or putting the app in the background and resuming it. In any of these cases you can use Appium to do the things that AltTester Unity SDK can't.
 
 ## AltTester Unity SDK with Appium example
 
 After you cloned our example project, there are a couple of things you need to check before running the tests:
 
-* For **Android** you need to have Android SDK version 16 or higher installed on your machine;
-* For **iOS** you need XCode with Command Line Tools installed (will only work on Mac OSX);
-* Your mobile device needs to have developer mode enabled and be connected via USB to the machine running the tests.
+-   For **Android** you need to have Android SDK version 16 or higher installed on your machine;
+-   For **iOS** you need XCode with Command Line Tools installed (will only work on Mac OSX);
+-   Your mobile device needs to have developer mode enabled and be connected via USB to the machine running the tests.
 
 **Running the tests**
 
-* For **Android** you can just run the script `run-tests_android.sh`
-* For **iOS**, you first need to `export IOS_UDID=<your-device-udid>` then run the script `run-tests_ios.sh`
+-   For **Android** you can just run the script `run-tests_android.sh`
+-   For **iOS**, you first need to `export IOS_UDID=<your-device-udid>` then run the script `run-tests_ios.sh`
 
 ```eval_rst
 .. note::