plugins-workspace icon indicating copy to clipboard operation
plugins-workspace copied to clipboard
verified publisher icon tauri-apps

Bug: HTTP fetch API call is blocked with no error

Open caol64 opened this issue 7 months ago • 12 comments

I'm using the [Vanilla JS API](https://v2.tauri.app/reference/javascript/api/#vanilla-js-api) from Tauri v2.

💡 Problem

The fetch call from @tauri-apps/plugin-http returns a response object, but calling response.json() silently hangs — no error is thrown, and execution is blocked indefinitely.

🧪 Minimal Reproduction

const { fetch: tauriFetch } = window.__TAURI__.http;

class WeUploader {
    constructor(imageHost) {
        this.imageHost = imageHost;
        this.tokenUrl = "https://example.com/token";
    }

    async fetchAccessToken() {
        try {
            const response = await tauriFetch(`${this.tokenUrl}?appid=xxx&secret=yyy`);
            console.log(response); // response.bodyUsed is already true
            const data = await response.json(); // hangs here with no error
            console.log(data);
        } catch (error) {
            console.error("Failed to fetch access token", error);
        }
    }
}

🖼️ Screenshot (response is printed, but response.json() never resolves):

Image

🔧 Environment Details

package.json:

"devDependencies": {
  "@tauri-apps/cli": "^2.3.1"
},
"dependencies": {
  "@tauri-apps/api": "^2.3.0",
  "@tauri-apps/plugin-http": "^2.3.0"
}

Cargo.toml:

[build-dependencies]
tauri-build = { version = "2", features = [] }

[dependencies]
tauri-plugin-http = "2"

tauri.conf.json permissions:

"permissions": [
  {
    "identifier": "http:default",
    "allow": [
      { "url": "http://**" },
      { "url": "https://**" }
    ]
  },
  "http:allow-fetch",
  "http:allow-fetch-cancel",
  "http:allow-fetch-read-body",
  "http:allow-fetch-send"
]

✅ Expected Behavior

Calling await response.json() should resolve to parsed JSON data, as in browser or other environments.

📌 Notes

  • response.bodyUsed is already true when the response is logged, which may indicate the body is already consumed or incorrectly handled.
  • There are no errors thrown, making debugging very difficult.

Let me know if you need a full reproduction repo. Thanks!

caol64 avatar May 19 '25 04:05 caol64

Please share the output of the tauri info command. This sounds like a version mismatch at first glance.

FabianLars avatar May 19 '25 06:05 FabianLars

I encountered the same issue. First, I deleted the target directory, then tauri build failed with a cmake error in aws-lc-sys. After that, I updated the project using cargo update, but during the build, I encountered errors like unresolved symbol 'aws_lc_0_29_0_aes_hw_set_encrypt_key' and several others of the same kind.

unresolved symbol errors 
.\target\release\deps\sqlx_macros-652649a3672bf2a1.dll.exp␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_set_encrypt_key，函数 aead_aes_ccm_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_set_decrypt_key，函数 aes_init_key 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_encrypt，函数 aead_aes_ccm_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_decrypt，函数 aes_init_key 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_cbc_encrypt，函数 aes_init_key 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_ctr32_encrypt_blocks，函数 aead_aes_ccm_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_ecb_encrypt，函数 aes_hw_ecb_cipher 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_xts_encrypt，函数 aes_xts_cipher 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aes_hw_xts_decrypt，函数 aes_xts_cipher 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_vpaes_set_encrypt_key，函数 aead_aes_ccm_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_vpaes_set_decrypt_key，函数 aes_init_key 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_vpaes_encrypt，函数 aead_aes_ccm_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_vpaes_decrypt，函数 aes_init_key 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_vpaes_cbc_encrypt，函数 aes_init_key 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_vpaes_ctr32_encrypt_blocks，函数 aead_aes_ccm_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_init_clmul，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_gmult_clmul，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_ghash_clmul，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_gmult_ssse3，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_ghash_ssse3，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_init_avx，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_gmult_avx，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_gcm_ghash_avx，函数 aws_lc_0_29_0_CRYPTO_ghash_init 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aesni_gcm_encrypt，函数 aws_lc_0_29_0_CRYPTO_gcm128_encrypt_ctr32 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_aesni_gcm_decrypt，函数 aws_lc_0_29_0_CRYPTO_gcm128_decrypt_ctr32 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_mul_mont_nohw，函数 aws_lc_0_29_0_bn_mul_mont 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_mul4x_mont，函数 aws_lc_0_29_0_bn_mul_mont 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_mulx4x_mont，函数 aws_lc_0_29_0_bn_mul_mont 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_sqr8x_mont，函数 aws_lc_0_29_0_bn_mul_mont 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_mul_mont_gather5，函数 aws_lc_0_29_0_BN_mod_exp_mont_consttime 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_scatter5，函数 aws_lc_0_29_0_BN_mod_exp_mont_consttime 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_gather5，函数 aws_lc_0_29_0_BN_mod_exp_mont_consttime 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_bn_power5，函数 aws_lc_0_29_0_BN_mod_exp_mont_consttime 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_1024_norm2red_avx2，函数 aws_lc_0_29_0_RSAZ_1024_mod_exp_avx2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_1024_mul_avx2，函数 aws_lc_0_29_0_RSAZ_1024_mod_exp_avx2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_1024_sqr_avx2，函数 aws_lc_0_29_0_RSAZ_1024_mod_exp_avx2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_1024_scatter5_avx2，函数 aws_lc_0_29_0_RSAZ_1024_mod_exp_avx2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_1024_gather5_avx2，函数 aws_lc_0_29_0_RSAZ_1024_mod_exp_avx2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_1024_red2norm_avx2，函数 aws_lc_0_29_0_RSAZ_1024_mod_exp_avx2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_amm52x20_x1_ifma256，函数 aws_lc_0_29_0_RSAZ_mod_exp_avx512_x2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_amm52x20_x2_ifma256，函数 rsaz_mod_exp_x2_ifma256 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_extract_multiplier_2x20_win5，函数 rsaz_mod_exp_x2_ifma256 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_amm52x30_x1_ifma256，函数 aws_lc_0_29_0_RSAZ_mod_exp_avx512_x2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_amm52x30_x2_ifma256，函数 rsaz_mod_exp_x2_ifma256 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_extract_multiplier_2x30_win5，函数 rsaz_mod_exp_x2_ifma256 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_amm52x40_x1_ifma256，函数 aws_lc_0_29_0_RSAZ_mod_exp_avx512_x2 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_rsaz_amm52x40_x2_ifma256，函数 rsaz_mod_exp_x2_ifma256 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_extract_multiplier_2x40_win5，函数 rsaz_mod_exp_x2_ifma256 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_CRYPTO_rdrand，函数 rdrand 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_CRYPTO_rdrand_multiple8_buf，函数 rdrand 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha1_block_data_order_avx2，函数 aws_lc_0_29_0_SHA1_Final 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha1_block_data_order_avx，函数 aws_lc_0_29_0_SHA1_Final 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha1_block_data_order_ssse3，函数 aws_lc_0_29_0_SHA1_Final 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha256_block_data_order_avx，函数 aws_lc_0_29_0_ECDH_compute_key_fips 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha256_block_data_order_ssse3，函数 aws_lc_0_29_0_ECDH_compute_key_fips 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha512_block_data_order_avx，函数 aws_lc_0_29_0_ECDH_compute_key_fips 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha1_block_data_order_hw，函数 aws_lc_0_29_0_SHA1_Final 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha1_block_data_order_nohw，函数 aws_lc_0_29_0_SHA1_Final 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha256_block_data_order_hw，函数 aws_lc_0_29_0_ECDH_compute_key_fips 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha256_block_data_order_nohw，函数 aws_lc_0_29_0_ECDH_compute_key_fips 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_sha512_block_data_order_nohw，函数 aws_lc_0_29_0_ECDH_compute_key_fips 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_neg，函数 ecp_nistz256_point_mul_base 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_mul_mont，函数 ecp_nistz256_cmp_x_coordinate 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_sqr_mont，函数 ecp_nistz256_get_affine 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_ord_mul_mont，函数 ecp_nistz256_inv0_mod_ord 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_ord_sqr_mont，函数 ecp_nistz256_inv0_mod_ord 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_beeu_mod_inverse_vartime，函数 ecp_nistz256_scalar_to_montgomery_inv_vartime 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_select_w5，函数 ecp_nistz256_windowed_mul 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_select_w7，函数 ecp_nistz256_point_mul_base 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_point_double，函数 ecp_nistz256_dbl 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_point_add，函数 ecp_nistz256_add 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ecp_nistz256_point_add_affine，函数 ecp_nistz256_point_mul_base 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(bcm.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_md5_block_asm_data_order，函数 AWS_LC_TRAMPOLINE_MD5_Update 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(chacha.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ChaCha20_ctr32_avx2，函数 aws_lc_0_29_0_CRYPTO_chacha_20 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(chacha.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ChaCha20_ctr32_ssse3_4x，函数 aws_lc_0_29_0_CRYPTO_chacha_20 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(chacha.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ChaCha20_ctr32_ssse3，函数 aws_lc_0_29_0_CRYPTO_chacha_20 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(chacha.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_ChaCha20_ctr32_nohw，函数 aws_lc_0_29_0_CRYPTO_chacha_20 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(e_chacha20poly1305.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_chacha20_poly1305_open，函数 chacha20_poly1305_open_gather 中引用了该符号␍
  libaws_lc_sys-3e95c455c3f6a66e.rlib(e_chacha20poly1305.obj) : error LNK2019: 无法解析的外部符号 aws_lc_0_29_0_chacha20_poly1305_seal，函数 chacha20_poly1305_seal_scatter 中引用了该符号␍
  .\target\release\deps\sqlx_macros-652649a3672bf2a1.dll : fatal error LNK1120: 79 个无法解析的外部命令␍

Later, after some trial and error (without any changes to the code, toml, or lock files—first deleting all my code, building an empty project successfully (cargo build --release, not tauri build), and then adding my code back in—a very, very strange behavior), the build succeeded. However, the json function is unresponsive (though I can still get the response headers).

I’m not sure if this issue is directly related to the aws-lc-sys crate, but problems with aws-lc-sys were present throughout my troubleshooting process. I’m sharing this in case it helps identify the root cause.

[✔] Environment
    - OS: Windows 10.0.19045 x86_64 (X64)
    ✔ WebView2: 136.0.3240.76
    ✔ MSVC: Visual Studio Professional 2022
    ✔ rustc: 1.86.0 (05f9846f8 2025-03-31)
    ✔ cargo: 1.86.0 (adf9b6ad1 2025-02-28)
    ✔ rustup: 1.28.1 (f9edccde0 2025-03-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.18.2
    - pnpm: 8.14.0
    - npm: 9.8.1
    - bun: 1.1.42
    - deno: deno 2.1.3

[-] Packages
    - tauri 🦀: 2.5.1
    - tauri-build 🦀: 2.2.0
    - wry 🦀: 0.51.2
    - tao 🦀: 0.33.0
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli : 2.5.0

[-] Plugins
    - tauri-plugin-opener 🦀: 2.2.6
    - @tauri-apps/plugin-opener : not installed!
    - tauri-plugin-clipboard-manager 🦀: 2.2.2
    - @tauri-apps/plugin-clipboard-manager : not installed!
    - tauri-plugin-shell 🦀: 2.2.1
    - @tauri-apps/plugin-shell : not installed!
    - tauri-plugin-updater 🦀: 2.7.1
    - @tauri-apps/plugin-updater : not installed!
    - tauri-plugin-http 🦀: 2.4.3
    - @tauri-apps/plugin-http : not installed!
    - tauri-plugin-fs 🦀: 2.2.1
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-single-instance 🦀: 2.2.3
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-global-shortcut 🦀: 2.2.0
    - @tauri-apps/plugin-global-shortcut : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/

hamflx avatar May 19 '25 07:05 hamflx

@FabianLars , Here's the output of tauri info:

[✔] Environment
    - OS: Mac OS 15.4.1 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.86.0 (05f9846f8 2025-03-31)
    ✔ cargo: 1.86.0 (adf9b6ad1 2025-02-28)
    ✔ rustup: 1.28.1 (f9edccde0 2025-03-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 22.14.0
    - pnpm: 10.7.1
    - npm: 10.9.2

[-] Packages
    - tauri 🦀: 2.5.1
    - tauri-build 🦀: 2.2.0
    - wry 🦀: 0.51.2
    - tao 🦀: 0.33.0
    - @tauri-apps/api : 2.5.0
    - @tauri-apps/cli : 2.5.0

[-] Plugins
    - tauri-plugin-http 🦀: 2.4.3
    - @tauri-apps/plugin-http : 2.4.3
    - tauri-plugin-os 🦀: 2.2.1
    - @tauri-apps/plugin-os : 2.2.1
    - tauri-plugin-sql 🦀: 2.2.0
    - @tauri-apps/plugin-sql : 2.2.0
    - tauri-plugin-dialog 🦀: 2.2.1
    - @tauri-apps/plugin-dialog : 2.2.1
    - tauri-plugin-fs 🦀: 2.2.1
    - @tauri-apps/plugin-fs : 2.2.1
    - tauri-plugin-clipboard-manager 🦀: 2.2.2
    - @tauri-apps/plugin-clipboard-manager : 2.2.2
    - tauri-plugin-shell 🦀: 2.2.1
    - @tauri-apps/plugin-shell : 2.2.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../src

caol64 avatar May 19 '25 07:05 caol64

tauri 2.4.1 works for me (I didn't just roll back tauri, but also the entire lock file).

tauri info 
[✔] Environment
    - OS: Windows 10.0.19045 x86_64 (X64)
    ✔ WebView2: 136.0.3240.76
    ✔ MSVC: Visual Studio Professional 2022
    ✔ rustc: 1.86.0 (05f9846f8 2025-03-31)
    ✔ cargo: 1.86.0 (adf9b6ad1 2025-02-28)
    ✔ rustup: 1.28.1 (f9edccde0 2025-03-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.18.2
    - pnpm: 8.14.0
    - npm: 9.8.1
    - bun: 1.1.42
    - deno: deno 2.1.3

[-] Packages
    - tauri 🦀: 2.4.1, (outdated, latest: 2.5.1)      
    - tauri-build 🦀: 2.1.1, (outdated, latest: 2.2.0)
    - wry 🦀: 0.50.5, (outdated, latest: 0.51.2)      
    - tao 🦀: 0.32.8, (outdated, latest: 0.33.0)      
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli : 2.5.0

[-] Plugins
    - tauri-plugin-clipboard-manager 🦀: 2.2.2
    - @tauri-apps/plugin-clipboard-manager : not installed!
    - tauri-plugin-shell 🦀: 2.2.1
    - @tauri-apps/plugin-shell : not installed!
    - tauri-plugin-single-instance 🦀: 2.2.3
    - @tauri-apps/plugin-single-instance : not installed!  
    - tauri-plugin-updater 🦀: 2.7.1
    - @tauri-apps/plugin-updater : not installed!
    - tauri-plugin-opener 🦀: 2.2.6
    - @tauri-apps/plugin-opener : not installed!
    - tauri-plugin-global-shortcut 🦀: 2.2.0
    - @tauri-apps/plugin-global-shortcut : not installed!
    - tauri-plugin-fs 🦀: 2.2.1
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-http 🦀: 2.4.3
    - @tauri-apps/plugin-http : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/

hamflx avatar May 19 '25 08:05 hamflx

tauri 2.4.1 works for me (I didn't just roll back tauri, but also the entire lock file).

tauri info

It also works for me.

caol64 avatar May 20 '25 02:05 caol64

me too

[✔] Environment - OS: Mac OS 15.4.0 arm64 (X64) ✔ Xcode Command Line Tools: installed ✔ rustc: 1.82.0 (f6e511eec 2024-10-15) ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21) ✔ rustup: 1.27.1 (2024-04-24) ✔ Rust toolchain: stable-aarch64-apple-darwin (default) - node: 22.14.0 - pnpm: 10.5.2 - yarn: 1.22.22 - npm: 11.4.1

[-] Packages - tauri 🦀: 2.5.1 - tauri-build 🦀: 2.2.0 - wry 🦀: 0.51.2 - tao 🦀: 0.33.0 - @tauri-apps/api : 2.5.0 - @tauri-apps/cli : 2.5.0

[-] Plugins - tauri-plugin-os 🦀: 2.2.1 - @tauri-apps/plugin-os : 2.2.1 - tauri-plugin-single-instance 🦀: 2.2.3, (outdated, latest: 2.2.4) - @tauri-apps/plugin-single-instance : not installed! - tauri-plugin-store 🦀: 2.2.0 - @tauri-apps/plugin-store : 2.2.0 - tauri-plugin-process 🦀: 2.2.1 - @tauri-apps/plugin-process : 2.2.1 - tauri-plugin-updater 🦀: git+https://github.com/tauri-apps/plugins-workspace?branch=v2#6c9e08dccb3ac99fccfce586fa2b69717ba81b52 (2.7.1) - @tauri-apps/plugin-updater : 2.7.1 - tauri-plugin-opener 🦀: 2.2.6, (outdated, latest: 2.2.7) - @tauri-apps/plugin-opener : 2.2.6 (outdated, latest: 2.2.7) - tauri-plugin-fs 🦀: 2.2.1, (outdated, latest: 2.3.0) - @tauri-apps/plugin-fs : 2.2.0 (outdated, latest: 2.3.0) - tauri-plugin-clipboard-manager 🦀: 2.2.2 - @tauri-apps/plugin-clipboard-manager : 2.2.2 - tauri-plugin-dialog 🦀: 2.2.1, (outdated, latest: 2.2.2) - @tauri-apps/plugin-dialog : 2.2.0 (outdated, latest: 2.2.2) - tauri-plugin-http 🦀: 2.4.3, (outdated, latest: 2.4.4) - @tauri-apps/plugin-http : 2.4.1 (outdated, latest: 2.4.4)

Sjj1024 avatar May 27 '25 10:05 Sjj1024

I have also been experiencing this issue only in tauri v2.5.1 but not in v2.4.1 as suggested

[✔] Environment
    - OS: Mac OS 15.5.0 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.87.0 (17067e9ac 2025-05-09)
    ✔ cargo: 1.87.0 (99624be96 2025-05-06)
    ✔ rustup: 1.28.2 (e4f3ad6f8 2025-04-28)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 24.1.0
    - npm: 11.3.0
    - bun: 1.2.8

[-] Packages
    - tauri 🦀: 2.5.1
    - tauri-build 🦀: 2.2.0
    - wry 🦀: 0.51.2
    - tao 🦀: 0.33.0
    - @tauri-apps/api : 2.5.0
    - @tauri-apps/cli : 2.5.0

[-] Plugins
    - tauri-plugin-fs 🦀: 2.3.0
    - @tauri-apps/plugin-fs : 2.3.0
    - tauri-plugin-process 🦀: 2.2.1
    - @tauri-apps/plugin-process : 2.2.1
    - tauri-plugin-updater 🦀: 2.7.1
    - @tauri-apps/plugin-updater : 2.7.1
    - tauri-plugin-http 🦀: 2.4.4
    - @tauri-apps/plugin-http : 2.4.4
    - tauri-plugin-os 🦀: 2.2.1
    - @tauri-apps/plugin-os : 2.2.1
    - tauri-plugin-single-instance 🦀: 2.2.4
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-dialog 🦀: 2.2.2
    - @tauri-apps/plugin-dialog : 2.2.2

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite

[-] iOS
    - Developer Teams: None

Serophots avatar Jun 07 '25 12:06 Serophots

The problem is solved on my machine by deleting /target, bun.lock, package-json.lock and node_modules, then running bun install again

Serophots avatar Jun 07 '25 12:06 Serophots

This also happened to me, updating, cargo clean, deleting node_modules, target... didn't work for me. Any idea?

cardo-podcast avatar Jun 28 '25 11:06 cardo-podcast

@cardo-podcast same request for you, please share the output of the tauri info command.

I'm also unable to reproduce it with the latest versions so i'd appreciate it if somebody could provide a minimal reproduction for me to try.

FabianLars avatar Jun 28 '25 13:06 FabianLars

I added a plugin and encountered the same issue I noticed that this change has updated the dependencies related to tauri Below is the information on git diff

tauri info 
[✔] Environment
    - OS: Mac OS 15.1.0 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.85.0 (4d91de4e4 2025-02-17)
    ✔ cargo: 1.85.0 (d73d2caf9 2024-12-31)
    ✔ rustup: 1.27.1 (2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 22.16.0
    - npm: 10.9.2
    - bun: 1.2.16

[-] Packages
    - tauri 🦀: 2.6.2
    - tauri-build 🦀: 2.3.0
    - wry 🦀: 0.52.1
    - tao 🦀: 0.34.0
    - @tauri-apps/api : 2.4.1 (outdated, latest: 2.6.0)
    - @tauri-apps/cli : 2.4.1 (outdated, latest: 2.6.2)

[-] Plugins
    - tauri-plugin-fs 🦀: 2.3.0, (outdated, latest: 2.4.0)
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-http 🦀: 2.4.4, (outdated, latest: 2.5.0)
    - @tauri-apps/plugin-http : 2.4.4 (outdated, latest: 2.5.0)
    - tauri-plugin-autostart 🦀: 2.5.0
    - @tauri-apps/plugin-autostart : 2.5.0
    - tauri-plugin-deep-link 🦀: 2.3.0, (outdated, latest: 2.4.0)
    - @tauri-apps/plugin-deep-link : 2.3.0 (outdated, latest: 2.4.0)
    - tauri-plugin-window-state 🦀: 2.2.2, (outdated, latest: 2.3.0)
    - @tauri-apps/plugin-window-state : 2.2.2 (outdated, latest: 2.3.0)
    - tauri-plugin-log 🦀: 2.3.1, (outdated, latest: 2.6.0)
    - @tauri-apps/plugin-log : 2.3.1 (outdated, latest: 2.6.0)
    - tauri-plugin-opener 🦀: 2.3.0, (outdated, latest: 2.4.0)
    - @tauri-apps/plugin-opener : 2.3.0 (outdated, latest: 2.4.0)
    - tauri-plugin-single-instance 🦀: 2.2.3, (outdated, latest: 2.3.0)
    - @tauri-apps/plugin-single-instance : not installed!

lock-diff.txt

hanaTsuk1 avatar Jul 05 '25 15:07 hanaTsuk1

@cardo-podcast same request for you, please share the output of the tauri info command.

I'm also unable to reproduce it with the latest versions so i'd appreciate it if somebody could provide a minimal reproduction for me to try.

Hey, I realized that I was using a wrong url that was the problem. In both v2 and v1 it results in a hanged request, how should I prevent this?

If it helps I made the same request.post to the same wrong url, the result is an inmediate

raise SSLError(e, request=request)

requests.exceptions.SSLError: HTTPSConnectionPool(host='nextlcoud.<myserver.com>', port=443): Max retries exceeded with url: /index.php/login/v2 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1000)')))

using browser an "SEC_ERROR_UNKNOWN_ISSUER" error is thrown. But the plugin didn't raise this error.

cardo-podcast avatar Jul 06 '25 16:07 cardo-podcast