-
Notifications
You must be signed in to change notification settings - Fork 42
Description
Title:
get_last_clean_time throws exit code -13 when setting timeout to 900 in HighloadWalletV3 (Ton4j v0.9.9)
Description:
I am trying to deploy a HighloadWalletV3 contract using Ton4j version 0.9.9, and I’m facing an issue when I set the timeout to 900 (15 minutes). The deployment seems to fail silently (extMessageInfo.getHash() returns null) and calling getLastCleanTime() throws:
java.lang.Error: method get_last_clean_time returned an exit code -13
This happens for both HighloadWalletV3 and HighloadWalletV3S when timeout is set to 900. It works if I remove the timeout or use a lower value (default).
Code snippet:
HighloadWalletV3 contract = HighloadWalletV3.builder()
.tonlib(tonlib)
.keyPair(keyPair)
.timeout(900) // causes issue
.walletId(42)
.build();
ExtMessageInfo extMessageInfo = contract.deploy(config);
log.info("deployed contract {}", extMessageInfo.getHash());
long lastCleanTime = contract.getLastCleanTime(); // throws Error
Observed behavior:
deploy() returns null hash.
getLastCleanTime() throws exit code -13.
Balance is topped up successfully.
No failure is thrown at the time of deploy itself.
Expected behavior:
Wallet should deploy successfully with 15-minute timeout (900).
getLastCleanTime() should return a valid result.
Environment:
Ton4j version: 0.9.9
Java version: 21
OS: Windows
Network: TON Testnet
Logs:
deployed contract null
java.lang.Error: method get_last_clean_time returned an exit code -13
Additional context:
This issue does not occur when the timeout is not manually set (defaults to 60). Could this be a serialization issue with config or a limitation on timeout range?