I press save, it looks like it’s saving (wait spinner comes up and goes away), but it’s not saved.
It started with not being able to update the name. Then I noticed the Aeros thinks the track is not saved in all the usual spots (save button still active, prompt to save when exiting, etc.) Tried going to other screens and coming back, but same issue.
The track is setup to save on the internal storage.
The only thing odd I can recall is first I tried to change the name unsuccessfully. Nothing odd in the name like spaces. I think the name is unique.
Pretty sure I pressed “Save” while the keyboard was up the first few times. I later tried exiting the keyboard before pressing save, but it did not fix it. (FYI “exit” from the keyboard or go-to next field is a pretty bad experience; not intuitive)
This was a new song, perhaps the first new one in v3.0 that I created.
The only things left for me to do is to create a new song and/or power cycle to verify the changes are lost.
Techinal Rambling: Do you have more than one thread running or multiple places the “state” of the song save is maintained that you try to keep in sync? Are you waiting for callbacks? UI threads can have subtle, non-reproducible issues with visibility, and it’s generally harder to protect yourself in embedded systems.