You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever an exercise is added to a program/routine, any further changes to the exercise's name are not reflected within the workout program. You would need to remove the exercise from the workout program and add it again.
As always, fantastic app.
BeatLink
To Reproduce
Steps to reproduce the behavior:
Go to 'Exercises'
Click on 'Add new Exercise'
Set Exercise Type to any
Set Exercise Name to "Change Me'
Go to Programs List
Create New Program titled "Test"
Go to editor
Add any number of sets of Change Me exercise
Go back to exercises
Rename "Change Me" to "Name Changed"
Go back to Programs List
Go to "Test" -> Editor
Notice that the exercise name is still "Change Me"
Expected behavior
The exercise names within existing programs should automatically update to match any changes to the name of the exercise
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Device: Samsung A21s
OS: Android 12
Browser N/A
Version FastNFitness 0.20.5.1 Database Version 25
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe your issue
Hey,
Whenever an exercise is added to a program/routine, any further changes to the exercise's name are not reflected within the workout program. You would need to remove the exercise from the workout program and add it again.
As always, fantastic app.
BeatLink
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The exercise names within existing programs should automatically update to match any changes to the name of the exercise
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: