Current Activity is null about plugin.firebase

[TobiasBuchholz]

PR #122 is now merged into the main branch and released with version 1.3.0.

[vhugogarcia]

I am facing the same issue you are @djordje200179 . Did you find a workaround for it?

[djordje200179]

@vhugogarcia Nope :/
I have tried a lot of things, but that didnt solve the problem. And unfortunately owner of the repo didn't say anything about the issue. So we are stuck until someone figures out what we are doing wrongly.

[vhugogarcia]

I tried to implement Analytics on my own following the same logic from this plugin without success. After debugging the issue the activity is not null, somehow the Initialize static method is not assigning correctly the object for instance it is null.

Plugin.Firebase/src/Android/Analytics/FirebaseAnalyticsImplementation.cs

Line 16 in c2d5c5f

_firebaseAnalytics = FirebaseAnalytics.GetInstance(context);

The code line above in the link is the one that is not being triggered somehow, I'm not sure why. I'm still investigating...

[TobiasBuchholz]

Hi, sorry for not giving any feedback yet, I was hoping the problem might have solved itself. If you provide me with an example project with this issue I can take a look and try to help.

[tranb3r]

Duplicate of #17

[tranb3r]

I'm also having this exception sometimes, in two different situations:

• app resumes after a period of inactivty (activity destroyed)
• app launched after the process has been started by a background worker

I haven't been able to debug the first situation.

However the second situation is easy to reproduce, and here is what happens:

• the background worker starts, of course there is no activity so Platform.CurrentActivity is null (which is legit)
• when a call to CrossFirebaseAuth.Current is done (by the worker), the constructor of FirebaseAuthImplementation is called ; in this constructor, an exception is thrown when getting Platform.CurrentActivity on GoogleAuth init.
• as CrossFirebaseAuth.Current is using a Lazy valueFactory, any attempt to initialize again FirebaseAuthImplementation is failing, even if it's done later in the app when an Activity does exist.

So, one problem is that an exception is thrown in the constructor of a class which is called by a Lazy valueFactory.
This problem can be avoided if the Platform.CurrentActivity is not retrieved in the constructor. Which is exactly what I've done in PR #122