Hi all,
Since last update my hr broadcasting is finally working again. However, now my app is consistently crashing when opening up the next day. Only way to resolve is clear cache and data, log in again and add devices and start new training. When starting up the next day, same issue occurs. This week I had to clear data and cache every day using the app.
Any other people experiencing this?
Do you have the latest version of our app? We are not seeing any more crashes in our logs with the latest version of the app.
Yes the latest version fixed my HR broadcasting from Garmin. Don’t see any new updates available in google playstore. Can I somehow share logs or anything?
Remind me which trainer you have and version of Android. I would check permissions. I see one crash from 1 user with regards to foreground activity, meaning
settings/apps/trainerday/permissions/ turn physical activity on
I also see 2 other users getting some error regarding bluetooth connectivity. But all together this is 4 crashes in a few days. So it seems your issue is not being captured if you crashed multiple times.
I have a Kickr Core and android version 15
Ok yes try this permissions. But it’s very strange that clearing data would resolve it if it is permissions. I would also try not using your watch for 1 workout if you did not mind.
The issue is not while the workout.
When I start up the app without any data (clean install), there is no issue.
When adding my KICKR Core as a trainer, and Watch for HR broadcasting, still no issue and I can select any workout and do it without any issues.
However, next time, when starting up the app again to start another workout, it seems to be automatically retrieving the available bluetooth connections, and then it freezes and crashes within 5secs.
I’m at the office now, and if I open the app here, no freezing or crashing occurs. Probably because its not able to retrieve any already registered bluetooth connections. If I only enable broadcasting from my garmin and starting the app, it also seems to be working. So its the combination of trainer & bluetooth it seems.
I will tonight try again, but as it has happened already 3 times past week, I expect it tonight to fail again when its retrieving the existing bluetooth connections.
Ok can you tell me how soon it crashes and what screen you are on? If you wait to go to quick start for like 10 seconds. Maybe it’s a timing issue, maybe your bluetooth initializes very slowly and we try to connect before it initializes. What you could do at the end of your ride is just unpair your devices, or make sure they are not on when you start our app.
Any luck fixing this? This is one of the only remaining critical issues I know of.
Hi Alex,
Somehow it resolved itself. I’ve not had it occurring anymore luckily. So topic can be closed.
Thanks for the followup