Add remote error capture to release builds #44

Open
opened 2026-02-24 08:33:53 -08:00 by puregarlic · 0 comments
Owner

After implementing the fix described in #41, we've been able to successfully build a --release for the client application. However, this build does not include the ability to open the developer console, so we have no way to access logs or view error messages. Considering that tracing has a Sentry subscriber, we should integrate this after #43 so we can collect errors from folks testing out the release build.

After implementing the fix described in #41, we've been able to successfully build a `--release` for the client application. However, this build does not include the ability to open the developer console, so we have no way to access logs or view error messages. Considering that `tracing` has a Sentry subscriber, we should integrate this after #43 so we can collect errors from folks testing out the release build.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
puregarlic/microclimate#44
No description provided.