Steps for the day lost if app not opened

[dayeggpi]

hi,

on nov 20, I did 8380 steps. the widget showed 8380 as well. on nov 21, I didnt open the app, the widget remained at 8380 at midnight. during the day, i obviously did steps, opened my phone several times, but the widget remained at 8380. at 19:46, I clicked on the widget to see the actual steps of the day (nov21) since the widget wasnt resetting. it reset the steps for nov21 to 0, but all the steps done for the day were lost.

screenshot attached for proof

[nvllz]

Hi, I'm aware of this problem. Well.. in your case there are two possibilities:

• your phone/app didn't record steps taken on Nov 21 – I tried to balance the step gathering part so it's battery efficient and doesn't record unwanted data (like adding steps when you pick up your phone), meaning it usually needs like continuous 5-10 steps in advance to listen actively and is more suitable for recording walks than being a reflection of how many steps you made during a day
• there was some interruption in the background or Stepsy foreground service was stopped by system

I would go for the second one to be honest. Every step detected by the app calls widgets to refresh, running the same function as when opening the app, and you mentioned seeing previous day's value in there, so it probably wasn't even called, which suggests app didn't record steps on this day. I guess it either crashed or service was killed.

What you can do now:

1. Fix your step data if you care (you need to estimate how many steps you have taken that day):

• export step data to a file and edit it using a text editor (notepad on PC or with an app like BeautyTxT)
• scroll to the bottom and replace "0" with a desired value (it will be like "1732444800,0" for gmt+0 timezone)
• restore updated backup file

2. Ensure Stepsy is not restricted by your system: you can check the dontkillmyapp website and find out how to make the app work in the background without any restrictions, which is vital for this app to work properly.

If there's any other reason of this problem, there's a chance I already fixed it with a feature of calling the app to reset steps at midnight in the background, pushed in one of the recent commits.

Sorry for the problems, I'll keep this ticket open for now.

[dayeggpi]

thanks for the answer. no worries, don't need to apologize, i dont have any critical business around the step count :) the system has stepsy as "do not kill it" to avoid that behavior, so i guess you must have fixed it already but i need to wait for the new version (as i already have 1.5.7 installed)

will keep you posted once i see the update and test it. thanks again

[dayeggpi]

hey @nvllz just to know, when do you think that a new version will be pushed ? thanks !

[nvllz]

@dayeggpi hi, I think it will be out by 2026.

[nvllz]

Okay, I'm closing it for now since it should be fixed. If you encounter this issue again, make sure you do everything you can to prevent your system from killing the app's foreground service. That's the only way I can think of for it to happen again.