Open carlonzo opened 11 months ago
one note I want to mention here: in my internal tests with few devices I used firstIdle
time instead of firstPost
time to calculate the preLaunchState
in https://github.com/square/papa/blob/31eebb3d70908bcb1209d82f066ec4d4377183ee/papa/src/main/java/papa/internal/Perfs.kt#L354
this looks like is working fine apart that pre 34 chained activity launches are all called before the firstIdle, when from 34 idle is called after the first activity launched.
Thanks, this is definitely worth looking into. I wonder what changed.
One thing I've noticed on my Pixel 7 Pro (API 34): after I manually kill the app, android starts the process again in background.
Here's the logcat:
---------------------------- PROCESS STARTED (15052) for package br.com.brainweb.ifood.debug ----------------------------
2024-04-09 17:23:07.003 15052-15052 GLP br.com.brainweb.ifood.debug D Pre-launch state: NO_ACTIVITY_NO_SAVED_STATE(WARM)
Is slow launch: false
Trampolined: false
Invisible Duration: 842629
Startup millis: 6225223
Duration: 510
---------------------------- PROCESS ENDED (15052) for package br.com.brainweb.ifood.debug ----------------------------
---------------------------- PROCESS STARTED (15605) for package br.com.brainweb.ifood.debug ----------------------------
Thanks, this is definitely worth looking into. I wonder what changed.
Hi, could you tell please, did you make some investigation of it?
Running Papa sample app I have noticed that on API 34
preLaunchState
was always warm (preLaunchState=NO_ACTIVITY_NO_SAVED_STATE(WARM)
). Adding some debugging log I notice that the recording of the first post on main thread is called before therecordActivityCreated
is called.This makes the calculation in
computePreLaunchState
never detect a cold state. Here are the logs I captured force-closing the application.API 31
API 34
is this a known issue or I am reading this wrong?