Server configuration

[arifBurakDemiray]

No description provided.

[github-actions]

Unit Test Results 🚀

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 9a1b239. ± Comparison against base commit 92def04.

♻️ This comment has been updated with latest results.

[Copilot]

Copilot reviewed 36 out of 36 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (4)

sdk/src/main/java/ly/count/android/sdk/ConnectionQueue.java:198

• Ensure that wrapping the location data addition within a configProvider check does not omit necessary data when location tracking is intentionally disabled; if this is the desired behavior, consider adding a comment to clarify the logic.

if (configProvider.getLocationTrackingEnabled()) {

sdk/src/androidTest/java/ly/count/android/sdk/TestUtils.java:477

• Renaming from getCountyStore() to getCountlyStore() improves consistency; please confirm that all references across tests have been updated accordingly.

protected static CountlyStore getCountlyStore() {

sdk/src/androidTest/java/ly/count/android/sdk/ModuleAPMTests.java:265

• [nitpick] Verify that the truncation of the trace key from 'a_trace_to_track' to 'a_tra' aligns with the intended key length limit in the server configuration and is consistent throughout the SDK.

String key = "a_trace_to_track";

sdk/src/androidTest/java/ly/count/android/sdk/ConnectionProcessorTests.java:81

• Double-check that overriding getSessionTrackingEnabled() to return false in the test configuration aligns with the intended session tracking behavior, as this may affect related session logic.

@Override public boolean getSessionTrackingEnabled() {