libc++abi.dylib: terminating with uncaught

Bug Reports
1

libc++abi.dylib: terminating with uncaught exception of type uThrowable: Uno.Exception

in Fuse.Scripting.JavaScriptCore.g.cpp

catch (const uThrowable& __t)
{
    if (uIs(__t.Exception, ::TYPES[0/*Fuse.Scripting.Error*/]))
    {
        ::g::Fuse::Scripting::Error* e = (::g::Fuse::Scripting::Error*)__t.Exception;
        *exception = ::g::Fuse::Scripting::JavaScriptCore::JSValueRef::MakeString1(uPtr(_context)->_context, uPtr(e)->Message());
    }
   // else throw __t; // <------ hot fix 
}
2

Hello Kevin!

Can you provide a small reproduction or a stack trace with break on exception turned on? The exception doesn’t originate from the code you’re showing, it’s only being re-thrown there, so the only thing this tells us is that the exception happened in some Uno code invoked from JavaScript, which could basically be anything.

Cheers!

3

Hi Olle,

the error pops up when running ImageTools.getBase64FromImage(file).then(function(base64Image) { console.log("The base64 encoded image is \"" + base64Image + "\""); });

4

Hey again Kevin,

I’ve created an internal issue on this and we’ll get back to you when we know more. Thanks!

5

hey olle,

there was a problem the way i was using ImageTools now this is fixed ImageTools.getBase64FromImage({ path: file, name: "Some random name" })..... the libc++abi.dylib: terminating with uncaught has gone as well