Issues resolved in FliteBrief 1.24

The following issues were resolved in version 1.24 of FliteBrief.

  • Certain NOTAMs with null purpose values are no longer incorrectly excluded from Briefing Packs.
  • When two users try to download a new OFP into Aviator, both users correctly receive the complete OFP. Previously, only the second user received an updated OFP.
  • When only the original loadsheet attachment is available, Aviator users now correctly receive updated loadsheet attachments.
  • Fuel Order emails now display the correct units of weight (as configured in the OFP).
  • The unit of measurement is now displayed correctly in the following fields of the OFP.xml file produced by the Sabre XML parser:
    • fuel unit
    • BurnOff
    • CumulatedBurnOff
    • FuelOnBoard
  • Aviator users no longer see an error when certain voyage and sector events are signed. The time and date property in the JSON payload is recorded as the time and date of the actual signature on the device instead of the time and date of the event transmission.
  • When the Include RVSM in companion app setting is turned off, Reduced Vertical Separation Minima (RVSM) checkpoints are no longer visible in the Enroute module of the FliteFolder mobile app mobile app.
  • The FliteFolder mobile app mobile app now correctly prints the selected documents, such as sector attachments and notices, instead of the OFP.
  • The Journey Log JSON is now correctly transmitted when the voyage is completed and signed off in the FliteFolder mobile app mobile app.