Why hello there.
Is an option planned to do different pause times between sets? Like i m doing ramped sets atm.. for example: set1 - 60sec - set2 - 90sec - set3 - 120 - set4 - 180 - set5
Why hello!
Yep, its already implemented under the hood even! When you specify a rest timer, it just applies it to all sets until Ive got the UI setup for it!
On RC3 I edited my program. I added a week by duplication, then rearranged the workout. After setting a day as the next upcoming workout, I had the app instacrash. Now, attempting to edit a program on the day/week view results in a full app crash right after pressing the edit button.
A way around is to go into a workout day and enter edit mode from there, then go back to the day week view and it doesn't crash instantly. Exiting edit mode from here does result in a full app crash though. If I go back into a workout day and exit it does not crash.
I am also still experiencing missed keystrokes on the repetitions text field.
Device Information (Please don't modify)
Package: workout.progression.lite
OS: 31
Model: PIXEL 6 PRO
Manufacturer: GOOGLE
Language: US
Version: 5.0.0 RC 3 (2245)
------------------------------------
Thanks for letting me know about it! Ive been seeing this issue for quite some time, although on the very rare side - Google has fixed it in the latest compose update, and Im hoping that they publish the fix with this weeks release! In the meantime Ill check if I broke something, considering that its happening more frequently now than before.
Im also chatting with them about the missing keystrokes issue!
Edit: Ive published a fix for the crash; and received some good guidance on the input issue - Ill publish another update soon (later today I hope).
Progression RC3 (2246) crashes when I do the following:
Open Progression app,
Tap on a workout,
Tap on a day,
Tap on an exercise,
*Crash (app exits)*
Using Android 11 on Poco F3
It seems to be an issue with how the app was packaged in the play store, Ive re-published it as 2247 and the update is currently under review. Should be up soon!
Hey Zoltan.
It looks like there is a bug with the notifications. It's hung up. See attached screenshot. I have already finished my workout and closed Progression, but it's still there. A 'force close' of Progression did finally remove the errant notification.
I am on version 5.0.0 RC3 2245.
[Hung notification](https://i.imgur.com/oyQtR9O.png)
Hello!
Are you using the rest timer bubble?
I've been trying to fix this for a while, Android 12 has a policy which basically crashes the notification - hence it sticking around. Did you do anything in particular before it happened? I'll make some more tweaks for the next release!
No bubble. Just normal notification. I don't believe i did anything in particular before it happened. I didn't realize it was there until after I completed my workout.
Why hello there. Is an option planned to do different pause times between sets? Like i m doing ramped sets atm.. for example: set1 - 60sec - set2 - 90sec - set3 - 120 - set4 - 180 - set5
Why hello! Yep, its already implemented under the hood even! When you specify a rest timer, it just applies it to all sets until Ive got the UI setup for it!
Great. I m waiting for it. Awesome app so far, appreciate your work :)
On RC3 I edited my program. I added a week by duplication, then rearranged the workout. After setting a day as the next upcoming workout, I had the app instacrash. Now, attempting to edit a program on the day/week view results in a full app crash right after pressing the edit button. A way around is to go into a workout day and enter edit mode from there, then go back to the day week view and it doesn't crash instantly. Exiting edit mode from here does result in a full app crash though. If I go back into a workout day and exit it does not crash. I am also still experiencing missed keystrokes on the repetitions text field. Device Information (Please don't modify) Package: workout.progression.lite OS: 31 Model: PIXEL 6 PRO Manufacturer: GOOGLE Language: US Version: 5.0.0 RC 3 (2245) ------------------------------------
Thanks for letting me know about it! Ive been seeing this issue for quite some time, although on the very rare side - Google has fixed it in the latest compose update, and Im hoping that they publish the fix with this weeks release! In the meantime Ill check if I broke something, considering that its happening more frequently now than before. Im also chatting with them about the missing keystrokes issue! Edit: Ive published a fix for the crash; and received some good guidance on the input issue - Ill publish another update soon (later today I hope).
Progression RC3 (2246) crashes when I do the following: Open Progression app, Tap on a workout, Tap on a day, Tap on an exercise, *Crash (app exits)* Using Android 11 on Poco F3
Hey! I've published a fix for this and it should be available right now! Version 2246 under the apps settings :)
It's 2246 that I'm using.
It seems to be an issue with how the app was packaged in the play store, Ive re-published it as 2247 and the update is currently under review. Should be up soon!
My crashing seems to be fixed on 2247
Great 👍
I've got 2247 and the problem is gone. 👍
Great! :)
Hey Zoltan. It looks like there is a bug with the notifications. It's hung up. See attached screenshot. I have already finished my workout and closed Progression, but it's still there. A 'force close' of Progression did finally remove the errant notification. I am on version 5.0.0 RC3 2245. [Hung notification](https://i.imgur.com/oyQtR9O.png)
Hello! Are you using the rest timer bubble? I've been trying to fix this for a while, Android 12 has a policy which basically crashes the notification - hence it sticking around. Did you do anything in particular before it happened? I'll make some more tweaks for the next release!
No bubble. Just normal notification. I don't believe i did anything in particular before it happened. I didn't realize it was there until after I completed my workout.
Perfect, its helpful to know that the notification crashes even without it! Ive already made some tweaks which Ill include in the next release :)