[Bug]

[mohamed234234]

Description

The Unity becomes unresponsive when clicking Stop. I am developing a game that uses Firebase databases. During testing, when I click Play and then Stop, the program becomes unresponsive. I don't know what is causing this. I don't remember adding any new code. Everything was working fine, but when I opened the program the next day, this problem suddenly occurred. While trying to understand the cause of the issue, I deleted the Firebase files in unity, and the Stop button started working perfectly again. Does this suggest that the problem might be related to the Firebase files?
And also
I discovered the file that caused the problem; it's the file inside Assets and "ExternalDependencyManager". This files: Google.VersionHandlerImpl.dll Google.VersionHandlerImpl.dll.meta When i delete this files the problem disappeared This explains why these two files are the cause of the problem, because even when I open the project, a loading window appears saying:

Reproducing the issue

No response

Firebase Unity SDK Version

13.15.0

Unity editor version

6000.0.66f2

Installation Method

Unity Package Manager

Problematic Firebase Component(s)

No response

Other Firebase Component(s) in use

No response

Additional SDKs you are using

No response

Targeted Platform(s)

Desktop

Unity editor platform

Windows

Scripting Runtime

Mono

Release Distribution Type

Pre-built SDK from https://firebase.google.com/download/unity

Relevant Log Output

If using CocoaPods for Apple platforms, the project's Podfile.lock

Expand Podfile.lock snippet

👀 Replace this line with the contents of your Podfile.lock!

[niccolo-hare]

Hi @mohamed234234, apologies for the delayed response. I tried testing this out with our quickstart sample, but I didn't encounter any issues such a crash or freeze. Though I would like to note that I was using Unity version 6.5 on a MacOS machine.

I think the Google.VersionHandlerImpl.dll is used to do some background version checks. And I'm thinking this might be encountering issues during Unity's reload process. Could you try the following steps, and see if it helps resolve the issue:

1. In Unity, go to Assets > External Dependency Manager > Version Handler > Settings.
2. Uncheck Enable Version Management.
3. Restart the Unity Editor.

Let me know how it goes.

[mohamed234234]

@niccolo-hare
I tried it now, but the problem still exists.

[mohamed234234]

@niccolo-hare
But there is something strange, when going to
Edit > Project Settings > Editor > Enter Play Mode Settings.
and Select:
"do not reload the domain or scene"
Instead of:
"reloading the domain and scene"

The problem is completely solved! I don't know why, nor do I know the function of this option or how dangerous it is?.

[niccolo-hare]

Thanks for letting me know that you were able to resolve the issue, @mohamed234234. I believe domain reload resets your scripting state to what it originally was before build (or rebuild). This provides you with a "clean slate" each time, but it seems to take more time as your code becomes more complex. It's possible your editor to became unresponsive if it took too long to complete the domain reload process.

Though I think it's safe to disable it. Doing so should allow you to enter Play Mode more quickly, as it skips a lot of initial cleanup steps that Unity does. But you may need to keep an eye on which processes are skipped. Like cleaning up static variables, for example. I would recommend checking the Unity docs (here) for more info on it.

With that, I'll go ahead close this issue since it looks like the issue is solved. But if you have other questions or clarifications, please feel free to reach back out and I'll re-open this issue.

[mohamed234234]

@niccolo-hare
Thank you, but the view i attached still appears whenever I run the project; it's annoying and time-consuming.

[niccolo-hare]

Hi, @mohamed234234. I tried testing again, but I'm still unable to reproduce the behavior with my sample projects. Based on my understanding, it seems you're using the Firebase Realtime Database SDK while this behavior is occurring. To help isolate it, could you try running our database quickstart app then see if the issue persists there?

This is code that we've verified works correctly, and should allow us to rule out any third party plugins or complex code setups from affecting the behavior you encountered. If it's reproducible there, then I can raise this to our engineers for a more in-depth investigation.

But if the quickstart sample works correctly, could you answer the following questions to help with our further investigation:

• Are you calling Firebase database methods via asynchronous calls? -- ex. are you calling Async/Await methods instead of Coroutines (similar to the quickstart samples)
  • If so, do you have any code set up that will clean these asynchronous methods in case the app is suddenly closed (ie. pressing Stop during Play Mode)
• Does the issue appear on a different machine, or a different or more up-to-date version of the Unity editor (ex. Unity 6.5)?
• Can you check if you have multiple copies of Google.VersionHandlerImpl.dll in your project?