Replies: 4 comments 2 replies
-
|
Hmm... making sure I understand, both the exports and imports worked prior to the refactoring releases, and now clicking export causes the app to crash? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it runs for 30 secs or so before it crashes though...there's A LOT of records now. 
|
Beta Was this translation helpful? Give feedback.
-
|
So...that makes me think you didn't actually break anything, but that the export feature is faulting out trying to deal with the massive dataset. Let me run some tests and I'll see if I can harden that feature, as it was honestly only put in initially to try and preserve data from one version to the next, so it isn't exactly robust. I'll keep you posted. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, pushing a patched version with a more complex backup protocol to see if this resolves the issue. Should be availble in about 30 mins |
Beta Was this translation helpful? Give feedback.
-
You are THE MAN! Sat here for a while... 
But then finished successfully! 
|
Beta Was this translation helpful? Give feedback.
-
|
Yup, basically the export feature was trying to cram all of your data into a single pull without staging it, which was maxing out your phone's memory capacity :-) Glad that was resolved |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
@9thLevelSoftware I can't thank you enough for all the time and effort you've put into the apps. Last week I got a wild hair about the last year of my data stuck in the old app. To say that I was annoyed that, seemingly, the only way to get my data out of the old app was to go into my profile, and manually click on every workout, into each exercise within that workout and export a CSV, is an understatement.
I realized I've been pushing the workouts into Google Fit. Granted, it's very limited data, but at least it would provide insight into avg weight and reps and I thought wouldn't it be great if I could import it into your new app. So I used Google takeout to export all my fit data and vibe coded something to parse through all the takeout data and ultimately generate a JSON file of all the exercises to restore into your app. I took a lot of liberties knowing my use case was specific to my fit data, so I was embarrassed to mention it until now because I figured it would make a hot mess of things for others.
Guess what.. looks like it made a hot mess for me. After you started pushing new versions out while you were refactoring, trying to make backups would crash the app for me. So in hopes of not losing more data I thought I'd start a discussion to see if you had any interest in what Gemini concocted for me in AI Studio.
Here's a random workout and it's exercises I was importing into 0.3.3 and then 0.3.4 ... I was able to make backups after importing in both those versions.
IDs are all generated, timestamps pulled out of fit data, mode is always Old School, since only concentric avg weight was being sent to Fit, I figured I'd just split the weight between cable A and B so I didn't have to worry about which exercises were single cable vs both. Since calorie info was in the fit data for the entire workout, I just split the cal evenly across each exercise.
Beta Was this translation helpful? Give feedback.
All reactions