dever wrote:now, when de app crashes in one error, the app just closes, a message like "the app stopped to work" shows and I cant see what happend where.
I dont know why...
Dever, this type of app crash (called a Forced Close (FC)) has happened to me too, with B4A. I found the only way to fix it was to find a backup version of the app you are writing that worked correctly (without FCing). Then add code to bring it up to the newest version (which crashes).
This means you need to have made a backup of your app's source folder on a regular basis, so you can take a step backward if you meet an unresolvable problem (like the code starting to FC).
I am assuming this FC event doesn't happen on all apps you write, just the one you are currently working on. If not then I wonder if a complete re-install might not fix it, maybe with a later/higher version of Java SDK?
I think 'FC' happens because there is an incompatibility between the app (and its Java level) and the Android version/hardware build of your attached device. But any issue can cause it. Android is like that. I have seen that it happens after I have added some library or other code and if you can find that you may get back to normal. Maybe someone with more experience with B4A might comment.