mirror of
https://github.com/meshtastic/Meshtastic-Android.git
synced 2026-06-01 22:19:18 +02:00
Revert "fix(takserver): emit *:-1:stcp contact endpoint so directed TAK-Talk/GeoChat routes over the mesh; SDK v0.5.1"
This commit landed on main outside the PR process and pins takpacket-sdk 0.5.1, which is not yet published to Maven Central — breaking the build. Reverting to restore a green main; the fix is being re-submitted as a pull request that will merge once 0.5.1 is available on Central. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -24,13 +24,7 @@ import org.meshtastic.proto.User
|
||||
// a single exported data package (containing truststore.p12 + client.p12) works for
|
||||
// both Meshtastic-iOS and Meshtastic-Android without reconfiguration in ATAK/iTAK.
|
||||
internal const val DEFAULT_TAK_PORT = 8089
|
||||
|
||||
// Default contact endpoint for mesh peers (the real endpoint is never carried over
|
||||
// LoRa). MUST be the TAK "reply via this server" form `*:-1:stcp`: it makes ATAK route
|
||||
// directed GeoChat / TAK-Talk (`<marti>`) back down the Meshtastic server stream. A
|
||||
// concrete host (e.g. `0.0.0.0:4242:tcp`) makes ATAK attempt a dead direct connection,
|
||||
// so directed messages never reach the mesh while broadcast PLI still works.
|
||||
internal const val DEFAULT_TAK_ENDPOINT = "*:-1:stcp"
|
||||
internal const val DEFAULT_TAK_ENDPOINT = "0.0.0.0:4242:tcp"
|
||||
|
||||
// Bundled certificate password — matches iOS (`"meshtastic"`). Used for the
|
||||
// server.p12 / client.p12 PKCS#12 files shipped under `tak_certs/` on the classpath.
|
||||
|
||||
@@ -88,7 +88,7 @@ kable = "0.43.0"
|
||||
mqttastic = "0.3.6"
|
||||
jmdns = "3.6.3"
|
||||
qrcode-kotlin = "4.5.0"
|
||||
takpacket-sdk = "0.5.1"
|
||||
takpacket-sdk = "0.5.0"
|
||||
|
||||
# Gradle Plugins
|
||||
develocity = "4.4.2"
|
||||
|
||||
Reference in New Issue
Block a user