Do not normalize UUIDs on native side

[fotiDim]

PR Type

Bug fix, Enhancement

---

Description

• Removed UUID normalization logic from both Android and iOS implementations.

• Simplified UUID handling by directly using provided UUID strings.

• Updated related methods to remove dependency on validFullUUID.

---

Changes walkthrough 📝

	Relevant files
Enhancement	UniversalBleHelper.kt Removed UUID normalization logic in Android helper              android/src/main/kotlin/com/navideck/universal_ble/UniversalBleHelper.kt Removed the validFullUUID function for UUID normalization. Updated toUUIDList to directly use provided UUID strings. +1/-9      UniversalBleHelper.swift Removed UUID normalization logic in iOS helper                      darwin/Classes/UniversalBleHelper.swift Removed the validFullUUID extension for UUID normalization. Simplified UUID handling by eliminating unnecessary logic. +0/-14
Bug fix	UniversalBlePlugin.swift Simplified UUID handling in iOS plugin                                      darwin/Classes/UniversalBlePlugin.swift Updated UUID handling in onScanResult to directly use UUID strings. Removed usage of validFullUUID in service UUID validation. +2/-2

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review UUID Validation The removal of UUID normalization may cause compatibility issues with devices that send short-form UUIDs. Verify that all connected BLE devices send full UUIDs. guard UUID(uuidString: serviceUUID) != nil else { throw PigeonError(code: "IllegalArgument", message: "Invalid service UUID:\(serviceUUID)", details: nil) Error Handling Direct UUID parsing without validation could throw IllegalArgumentException if invalid UUID string is provided. Consider adding error handling. return this.map { UUID.fromString(it) }

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Add error handling for invalid UUIDs Add error handling for UUID validation before mapping services. The current code could crash if an invalid UUID is encountered. darwin/Classes/UniversalBlePlugin.swift [351] -services: services?.map { $0.uuidStr } +services: services?.compactMap { service in + guard UUID(uuidString: service.uuidStr) != nil else { return nil } + return service.uuidStr +} Apply this suggestion Suggestion importance[1-10]: 8 __ Why: The suggestion adds important error handling for invalid UUIDs that could cause runtime crashes. This is particularly relevant since the PR removes the UUID normalization logic.	Medium
	Handle invalid UUID parsing errors Add try-catch block to handle potential IllegalArgumentException when parsing invalid UUIDs. android/src/main/kotlin/com/navideck/universal_ble/UniversalBleHelper.kt [77] -return this.map { UUID.fromString(it) } +return this.mapNotNull { uuid -> + try { + UUID.fromString(uuid) + } catch (e: IllegalArgumentException) { + null + } +} Apply this suggestion Suggestion importance[1-10]: 8 __ Why: The suggestion adds critical error handling for UUID parsing that could throw IllegalArgumentException. This is especially important after removing the UUID validation function.	Medium