Since upgrading to Flash CC my colleagues and I have noticed several isntances of code disappearing. We would write code in the FLA on the timeline, save, export, and see the movie working only to be scolded by QA an hour later saying we didn't do any work! We then return to the FLA to find missing blocks of code. Perhaps there is some issue with FLA saving in Flash CC x64? Or perhaps the new code editor (which still lags, I was hoping the new Flash could finally pull of a text editor without lag with reliable code completion) just randomly loses things?
Are you upgrading an old project created in the previous versions of Flash to Flash CC or are you creating a new project in Flash CC itself?
One scenario that I can think of is when you upgrade a FLA created in the older version of Flash which has any AS2 code attached to instances on Stage. In this case the FLA will open up in Flash CC throwing a warning about AS2 code and on trying to save/publish the FLA the actions associated with the buttons or movieclips instances will be ignored.
Thanks and Regards,
Adobe Flash Professional Team
Yes, we are upgrading old CS6 projects. However all of the projects I've done in CC so far have been AS3. In some cases, we are even sharing projects between folks that still use CS6 and have noticed that movieclips containing groups of more movie clips do not port back too well but otherwise haven't had many problems.
Both times my code disappeared though I was the only one who had touched the FLA all day and only used CC and it happened at some point in the middle of development. What I found most intriguing is that it hasn't yet removed code that caused an error. It is usually like we write a for loop like so:
// some code
and occaisionally // some code will disappear but both the for loop and any code before and after will remain intact. My guess is that is related to saving or marking a file as saved. Perhaps I hit ctrl+s and the close the project and it lets me because the asterisk has disappeared but it was not yet complete. I had another save related bug in CS6 where for a couple months I would need to save twice in order to get the asterisk to go away every time and then one week it just started having to only save once again after no update. This happens on Windows 7 x64 by the way. I haven't had the chance to install Flash CC at home on my Windows 8.1 PC yet.
Update: Perhaps it is related to auto-recovery and/or file names somehow. My co worker was working on a file on the network drive and experienced this problem and promptly started working locally in an attempt to make it stop. He worked on the file for a couple hours without any problems. Another person had finished some work in a copy of the same FLA and uploaded it to the network. My co-worker opened the updated network FLA along side his local copy and code disappeared from both. I've since disabled auto-recovery. I'll update again if that solves the problem.
code added to a moveclip timeline will not be saved in flash cc unless something is changed on-stage. this is a known bug.
to prevent the problem, change something on-stage or don't add code to movieclip timelines (other than the main timeline).
Thanks for the heads up, in the most recent case however, my co-worker had no changed anything in his copy of the document but opening a different copy of the same document at the same time seemed to revert it to an older version.
Great to hear it has been fixed, waiting for update. I can confirm this bug. Has been happening to me lately and I thought I was losing my mind, seemed like every fix I made at the end of a session would then disappear on next start up. I am OCD about saving and this really caught me off guard. Just today I managed to recreate the problem several times by opening a movie clip tacking on some code on the end, going to file > save instead of my usual ctrl+s, then closing flash out all together upon return the newly added code was missing. This is a big minus. And yes this file is a port from CS6 but all AS3.
The update that contains fix for this bug is now available.
Please refer to the release notes for details on bugs fixed.