Latest fixes & improvements on 10.105.16612: eReporting fields support multiple tags and are consistently included in custom JSON submissions. Date and time input fields now respond across the full field area, improving usability and interaction consistency. New controls can be created in the Neo editor reliably without errors. Neo now avoids creating change logs when no actual changes are made. DateTime calculations correctly account for date transitions when evaluating time differences. Flight submission has been stabilised, restoring normal operation for all affected configurations.

eOFP input fields - interaction issues Incorrect field activation and random values fixed; input behaviour now works properly. App freezes when opening Neo Neo freeze fixed by optimising configuration loading; editor now opens smoothly. Crash during LMC workflow LMC crash resolved; workflow stable with responsive buttons and no freezing. Envelope graph & maximum weight assessment Boundary and max-limit values now validate correctly and display green.

fixed freeze on eofp

fixed time input in eofp

bug fixes

deploying internal staging to external

Small bug fixes and performance improvements.

Bug fixes: - missing eOFP data when switching between application Improvements: - OPT parser to support runway L or R

Bug fixes and internal architecture improvements. Portal improvement: Inactive users now visible and manageable in the new portal Until now, it was not possible to see or filter users based on their status (Active/Inactive) in the backend portal, which led to confusion and errors when inactive users already existed.

Fixes: 1. Cleaned the error backlog and implemented fixes for OS issues thrown to our error monitoring tool Improvements: 1. Refactored parts of our code to better log the system-based errors 2. Boost our plan for error monitoring/logging

Fixes: 1. Unit mismatch in Loadsheet We fixed an issue where fuel, cargo, and passenger units weren’t showing correctly in the Loadsheet when using different units (like kg vs lbs). The app now automatically handles the conversion, so you’ll get a popup when needed, and the loadsheet output will be saved in the right unit (aircrat unit). 2. Missing users in the portal Some active users weren’t showing up in the user list on the portal due to how the filtering was setup. That’s now corrected, and all users should be visible unless filtered out on purpose. 3. Logging out while offline Last couple of releases there was an issue with log out during offline usage. We’ve added a new setting named: BlockOfflineLogout - that disallows logging out when enabled and no internet connection is found. It will show a warning instead when the button is tapped 4. Loadmaster/cabin crew user access issues We had a bug where the Loadmaster role either couldn’t log in or had access to all pages, regardless of the setup. That’s now fixed, and role access works as expected. 5. Infant count in Loadsheet Previously in version 10.94, the Loadsheet only said that infants were onboard, but didn’t show how many. Now you’ll see “+ X infant” next to the total passenger count when applicable. 6. Azure MFA login & signing required two attempts Some pilots were getting an “Incorrect username or password” error when login in, signing a report, even when entering the correct details using Azure MFA integration. It worked on the second try, which was not intended case. This issue has now been fixed, and it should work on the first try. 7. Duplicate flights in the new portal Flights were sometimes listed twice in the new web portal. That’s now been resolved. We’ve also improved how flights can be filtered based on signed preflight or postflight status. 8. Windows app – install and UI issues There were some problems installing EFBOne on Windows (certificate warnings), and users couldn’t minimize or close the app. These have all been sorted out,

Adding new mapping for flightkey provider

Fixes

Print Button Restored The print button for PDFs (OFP, NOTAMs, ATC, etc.) was missing since version 10.89. It has now been restored to its original position once the PDF control (flight document) is opened. eOFP (Fuel and time check) - Burn-off Input Influences FOB Previously for some clients, entering and deleting a value in the burn off field caused an issue where an entry FOB in the eOFP would disappear. This has been fixed, burn-off input now correctly influences FOB without deletion. Incorrect eOFP Coordinates Some NavLog waypoints with a leading zero (0) were displayed incorrectly (e.g., W07051.6 was shown as W7051.6). This issue has been fixed to ensure accurate coordinate display. Error with Promoted Controls not visible in Production Some controls were promoted to production but did not appear in the layout. This issue's root cause has been identified and resolved, and the controls are now available. Screen Jumping Issue Fixed Users reported that the screen would randomly jump and become unresponsive when swiping up. It often took multiple repeated swipe attempts before the screen responded properly. It is fixed and it is working as expected. Loadsheet Limit Display Fixed The Limit (Kg) field in the Loadsheet (Masses tab) previously remained green even when loads were outside the limit, only correcting after switching tabs. User Login Issue Fixed Newly created users were unable to log in despite multiple password resets. The issue was caused by missing user roles, preventing access. This has now been addressed with the following updates: User Role Validation Added - Users without the required role (e.g., pilotuser) could not log in. This check is now in place to ensure proper role assignment. Updates for users page User Creation Moved to New Portal - The old portal now redirects to the new user creation page. Custom Password Rules for Admins - A new setting in the Airline App Setting Screen allows admins to define password rules using regex. For example, a 10-digit PIN can be enforce

OPT and mPilot fixes

Bug fixes

• Fixed crash on pdf • Fixed first page being blurry • Fixed loadsheet delay • Fixed loadsheet not being able to load on first render

fixes for pdf viewer fixes

Key Improvements for NOTAMs Enhanced Visual Differentiation for New NOTAMs: New NOTAMs are now labeled with a “New” tag and highlighted with a distinct color scheme at the top of the list. Previously Viewed NOTAMs are sorted below with the standard background color for easy distinction. Bookmarks Valid Across Flights: Bookmarked NOTAMs now stay saved for the same pilot across more flights. Our system checks NOTAMs validity during future flight downloads to ensure that valid NOTAMs are always available and outdated ones are removed. + fix for the update flight plan losing the bookmarked NOTAMS NOTAM Classification and Filtering: NOTAMs are now categorized into Airport, Approach, Runway, Taxiway, ATC, Airspace, Hazards, and Library. Pilots can filter NOTAMs by category using a dropdown menu with a multi-select option for a more focused and efficient review. Fixes for M&B issue related to average passenger weight.

Broker app fix

bugfixes

- Changed Logo to White BG - UI Improvments - Bug Fixes

Flight submission fix

Flight submission fix

API declaration file