getJettonData() fails

[rtentser]

const getJettonData = async (provider: TonClient): Promise<void> => {
  const jettonAddress = 'EQBynBO23ywHy_CgarY9NK9FTz0yDsG82PtcbSTQgGoXwiuA'
  const jetton = provider.open(JettonMaster.create(Address.parse(jettonAddress)))
  console.log(await jetton.getJettonData())
}

fails with

Error: Invalid address: 0
    at BitReader.loadAddress (/home/rtentser/miki/ton-mvp/node_modules/@ton/core/dist/boc/BitReader.js:279:19)
    at Slice.loadAddress (/home/rtentser/miki/ton-mvp/node_modules/@ton/core/dist/boc/Slice.js:321:29)
    at TupleReader.readAddress (/home/rtentser/miki/ton-mvp/node_modules/@ton/core/dist/tuple/reader.js:81:46)
    at JettonMaster.getJettonData (/home/rtentser/miki/ton-mvp/node_modules/@ton/ton/dist/jetton/JettonMaster.js:27:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

provider is new TonClient({ endpoint: rpcProviderUrl, apiKey })
rpcProviderUrl is https://toncenter.com/api/v2/jsonRPC
jetton is jUSDT

From the look at this test it should work.
Am i doing something wrong?

[n3omaster]

I'm doing like this:

require("buffer")

import { TonClient, JettonMaster, Address, beginCell } from "ton"
const client = new TonClient({ endpoint: 'https://toncenter.com/api/v2/jsonRPC', apiKey: process.env.TON_API_KEY })

export const fetchCache = 'force-no-store'
export const revalidate = 0

const usdtJetton = "EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs"
const walletAddress = "UQBon7mHV_aVCRu3kiZECZ5PXpPAIWHE9DugcSdIkvwzyMAx"

export async function GET(request) {

    const data = []
    const jettonMasterAddress = Address.parse(usdtJetton)
    const userAddress = Address.parse(walletAddress)

    const jettonMaster = client.open(JettonMaster.create(jettonMasterAddress))
    const jettonAddress = await jettonMaster.getWalletAddress(userAddress)
    const jettonData = await jettonMaster.getJettonData()

    console.log(jettonAddress.toString())
    console.log(jettonData)

    return new Response(JSON.stringify(data), { headers: { 'Content-Type': 'application/json' } })
}

[khaydarov]

@dvlkv Hi, the same problem we have with NOTCOIN jetton. Making readAddress optional here (by calling readAddressOpt) helps, but it is difficult to predict the consequences.

Here is the contract address EQAvlWFDxGF2lXm67y4yzC17wYKD9A0guwPkMs1gOsM__NOT