AltTester Unity SDK's compatibility with Android 12

[jayMaheta721]

The application crashes on startup when integrated with the AltTester Unity SDK on devices running Android 12 (API level 31) or higher.

Steps to reproduce

1. Integrate the AltTester Unity SDK into a Unity project.
2. Build the project targeting Android.
3. Install and launch the application on a device running Android 12 or higher.

Actual result

The application crashes immediately upon launch.

Additional info

• Error Log:
  java.lang.RuntimeException: Unable to start activity ComponentInfo{com.sunsetgames.name/com.unity3d.player.UnityPlayerActivity}: java.lang.SecurityException: com.sunsetgames.name: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts

• Device: Motorola Edge 40

• OS Version: Android 14

• Unity Version: 2021.3.15

• AltTester SDK Version: 2.1.2

Expected result

ER

The application should launch successfully without crashes on devices running Android 12 or higher.

Testability

Test Environment: Use a device running Android 12 or higher.

Test Steps:
1) Integrate the AltTester Unity SDK into a Unity project.
2) Build and install the application on the test device.
3) Launch the application and verify it starts without crashing.

[iulianatodoran]

@jayMaheta721, we started looking into this issue and will continue to address it promptly.

[iulianatodoran]

@jayMaheta721 We tested multiple Android 12, 13, and 14 devices using builds instrumented with AltTester Unity SDK v2.2.0 and were unable to reproduce the issue.
Additionally, we tested both Mono and IL2CPP builds with the same results.

Here are a few suggestions to help further investigate the problem:

• Please try upgrading to version 2.2.0 and test again.
• Can you reproduce the crash with a build that does not include the AltTester Unity SDK?
• If the crash does not occur for a build without AltTester Unity SDK, but still occurs when instrumented with AltTester Unity SDK v2.2.0, could you provide more details about your setup? This information might help us debug the issue more effectively.