Fire debugger seems in stop state Fire not shows that state

Hello.

I placed native JNI map widget in my android app and run with fire debugger

and app seems frozen
However fire only saying there were NRE exception
but it is not showing continue button.
So i detatched USB cable from my laptop
and app resumed and worked as normal.

Since i can reproduce it everytime i build
i am going to send the project
But it contains api keys so i am mailing it to you.

Thanks, logged as bugs://78434

Go the mail, thanx; will have a look.

1 Like

Thank you.

I downloaded latest Fire.
and I found it is happening same.

App seems frozen due to the exception
but fire debugger doesnt allow me to continue.

Yes, RTM was built-in Friday, so even if this issue had been fixed yet (which it hasn’t), the fix would nit be in this build. :wink:

1 Like

Reproduced and fixed. it’s nit actually an NRE in you code; your code throws a “android.system.GaiException” exception without a message. The debugger does she extra checking for certain exception types (including android.system.GaiException) and didn’t handle the nil message well, and that is what NREed ;).

In tomorrows beta you shoud see the real exception

1 Like

I am getting some confidence to use fire now. Thank you.

1 Like

I am so sorry to report that it is not resolved.

It is showing different message

hm, but that’s not the bug you originally reported?

It is a same project. It doesn’t allow me click continue button. That way i can say it is same.

but it’s not. the bug you reported before was an NRE in the debugger on an empty exception message, and that’s fixed. this is a different bug altogether.

I dont know why nre is not showing up . I know it is a same project.

That said, i think i now what that second problem is — the debug engine/IDE has some issues with how it handles the rare case when a second exception comes in while it’s breaking from the first one (which seams like it should be impossible, but apparently not ;). I just made some enhancements to that scenario. if you want, can send you a new Fire build inn hour or so.

BECAUSE I FIXED IT! :wink:

I will wait for next beta build.
I dont want to disturb elements developments for other area.
Like you said it is a rare case.
I think element has potential so i renewed my academic license even though i know i might experience some bug and also i am a student who has budget constraints.
I tried years with element and i reported several bugs also.
Those are not for complaints.
I really want to experience the best of elements in my use case i want to spread it if i can sure.

It’s no trouble at all: in fact, it helps me fix and iterate faster to get the feedback. i’ve uploaded a new build for you now.

Thanks for the interim release.

I tested again and Fire IDE is crashed when I start the debug session.

ok. i id have details on the crash i could maybe do something about it.

I saw just crash.
Fire crashed without showing any bugs.
just crashed.
I could reproduced over and over again.
It is basically same project.