Building game causes first dialogue coroutine to be inactive.

Unity Engine
1

I am making a Ace Attorney inspired themed Investigation game, and in the editor everything works fine. Once clicked in a certain spot, the UI comes up and the appropriate dialogue plays with a Type Animation. But when I export it, the animation does not play and It is instantaneous.
In Unity Editor:

In build:

The code is the same, everything is same. So why does this occur?

2

The game actually starts running while the Unity splash screen is still active… and in the editor sometimes there’s a hitch as things load… you could test this theory by inserting a very first scene that asks you to tap when you see it. I bet if you do that, you’ll see your first scene just fine.

If not, here’s how to debug it, device or editor:

You must find a way to get the information you need in order to reason about what the problem is.

What is often happening in these cases is one of the following:

  • the code you think is executing is not actually executing at all
  • the code is executing far EARLIER or LATER than you think
  • the code is executing far LESS OFTEN than you think
  • the code is executing far MORE OFTEN than you think
  • the code is executing on another GameObject than you think it is
  • you’re getting an error or warning and you haven’t noticed it in the console window

To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

  • is this code even running? which parts are running? how often does it run? what order does it run in?
  • what are the values of the variables involved? Are they initialized? Are the values reasonable?
  • are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

Knowing this information will help you reason about the behavior you are seeing.

You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as Debug.Log("Problem!",this);

If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.

You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.

You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer or iOS: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on Android

Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:

3

Hey, thanks for going this much into details. I’d just like to ask since the code and every other thing is the same, would this be considered a bug within unity itself? Thanks for helping!

4

Do you know of a piece of documentation that says the above is NOT correct? Or are you simply going on your own assumptions?

Beyond that, I suppose it is really a philosophical question. “Is this a bug or a feature?”