Unexpected VM type failures now report the failing Objo source location

Status: Fixed
Fixed in: v26.8.4
Source discussion: https://forum.objo.dev/d/852-app-exited-with-exit-code-1-what-does-it-mean-and-what-causes-it
Last updated: 2026-08-17

Upvotes

0 upvotes

Uses your Objo forum account.

Public summary

An unexpected internal VM type mismatch can currently bypass Objo runtime-error handling, print a raw .NET stack trace, and leave Studio able to report only that the application exited with code 1. Studio should instead surface a source-mapped runtime diagnostic and debugger exception for the failing Objo instruction.