Closed sgielen closed 2 months ago
It looks like the RPC did succeed normally, though. The error also does not reoccur when I perform the RPC again, so it's not blocking.
Looks like I get this error exactly once per new RPC I perform after switching to the beta channel.
Hi and thanks for reporting this bug. LoginService.krcol
implies that Kreya tried to open a Collection (krcol file extension).
Can you reproduce this bug consistently? If so, how?
Can you reproduce this bug consistently? If so, how?
I can reproduce it consistently, but only exactly once per new RPC I try to run, simply by sending the RPC. Luckily, we have a lot of them so I can reproduce for the forseeable future.
I'm not sure what a Kreya Collection is, I wasn't aware I was using this feature. I am sending gRPC-Web requests loaded from a .proto file.
I expect this bug will have to do with my current Kreya project state, so I'm not sure if the reproduction steps are complete, but I simply open Kreya, browse to any of my gRPC-Web methods by double-clicking one of them in the RPC browser to the left. Then, for all of them, Kreya typically already has the last Request I used loaded, so I just click Send. This then pops up the error, and when I dismiss it, the Response shows the gRPC-Web response as expected.
Ah, I managed to reproduce this. We will fix this in the next release
Kreya 1.14 has been released
Describe the bug I just switched Kreya from the stable to the beta channel. Most RPCs worked properly but when using a new RPC suddenly this error popped up.
Environment (if possible, copy the information from the error dialog or the About menu):