[BUG] The core clash-rs cannot be used

[xmh0511]

Configuration group is empty uder the use of clash-rs.

The log is

ERROR clash_lib::app::profile: failed to read cache file: stream did not contain valid UTF-8, initializing a new one

AT
clash_lib/src/app/profile/mod.rs:119

AT
clash_lib/src/proxy/converters/vmess.rs:28

WARN clash_lib::proxy::converters::vmess: skipping TLS cert verification for 

startERROR:
invalid config: unsupported network: grpc

thread'MAIN'
panicked at clash/src/main.rs:68:6:

called`RESULT::UNWRAP()`
on an `Err` value: InvalidConfig("unsupported network: grpc")

ERROR clash_lib: panic hook: PanicInfo { payload: Any { .. }, message: Some(called `Result::unwrap()` on an `Err` value: InvalidConfig("unsupported network: grpc")), location: Location { file: "clash/src/main.rs", line: 68, col: 6 }, can_unwind: true, force_no_backtrace: false }

AT
clash_lib/src/lib.rs:158

[greenhat616]

clash-rs 的 GRPC 支持还没完全实现（目前遇到了实现上的一些问题）。

• 目前尝试的两个方法都不是按照 meta、sing 的思路走的。接下来应该会尝试完全复刻 Gun 的。

可以在这两个问题里进行跟踪：

• implement grpc for trojan and vmess Watfaq/clash-rs#203 grpc Watfaq/clash-rs#69

[xmh0511]

clash-rs 的 GRPC 支持还没完全实现（目前遇到了实现上的一些问题）。

* 目前尝试的两个方法都不是按照 meta、sing 的思路走的。接下来应该会尝试完全复刻 Gun 的。

可以在这两个问题里进行跟踪：

* [implement grpc for trojan and vmess Watfaq/clash-rs#203](https://github.com/Watfaq/clash-rs/pull/203) [grpc Watfaq/clash-rs#69](https://github.com/Watfaq/clash-rs/issues/69)

After such two PR had merged, I tried to re-compiler the latest code and replace the original packed clash-rs in this release version with the compiled clash-rs. The configure group is OK, however, test latency always gives the error.

[greenhat616]

clash-rs 的 GRPC 支持还没完全实现（目前遇到了实现上的一些问题）。

* 目前尝试的两个方法都不是按照 meta、sing 的思路走的。接下来应该会尝试完全复刻 Gun 的。

可以在这两个问题里进行跟踪：

* [implement grpc for trojan and vmess Watfaq/clash-rs#203](https://github.com/Watfaq/clash-rs/pull/203) [grpc Watfaq/clash-rs#69](https://github.com/Watfaq/clash-rs/issues/69)

After such two PR had merged, I tried to re-compiler the latest code and replace the original packed clash-rs in this release version with the compiled clash-rs. The configure group is OK, however, test latency always gives the error.

I tested it in latest dev build, the latency test in clash-rs is ok. Can you paste core and nyanpasu log here?
As far as I'm concerned, It could be clash-rs issue, if something wrong shown your log.

[xmh0511]

clash-rs 的 GRPC 支持还没完全实现（目前遇到了实现上的一些问题）。

* 目前尝试的两个方法都不是按照 meta、sing 的思路走的。接下来应该会尝试完全复刻 Gun 的。

可以在这两个问题里进行跟踪：

* [implement grpc for trojan and vmess Watfaq/clash-rs#203](https://github.com/Watfaq/clash-rs/pull/203) [grpc Watfaq/clash-rs#69](https://github.com/Watfaq/clash-rs/issues/69)

After such two PR had merged, I tried to re-compiler the latest code and replace the original packed clash-rs in this release version with the compiled clash-rs. The configure group is OK, however, test latency always gives the error.

I tested it in latest dev build, the latency test in clash-rs is ok. Can you paste core and nyanpasu log here? As far as I'm concerned, It could be clash-rs issue, if something wrong shown your log.

[greenhat616]

Could u upload the latest log file from this dir?

[xmh0511]

Could u upload the latest log file from this dir?

The log has some secret key, it's not safe to upload it here.

[greenhat616]

If you don't mind, you can delete any secret info, then send it to my email.

[xmh0511]

If you don't mind, you can delete any secret info, then send it to my email.

I sent them to your email.

[greenhat616]

If you don't mind, you can delete any secret info, then send it to my email.

I sent them to your email.

I have received logs you sent. I noticed that closed with error crypto error: BAD_DECRYPT are thrown when you visit sites that should match Proxy group. It seems clash-rs's vmess impl issue.

If possible, you can draft a minimal reproduction or post config in your proxies group, with secrets removed, and create a issue to clash-rs.

[4o3F]

Fixed by clash-rs core