[iOS] Location Usage Description dependency issue

[RobertPoienar]

The iOS build process fails if the Location Usage Description is empty because the AltTester SDK references Input.Compass and Input.Location for input simulation, triggering Unity's mandatory permission check.

Steps to reproduce
Use Unity 6.0 with AltTester SDK 2.2.6 or 2.2.7.

Ensure the Location Usage Description in Project Settings > Player > iOS is empty.

Attempt to perform a regular (non-test-automation) iOS build.

Actual result
AR
The build fails with the error: LocationService class is used, but Location Usage Description is empty in Player Settings.

Additional info
This occurs even if the AltTester plugin is not active in the build, as the compiler detects the usage of location-related APIs within the SDK source code.

Expected result
ER
Regular iOS builds should not require location permissions or descriptions if location simulation features are not being utilized.

Additional info
The SDK should only include location-related code when explicitly requested by the user, preventing unnecessary privacy metadata requirements in production builds.

[andreion1ca]

I tested this issue using the AltTester Unity SDK GPL version from branch b842243.

Test setup:

• Unity: 6.0
• Platform: iOS
• Location Usage Description: left empty in Project Settings > Player > iOS

Result:
With the SDK changes from branch b842243, I was able to successfully build the iOS project without providing a Location Usage Description. The build completed without errors, and Unity did not require location permissions.

Conclusion:
The issue is fixed in this branch. Location-related APIs are no longer triggering Unity’s mandatory iOS permission checks during regular (non-test-automation) builds when the location simulation features are not explicitly used.