Android Question Unfortunately (app) stopped

fasilosman

Active Member
Licensed User
Longtime User
I had a working project in version 3.8.
When I upgraded the B4a to 4.0 and run the project in device and AVD it says Unfortunately (app name) stopped.

Please help me in this regard
 

fasilosman

Active Member
Licensed User
Longtime User
Hello,
Is there any Debug information at all?
the message it appears just after "waiting for IDE debugger to connect" and the debugging stops. I have attached the a screen shot about debugger information.
 

Attachments

  • Untitled.png
    Untitled.png
    45.9 KB · Views: 116
Last edited:
Upvote 0

fasilosman

Active Member
Licensed User
Longtime User
You should not initialize any object in Process_Globals.
I have moved the codes to sub global and tried but the same is happening.
I have attached the screen shots.

Note(3.8 version was worked fine)
 

Attachments

  • 01.png
    01.png
    84.9 KB · Views: 115
  • 02.png
    02.png
    275.2 KB · Views: 107
Upvote 0

fasilosman

Active Member
Licensed User
Longtime User
Thanks every one. I found the problem.
I have initialized object in a different module. But not in the Main module
 
Upvote 0

devlei

Active Member
Licensed User
Longtime User
I am having the same problem as fasilosman described in first post. I upgraded to B4A v4 and now get the "Unfortunately, [my App] has stopped" error message.

The error log gives the following:
LogCat connected to: emulator-5554
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
maininitializeProcessGlobals (java line: 1408)

java.lang.VerifyError: b4a/bettaman/reports
at b4a.bettaman.main.initializeProcessGlobals(main.java:1408)
at b4a.bettaman.main.afterFirstLayout(main.java:94)
at b4a.bettaman.main.access$100(main.java:16)
at b4a.bettaman.main$WaitForLayout.run(main.java:76)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:825)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:592)
at dalvik.system.NativeStart.main(Native Method)

I have checked all the modules, but can't see anywhere that an object has been initialized in a Process_Globals. I notice I have some Process_Global variables in different modules with the same name - would that cause the problem?

Any assistance would be greatly appreciated!
 
Upvote 0

devlei

Active Member
Licensed User
Longtime User
Why would this only make a difference after upgrading to B4A v4? Everything worked 100% for the last year on the same devices until I installed v4.
 
Upvote 0

devlei

Active Member
Licensed User
Longtime User
I uninstalled B4A v4, reinstalled v3.8, then it runs ok again. In the first post of this thread fasilosman also appears to have had the same problem.

Any further suggestions of what I should be looking for?
 
Upvote 0
Top