-
Notifications
You must be signed in to change notification settings - Fork 626
Open
Labels
Description
[REQUIRED] Step 2: Describe your environment
- Android Studio version: Android Studio Electric Eel | 2022.1.1 Patch 2
- Firebase Component: Performance
- Component version: 20.3.1
[REQUIRED] Step 3: Describe the problem
Since version 20.3.1 it seems that Firebase Performance does not report the application startup time if Firebase is manually initialized.
Probably due to this check in FirebasePerfEarly
:
firebase-android-sdk/firebase-perf/src/main/java/com/google/firebase/perf/FirebasePerfEarly.java
Line 48 in 02b3365
if (startupTime != null) { |
As StartupTime is not initialized if Firebase is manually instantiated
firebase-android-sdk/firebase-common/src/main/java/com/google/firebase/FirebaseApp.java
Line 432 in 02b3365
// Don't provide StartupTime in direct boot mode or if Firebase was manually started |
Steps to reproduce:
Disable FirebaseInitProvider
and initialize Firebase in code with FirebaseApp#initializeApp(context)
, the App startup time won't be reported on Firebase Dashboard
SimonMarquis, hongyang-hua-20230331, vipulpelm, ganadist, Seonny and 6 more
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
[-]Application startup time not report when initializing FIrebaseApp manually api: performance type: bug [/-][+]Application startup time not report when initializing FIrebaseApp manually[/+][-]Application startup time not report when initializing FIrebaseApp manually[/-][+]Application startup time not reported when initializing FIrebaseApp manually[/+]argzdev commentedon Mar 10, 2023
Thanks for reporting, @louisbeaujeu. I was able to reproduce the same behavior. I'll notify our engineers and see what we can do here.
louisbeaujeu commentedon Apr 17, 2023
Thanks for the response ! Any update on this issue ?
argzdev commentedon Apr 17, 2023
Hi @louisbeaujeu, sorry for the radio silence. Our engineers are currently working on other issues at the moment. However, rest assured that this is being investigated and worked on.
That said, I'd like to ask for a favor for anyone else that encounters the same issue to kindly leave a thumbs up on the author's original post. This'll help us prioritize issues based on severity and demand. Thanks!
ganadist commentedon Oct 6, 2023
In my case, I want to measure app startup time with Firebase Perf.
But by this issue, I have a concern whether my app comply with legal compliance requirements such as GDPR.
muhammad-darmawan commentedon Oct 22, 2024
Hi, any update on this issue?
Thanks
exaby73 commentedon Oct 29, 2024
Hello @louisbeaujeu. I am unable to reproduce this issue with the latest BOM. Can you provide me some sample code that you can confirm reproduces this issue?
SimonMarquis commentedon Oct 29, 2024
@exaby73 the code still relies on this
FirebaseInitProvider.isCurrentlyInitializing()
call:firebase-android-sdk/firebase-common/src/main/java/com/google/firebase/FirebaseApp.java
Lines 433 to 437 in 0697dd3
which is a static private variable:
firebase-android-sdk/firebase-common/src/main/java/com/google/firebase/provider/FirebaseInitProvider.java
Line 40 in 0697dd3
modified only in
FirebaseInitProvider.onCreate()
firebase-android-sdk/firebase-common/src/main/java/com/google/firebase/provider/FirebaseInitProvider.java
Lines 66 to 78 in 0697dd3
... so, nothing has changed since, and the issue is still present.
Here is how to reproduce this:
google-oss-bot commentedon Nov 5, 2024
Hey @louisbeaujeu. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
SimonMarquis commentedon Nov 5, 2024
@exaby73 what do you need exactly?
Do you need a basic Android project with this?
'cause it is fairly trivial to do on its own, and it will probably not be that useful since we already outlined the exact issue here.
google-oss-bot commentedon Nov 12, 2024
Hey @louisbeaujeu. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
SimonMarquis commentedon Nov 12, 2024
😒 @google-oss-bot
google-oss-bot commentedon Nov 19, 2024
Hey @louisbeaujeu. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
SimonMarquis commentedon Nov 19, 2024
😒 @google-oss-bot
google-oss-bot commentedon Nov 26, 2024
Hey @louisbeaujeu. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Lyokone commentedon Dec 10, 2024
Moving to feature request, since the intended behavior is working.