Android Question App has stopped. Open app again.

[Ronald Berardinis]

When I run the application in debug it runs fine and without error.
No error logs exist.
When in release, I get the following error.

I click a button on one form and then launch the form below that shows a list of items numbers.
all looks great.
But when I click exit it gets the "has stopped" error
like I said, works great in debug.

any idea why happening?
should this grid be placed in a panel on the same parent form and not pop up a form on top of the main form?
Thank you.

 

[Geezer]

What's the code for you exit button ?

 

[DonManfred]

More interestingly: Where is the FULL Errormessage?

 

[Ronald Berardinis]

there are no messages in the log when running in Debug mode.
I don't see messages when release.
code below.

 

[DonManfred]

Remove the TRY CATCH Block
Remove the Msgbox, use LOG Instead.

 

[Computersmith64]

Remove the TRY CATCH Block
Remove the Msgbox, use LOG Instead.

Also, don't post code as images. Use code tags instead.

- Colin.

 

[Ronald Berardinis]

I found a solution that appears to fix the problem.
I found this article.
"Using CallSubDelayed to interact between activities and services" by Erel.
i changed the code from this
StartActivity("actPopUp")
to this
CallSubDelayed2("actPopUp","Activity_Create", True )

I am happy.

 

[OliverA]

CallSubDelayed2("actPopUp","Activity_Create", True )

When you use CallSubDelayed, an Activity that is not running/started will be starter for you. This will call Activity_Create. Once up and running, you are calling Activity_Create again. Why?

 

[Ronald Berardinis]

No, the activity actPopUp is only called once.
List of part numbers to do an inventory physical count.
the activity that called actPopUp was actStockTake.
needs to return back to actStockTake.

 

[Computersmith64]

If actPopUp was started from actStockTake, all you need to do to return to actStockTake is tap the back button - or if you are intercepting the back button then call Activity.Finish in actPopUp. You shouldn't call Activity_Create.

- Colin.

 

[OliverA]

If you are calling Activity_Create to make actPopUp work correctly, you're doing something wrong. Most likely, you have code in Activity_Create that should be in Activity_Resume.

 

[Ronald Berardinis]

Oliver, not clear.
I tried this.
'StartActivity("actPopUp") comment out
and got errors above.

used below and this seems to work.
CallSubDelayed2("actPopUp","Activity_Create", True )

however, it seems this runs through the activity twice?

definitely not clean and work like I would wish.

what would be in the resume?

BTW, the back arrow gives the same error. Stopped.

 

[Computersmith64]

There is obviously something wrong in your code. It's not normal to have a crash when starting or finishing an activity. Your best bet would be to export your project as a zip from the B4A IDE & post it to this thread so we can take a look at it .

- Colin .

 

[OliverA]

I suggest reading https://www.b4x.com/android/forum/threads/android-process-and-activities-life-cycle.6487/#content and watching the video posted there. I'm guessing (a guess) that in Activity_Create you are checking the True flag and process something. If Activity_Create is called with false, something bombs out, meaning you are processing something in the true portion that you should be processing no matter what the flag is. This is just a guess. Also, see @Computersmith64's post above this in regards to posting a sample app that crashes.