Brolin McKay wrote:
This is a known issue, working on it.
OK, but there are two issues at play here. Are *both* of them known, and are *both* of them being worked?
1) Issue when iFly has both an about-to-expire set of data loaded and an about-to-come-alive set of data loaded, and gets confused about which expiration date to show for data. (Previously explicitly acknowledged by Walter as in-work.)
2) Issue where iFly is not reporting expiration dates for RealView imagery (which may be normal behavior, since those don't have formal "expiration dates"? But then why are they listed as an option to show expiration dates for?) (Ambiguously acknowledged by Brolin, but not clear whether he was referring explicitly to this issue or was just repeating Walter's acknowledgement of the other, different issue.)