Page 1 of 1
App crashes again if menu is opened
Posted: March 2nd, 2023, 7:37 am
by mibru
The ErgData app crashes if you have the menu opens through saving.
Steps to reproduce:
1. Setup bikeerg and open ErgData app
2. Setup a training
3. Do the training
4. Open the menu before saving the results and leave it open
5. Finish the training
Result: app crashes and doesn’t save and sync results. Not possible anymore
Expected result: app saves the results and syncs them
Re: App crashes again if menu is opened
Posted: March 2nd, 2023, 7:50 pm
by Cdub
Simple fix. Save the row in ErgData before you screw with the menu!
Basically, you’ve been closing the session while the PM5 is in the middle of offloading ALL the data.
I’ve been bitten by this “hurry up” syndrome myself and had to manually upload from the PM5 to the logbook. Patience is a virtue.
Re: App crashes again if menu is opened
Posted: March 2nd, 2023, 8:33 pm
by Tsnor
Cdub wrote: ↑March 2nd, 2023, 7:50 pm
Simple fix. Save the row in ErgData before you screw with the menu!
Basically, you’ve been closing the session while the PM5 is in the middle of offloading ALL the data.
I’ve been bitten by this “hurry up” syndrome myself and had to manually upload from the PM5 to the logbook. Patience is a virtue.
Good work around.
I think the SW devs will be very happy to see a repeatable scenario that causes a crash, and will fix the underlying bug if Mibru sends them a note. "Result: app crashes " is not what anyone intends.
Re: App crashes again if menu is opened
Posted: March 3rd, 2023, 8:08 am
by Citroen
Send an email to
info@concept2.com as the Ergdata developers don't follow this forum.
Re: App crashes again if menu is opened
Posted: March 3rd, 2023, 7:53 pm
by Cdub
Tsnor wrote: ↑March 2nd, 2023, 8:33 pm
Good work around.
I think the SW devs will be very happy to see a repeatable scenario that causes a crash, and will fix the underlying bug if Mibru sends them a note. "Result: app crashes " is not what anyone intends.
Tsnor- I don’t think of it as a workaround or problem. I think especially in situations where you stop an interval set after ‘x’ cycles and many other situations, the app & the PM5 need a little time (10-15 sec) to shore data. Hitting the PM5 menu button disrupts that sharing.
Re: App crashes again if menu is opened
Posted: March 3rd, 2023, 10:10 pm
by Tsnor
Cdub wrote: ↑March 3rd, 2023, 7:53 pm
Tsnor wrote: ↑March 2nd, 2023, 8:33 pm
Good work around.
I think the SW devs will be very happy to see a repeatable scenario that causes a crash, and will fix the underlying bug if Mibru sends them a note. "Result: app crashes " is not what anyone intends.
Tsnor- I don’t think of it as a workaround or problem. I think especially in situations where you stop an interval set after ‘x’ cycles and many other situations, the app & the PM5 need a little time (10-15 sec) to store data. Hitting the PM5 menu button disrupts that sharing.
Cool. Understand your point.
In my world code is *NEVER* allowed to crash because the user hits buttons or gives nonsense input. " the app & the PM5 need a little time (10-15 sec) to store data." and they can create that time however they like including null response to buttons, masking for interrupts, etc. But the code cannot crash or lose data or give wrong answers. If you ask a user to wait a few seconds in product messages or documentation you STILL have to put in the defensive code that prevents crashes, lost data and incorrect results.