Contact Details

olli.raty@lut.fi

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

• I actually read this list, and should be taken seriously.

Affected app version

2.7.14 (29321034) google

Affected Android version

Android 16

Affected phone model

Samsung Galaxy A54

Affected node model

Seeed Card Tracker T1000-E

Affected node firmware version

2.7.15

Steps to reproduce the bug

Go to module settings>MQTT
input an address for a private MQTT broker that has tls enabled
enable tls
press check connection
error pops up: TLS handshake failed: Domain specific configurations require that hostname aware checkServerTrusted(X509 Certificate[], String, String) is used

Actual behavior

An error pops up: TLS handshake failed: Domain specific configurations require that hostname aware checkServerTrusted(X509 Certificate[], String, String) is used

Expected behavior

Should not give an error, or at the very least, the error should be related to the connection, rather than which method or function was used in the verification.

Screenshots/Screen recordings

No response

Relevant log output

Additional information

I am aware that the node isn't on the alpha firmware, but given that the connection probing happens entirely within the app, it is irrelevant. Also, I have checked that the MQTT broker I'm using is reachable from the network I'm using. The certificates are self-signed with openssl.