we have a suite of apps that we keep in-synch & compile together (same
workspace). recently we had users complain that they were seeing a really old
version of one app--like jan-2015 old--instead of the latest build (jun-2016). i
checked the SWF timestamp, it had the correct date. but testing the app showed
it was indeed the jan-2015 version. i thought it was a deployment screw up, so
re-compiled the app & tested. same jan-2015 version. clean & build, new
workspace, shut down FB, re-booted w/s, etc. made no difference. same fossilized
version. i started watching the output dir & saw that the compiler emitted the
SWF in alphabetical order & the app in question (alluvium) started out with a
SWF size of 1.318mb. but by the time the whole suite was compiled, that app had
shrunk to 1.299mb & was the fossil version. re-compiled & grabbed a copy of the
larger SWF before the suite finished compiling & that was the correct jun-2016
version. yikes.
its like the compiler is digging up source from God knows where & re-compiling
that as it works thru the suite. i can't even find that source version anywhere
but buried in the code repository.
has anybody seen this kind of behavior? any ideas where to start looking to fix
it?
FB4.6
flex 4.13 SDK
target flash 14.0
thanks.
