Does anyone know origin of this error?

Getting Started Newbie Questions
#1

The error occurs when I press the Android back button to hide an overlay. My question is because I had never seen the origin of this error. Always the error lies in the location of my project, not in a repo.

#2

You’ve likely done one of these:

  • caused the deletion of an object before its transition is complete
  • caused the deletion of an object before some of your code tries to apply a transition to it.

Good news, you can now go directly to line 574 and find out what code is executing, but then you’ll still need to trace it back to the error in your code.

Make sure to use this setting in build.settings to get complete debug messages on your device:

settings = { build = { neverStripDebugInfo = true, }, ...
#3

@roaminggamer wao… sounds a lot of work…I’m using the last public build with android api level 27. The only thing I change is the options of “composer.gotoScene()” in the Android back button function in main lua.

I replace this:

composer.hideOverlay( "crossFade", 700 )

With:

composer.hideOverlay( options )

In which options is a table taken from the Corona documents where it explains how to configure composer transition options. 

I really would not like to change anything that has coded by a professional.

#4

line 574 of transition.lua:

local tMax = tween.\_duration
#5

Sounds like no work at all to me.  :huh:

Now you have everything you need to work this out. Thanks to the fact that the transition.* lib is now open sourced, there is no code in this process  you don’t have access to.

Nobody will be able to tell you the cause of this without seeing and running your project.  You will need to apply debugging skills and practices to work it out.  

Alternately, you could pay someone to figure it out: https://forums.coronalabs.com/topic/69420-hire-a-hitman-problem-solver-is-back/

#6

You cannot pass a table for hideOverlay AFAIK.

#7

@fungrip is right.

Also, what does your logcat log say?

There must be more information in the log than just the last error message.

#8

You’ve likely done one of these:

  • caused the deletion of an object before its transition is complete
  • caused the deletion of an object before some of your code tries to apply a transition to it.

Good news, you can now go directly to line 574 and find out what code is executing, but then you’ll still need to trace it back to the error in your code.

Make sure to use this setting in build.settings to get complete debug messages on your device:

settings = { build = { neverStripDebugInfo = true, }, ...
#9

@roaminggamer wao… sounds a lot of work…I’m using the last public build with android api level 27. The only thing I change is the options of “composer.gotoScene()” in the Android back button function in main lua.

I replace this:

composer.hideOverlay( "crossFade", 700 )

With:

composer.hideOverlay( options )

In which options is a table taken from the Corona documents where it explains how to configure composer transition options. 

I really would not like to change anything that has coded by a professional.

#10

line 574 of transition.lua:

local tMax = tween.\_duration
#11

Sounds like no work at all to me.  :huh:

Now you have everything you need to work this out. Thanks to the fact that the transition.* lib is now open sourced, there is no code in this process  you don’t have access to.

Nobody will be able to tell you the cause of this without seeing and running your project.  You will need to apply debugging skills and practices to work it out.  

Alternately, you could pay someone to figure it out: https://forums.coronalabs.com/topic/69420-hire-a-hitman-problem-solver-is-back/

#12

You cannot pass a table for hideOverlay AFAIK.

#13

@fungrip is right.

Also, what does your logcat log say?

There must be more information in the log than just the last error message.