Error log saving problem

Dear all I would like to save the error log for my app.

I modified my app in order to generate a runtime error.

I tried to use web component with a “put” block inside the “when screen1 error occurred block”…but nothing appens.

After I tried to use tinyDB component “store value” block inside the “when screen1 error occurred block”…but when I call “get value” I have no values.

How can I solve this problem?

No issues here:

The errors list is correctly reported in Label2

You would need this on every real screen, but you can share one tinydb, suggest a separate namespace for this.

not all errors trigger the ErrorOccurred event

1 Like

Ho @TIMAI2

Can you share what is the error you used to see the error log?

In my app I used a get mills block without an input block.

I received the error message on my phone, but nothing saved in my log

Do you know what type of errors are not intercepted?

Sorry I don’t know, but it would be interesting to have a list ( or to have all errors trigger the event )

SMS permissions on Android 16.

I made an example. @TIMAI2 @davidefa

In this app I receive the Android error message on my phone “The arguments are the wrong number of arguments for GetMillis”, but nothing appears in label 2…why?

You have found one that doesn't get captured by the event

From the documentation:

image

What runtime errors are you expecting your app to generate ?

I dont know exactly what. My idea is that when I deploy to the “world”, my app will be tested by many devices and people, so errors could be. I would like to have a method to receive a log.

I tried with your “ask for permission “send message” and with this error the log is ok…

Now the question is: is this method a good way to receive the log from users? It will not be complete!

I thought you were geoblocking to the EU?

Get people to test the app for you, you should be handling any errors that arise in your app, or at least validating any data entry by users.

yes of course, I will do geoblocking for the EU, it was just a figure of speech

@TIMAI2

Only for errors that are captured by the ErrorOccurred block...

This is a programming error, you forgot to fill a socket. These type of errors can't be catched by the ErrorOccurred event.

You should fix all red errors first before testing

d4072e590a7e1f2dc8862719c3057ec446a92499

Taifun

It was a test to obtain an error message

Hmm, the text block does not throw a runtime error.

So, you should keep an eye on all errors and warnings and ideally fix them beforehand.