100% reviewed source file: 'en_US.json'
on 'es_419'.

The server running is using a local dinky server, pls no abooze.

TODO: Implement Sentry catcher to ALL EXCEPTION HOLY THAT IS A LOT

100% reviewed source file: 'en_US.json'
on 'zh_CN'.

`USEREMOTELOGGING`, automatically enabled on Preview & Debug branches for obvious reasons.

update logger types

Does not initialize or de-initialize the utility.

Note: An app restart may be required when selecting the option

sends it to Sentry so we don't have to refactor all our exception calls

Move SentrySDK init to its own helper

…nts' into sentry-error-collection

This added current log for when exception is sent to Dsn

1. Redacted username in the log file when its not debug build
2. Properly dispose SentrySdk when toggled off
3. Pipe SentrySdk log to Logger
4. Use correct flusher for SentryHelper.cs
5. Fixed cleaner loop for ExceptionHandler_ForLoop by @neon-nyan

Co-authored-by: Kemal Setya Adhi <dev.kemalsetyaa@gmail.com>

No need for adding Sentry's ExceptionHandler on catcher that has SendException already

Grabbed from Velopack's Implementation with adjustments to make the COM Interop compatible with AOT/Trim

100% reviewed source file: 'en_US.json'
on 'ja_JP'.

Note:

- Some submodules cannot import SentryHelper, which is in `Hi3Helper.Core`
- Some calls are asynchronous, mostly for the handled exceptions, but also where it felt best to use them, feel free to change them if needed
- Most are categorized as `UnhandledOther`, but if we feel the need to change some, we can, it simply affects tagging on the frontend dashboard.

100% reviewed source file: 'en_US.json'
on 'id_ID'.

1. Only uploads log file when exception is unhandled
2. Add cache dir path using Collapse's LocalLow data path
3. Dispose _loopToken before creating a new one to prevent memory leak
4. Reordered LogWriteLine on initialization
5. Release exception redirect event when feature is disabled

This is possible thanks to our adaptation of the new ShellLinkCOM API using COM Wrapper

I'm eepy

Also add a way to disable log uploading. This is due to a bug(?) where log upload length reported as 0 and causes BadRequest error. See getsentry/sentry-dotnet#3747

HOLY

1. Use Sentry's own backend
Still at testing phase, if any change happens it will be changed again to our self-hosted instance.
2. Add a way to disable via system environment variable
Setting env var "DISABLE_SENTRY" to true or 1 will disable exception handling
3. Omit IP address from being sent
4. Regionalized SentryHandler.cs
5. Updated PRIVACY.md

1. Use the InnerException if exception caught is an AggregateException
2. Throw TCE/OCE to the bin and not upload them
3. Deduplicate exception handling mechanism and use an inner method instead

Also set the environment as either Debug/non-debug based if there is any debugger attached

https://docs.sentry.io/platforms/dotnet/configuration/msbuild/

# Main Goal
Add a way for Collapse to automatically report errors to a self-hosted
instance of SentrySDK compatible server

oopsies....

Link the native lib directly on main app
Need to remove this once they fixed it

See getsentry/sentry-dotnet#3484

100% reviewed source file: 'en_US.json'
on 'es_419'.

+ Move PInvokes for CoCreateInstance
+ Move PInvokes for ResizableWindowHook

This due to the buffer getting flushed by the GC while the WindowRect data is being accessed. This commit is switching from unsafe implementation to more safer approach

100% reviewed source file: 'en_US.json'
on 'zh_CN'.

100% reviewed source file: 'en_US.json'
on 'id_ID'.

This way, user will be asked to download and install the missing VCRedist

#607

100% reviewed source file: 'en_US.json'
on 'es_419'.

100% reviewed source file: 'en_US.json'
on 'zh_CN'.

100% reviewed source file: 'en_US.json'
on 'es_419'.

100% reviewed source file: 'en_US.json'
on 'ja_JP'.

…click

Yes, I use artificial delay, deal with it 😎

damn you vulkan_gpu_list_config.txt (╬▔皿▔)╯