Jeremy Meng

@dittmarconsulting thank you for the interests! I am looking into this, currently investigating what's needed to be able to use @azure/app-configuration package in react-native. Thank you for the pointer to...

The build error started between 6a429ef5ef9 and 59c7f7d2093, so very likely that rush update --full introduce some incompatible breaking change

we need to unpin the version pinned in https://github.com/Azure/azure-sdk-for-js/pull/30233 when the linked issue is fixed

So it seems we added the proxyPolicy to the pipeline because isNode is true probably because of node integration is enabled, but still the browser version of the proxyPolicy is...

or maybe @types/node shouldn't have breaking changes?

@JPStrydom did you meant that after changing to `createMessageProcessor` and `createMessageProcessor` you still see the issue happening? I would not expect that the subscription still receives errors after receiver is...