gRPC-Web Developer Tools conflicts with unary interceptors introduced by grpc/grpc-web

I’v found that enabled gRPC-Web Developer Tools (by SafetyCulture) brokes up unary interceptors set up for grpc-web client. Interceptors are being not called when gRPC-Web Developer Tools are enabled.

Issue was found with next code:

const AuthInterceptor = function() {
    this.intercept = function(request, invoker) {
        request.getMetadata().Authorization = AuthService.GetAuthHeaderValue();

        return invoker(request);
    };
};

const options = {"unaryInterceptors": [new AuthInterceptor()]};
const APIClient = new APIPromiseClient(API_URL, null, options);

const enableDevTools = window.__GRPCWEB_DEVTOOLS__ || (() => {});
enableDevTools([
    APIClient,
]);


APIClient.me(new ProtobufEmpty(), {})
    .then(result => {
        ...
    })
    .catch(error => {
        console.error(error);    // <-- when gRPC-Web DevTools are enabled I receive error "no auth header" from my backend
    });

[jrapoport]

this will fix it https://github.com/SafetyCulture/grpc-web-devtools/pull/79

[CyborgMaster]

@jrapoport, sorry for the delayed response. Unfortunately that won’t help us here. The IT org has chrome locked down so we can only install extensions from their whitelist, so even if you published it, I’d have to get it through the approval process, which is a bunch of red tape. I understand their concern, there is a fair bit of malware on the chrome extension store.