This is a clone of the original issue which was caused by Glass trying to access main Java env after the main Java thread has been already detached.

The original problem was fixed by explicitly checking for the main Java env at the specific code location that was causing the problem, however, the issue potentially exists for all Glass APIs. The way to address it is to assert that the main Java thread is still attached at the time we try to retrieve it, and if it is not available, then we can throw Java exception on the calling thread to notify that things are really really wrong.