Nev
Nev
FYI - We are now working on a new "extension" which may also help with this. The extension is being designed to allow all telemetry emitted while "offline" to be...
If you want to see the PR's [this (should) identify them](https://github.com/microsoft/ApplicationInsights-JS/pulls?q=is%3Apr+label%3Aoffline-support+)
> Will this latest release (3.1.0), which came out last week, make it possible to support offline situations in a react-native app? Depending on your detection of whether your offline...
This would mean that you have a large number of LARGE events that have been sent to the backend, but we (the SDK) has not received a response for, so...
There is no need for any `disableConnectionStringValidation`, you can still use the `disableInstrumentationKeyValidation` (as long as the connection string is well formed) This is because when we parse the `connectionString`...
Not exactly, while "InstrumentationKey" support is going away, this is just for directly setting the `instrumentationKey`, the actual `InstrumentationKey` while still exist, just encoded with the `connectionString` (like it is...
If your connection string includes the `ingestionendpoint`, then this will replace any `endpointUrl` you provide in your configuration. Just removing that from the connection string you provide should work. https://github.com/microsoft/ApplicationInsights-JS/blob/dce1e44afd47762fc4021885669852a6e37df8c7/AISKU/src/AISku.ts#L196-L201
All "keys" from the parsed connection string become lowercase -- so the one you provide doesn't have to have it all in lowercase.
Well bother! Lets tag this issue as a bug so that we can "update" the `parseConnectionString` to "pass-in" the "user default endpointUrl", this will allow the caller (the AISku.ts) to...
The other languages are controlled differently to the JS repo, and I'm not sure if they have any instrumentation key validation or the ability to have the endpoint declared differently....