uTLS fingerprint falls back to 'chrome' on subscription import / Visual update bug

[temperance447]

Description

When adding a subscription via Remnawave, all client profiles incorrectly display the uTLS fingerprint as chrome, regardless of the actual client settings.

The connection itself remains fully functional. This appears to be a visual UI/sync bug: if a user manually changes the fingerprint inside the profile and then updates the subscription, the panel states that there is "nothing to update" (no changes detected), and the fingerprint value fails to update correctly.

Steps to Reproduce

1. Import/add a subscription in Remnawave.
2. Check the client profiles (all show chrome as the uTLS fingerprint).
3. Manually change the fingerprint in a profile to a different value.
4. Trigger a subscription update.
5. Notice the message "Nothing to update" and that the fingerprint is not synced/corrected.

Expected Behavior

The panel should correctly fetch, detect, and display the actual uTLS fingerprint configured in the profile during subscription creation and updates.

Actual Behavior

The UI defaults/hardcodes the display to chrome for all profiles, and subsequent subscription syncs fail to update this value because they see no changes.

Environment

• Remnawave Panel Version: v2.8.1
• Xray-core Version: v26.6.27
• Exclave: v0.17.46)

[dyhkwong]

Only information necessary for connecting to a server will be parsed. uTLS is not one of them.