Gotcha’s,glitches and WiP

27 May

An interim build released to address a specific problem with German Passports which do not use ISO country codes in passports (only one in europe) plus some other minor changes version now 3.6.4 Android available now submissions to Stores (Apple/Microsoft) may take a little longer

21 May 2026

A new version which is an update to Dotnet9(the underlying technology which is required to improve the ‘cloud’ links) is now submitted to the Stores – we await approval there, but expect approval by the weekend.- The latest Android is on this website under ‘downloads’ The new version is 3.6.3 with build version 2 or 3
We have taken the underlying technology upgrade work as an opportunity to include improvements in User Interface though versions on bigger iPads may still look a little small ( a WiP) . Several obtuse glitches partly caused by the way in which UKBF servers (they are operating 2 separate systems) work. Workarounds are part of the update. The main effort has been to improve the ‘cloud’ service synchronisation. The improvement to the facility to use a second passport or an ID (useful for Common Travel Area to/from UK) has also been streamlined. Please note this does not refer to the facility/requirement to enter a passport for to/from UK trips. It only makes it possible to use an ID (driver licence) for trips within the UK/CTA zone. If you want to use an ID, this is not permitted inbound or outbound to UK unless it is a journey within the CTA (IRL,IoM,CI) If you wish to declare into/out of UK you must use a passport otherwise. But for the non UK jurisdictions you may alter the gendec/pdf to declare an ID before you send it to them. This will be found on the gendec/pdf pages once you have completed the main GAR. Final point – into and out of UK you must use the same passport (your primary or secondary) and maybe alter it on the declaration to the non UK jurisdiction. Finally if you try to send a GAR to UKBF before their 48 hour time limit it will ask if you wish to mark it as pending. It is the intention to make this more automatic but that too is a WiP and for now you must reopen the app and send it manually within the time limit. Many more things to do 🙂

9th May

version 3.5.10 is now release to Appstore (for mac and ios) microsoft store for windows and is on this website for Android. Very small changes including the mismatch of some airfield names mentioned previously

6 may

We’ve been notified of a small bug which occurs when importing the journey from a flightplan. the text for departure or arrival may not match with UKBF records and therefore the trip is not seen as involving UKBF – therefore no connection to UKBF is made (If you don’t see the UKBF receipt it hasn’t gone!). This only affects FP imports and then only on a small number of airfields where the description varies from UKBF records

This will be resolved very soon. 3.5.10 A workaround meantime is to delete the string of the UK end of the trip (depart/deastination) click on the X then select the airfield from the drop down list

5 May 2026
essential upgrade 3.5.9 affected iphone and ipad users on ios 26+ cause som ebuttons to disappear on some devices. Though not essential on all platforms we advise all to upgrade to 3.5.9 whatever OS or device. These versions will be available on the stores and on this website shortly

4 May win version submitted to Microsoft Store
MacOS version submitted to Appstore – awaits review iOs version submitted to Appstore awaits review – expected availability 48 Hours delete installations of versions prior to 3.5.7 or 3.5.8 on Apple

3 May 2026 : version 3.5.8 published – available immediately on mygar.net downloads for Android. All other platforms await processing of the appstores. solves issues arising from differences in handling by the 2 UKBF servers.(UKBF uses two different systems to process a GAR) Numerous improvements on UI in response to comments. t

__________________________________________________________________________

It’s still early days and we are working hard to slick up the operation – all feedback welcome

Here are some minor confusions

do I put in my email or username
1. well you’ll have set up a membership on this site. You can use your email as your user name but you have to put it in in both fields. The email is primarily to help you out if credentials are lost
  So if you’re more comfortable using your email as username then duplicate this in the ‘username’ field if you want and the app will recognise it
I keep getting this message ‘No Owner name’
1. on the aircraft screen several users have put in their full name in the first field – sorry the labels were not at all obvious (been changed) you must enter a ‘family name’ as well as ‘given name’ There is a ghost prompt saying ‘Doe’ under the family name field.. if you don’t put your surname in there it will spark this warning
Its been noted that the drop down list of aircraft types is missing some. you can ignore it or select ‘not specified’ For example the list comes from an old ICAO database and the GUID ref for a DA62 is actually recorded as the prototype DA50 which never went beyond prototype. In this case, until we can update embedded lists you can free form enter DA62 – ignore any message saying ‘no results’ and press enter to record what you’ve typed in. (that message just means it cant match it up to the icao ID and can be ignored) . Your free form entry will stay there. Also – (it’s a hangover from testing) but it is perfectly legal to leave the type blank – until we update the validation though best to use one of these two methods – enter freefrom/ignore no results or select not specified from drop down list
At present the details of the aircraft and owner/operator are only saved if you have entered them from main menu item ‘Manage Aircraft Lists’ (second on front page) this allows you to save up to 5 different aircraft. You can of course enter a completely different aircraft directly on the Manifest/Gar form but it will not automatically save as your favourites
If you are using a UKBF designated field (these are locations which have a private agreement with UKBF to arrive and depart, despite not being formal ports of entry). Most of these are private and wont be found on the list of fields unless you know the precise designator. Even so there is an issue with how UKBF server handle the information. Until this can be corrected with UKBF then the best advice is to use a lat/long. Click on the ‘departure’ or ‘destination’ label (to the left of dest/dept entry field) and a popup will allow you to specify a lat and long [Update latest 3.5.6 version to be released shortly will solve this but you must have the ‘field’s owner permission to use it]
When you register as a user/member on MyGar.net it is better to specify a ‘username’ as distinct from email. the email is really only there to enable a solution to a ‘lost’ password.
when I install the android app (and I believe it happens on other platforms) it appears to ‘hang’ when you first open it. == this maybe because you had a previous version and there is still a valid setting for a ‘cloud’ service. On first opening up, the app will try to do a complete synchronisation and this may take quite a while without there being a note that it is going on – give it a minute or two
one the PaxCrew entry form you may enter 2 passwords and one ID card. on the passport section there is a field for Longpassport number – this is the 28 characters on the bottom line of your passport page. You are not obliged to fill this in – if you dont and simply enter individual fields such as passport number/expiry/nationality/gender/DoB teh app will create this for you. But if you enter it it will fill in all the fields. It is largely designed to assist with OCR passport scanning but if you choose to enter it manually there are a couple of gotchas. 1) It must be the last MRZ line not the one above which is the name. 2) do not enter leading characters ‘<‘ the ‘< is a filler/space it is only valid if it is within the 28 characters the string must be exactly 28 characters long. If a passport number is only 8 characters long the correct MRZ is ‘PAC12345<‘ the ‘<‘ making up the passport number to 9 – which is followed by a check digit. German passports do not use the ISO country code – Instead of DEU the correct nationality is ‘D<<‘ A German MRZ looks like this CZ6311T472D<<8308126F34050192405<<<<<<<<10<<
But you do not enter it all 28 chars takes you up to ‘2405’ which exceeds the real longppno. You only enter CZ6311T472D<<8308126F3405019
some have asked where do I enter the crew/pax address and why. Well the address comes below the long section on passports x2 and ID so can get a bit overlooked. on why, well the UK system is transitioning from 2 to one but at the moment the demands of both need to be met. the new permission to travel system wants one of the crew to be marked as Pilot in Command and to have contact details for that person. The old system asked to either the owner or operators to be recorded as main point of contact

We are aware of some minor ‘non saving’/default saving which can look odd (particularly on ‘view’- these are being addressed for a release in next week or two (Late Apr 2026) but having checked the values transmitted are as entered on the GAR form.

Work in Progress

As of ver 3.2.6 the app now allows you to save 2 passports and an ID card detail to each saved crew//pax. Note while this has been asked for there is a misunderstanding how this works. When entering or leaving a jurisdiction which operates an Electronic Travel Authorisation (currently UK but EU are bringing in their own ETIAS later this year) then the declaration to that jurisdiction must be consistent – so you cannot declare one passport for entry and a different one for exit . Declarations for departure and arrival are quite separated . So for example if you wished to declare a british passport for arrival and/or departure from UK that is th epassport you would choose to put on the GAR. But the app also constructs pdf declarations for IRL/IoM/GSY/JSY/BEL/FR. If you wish to use, say, your EU passport or ID card for arrival then on the PDF view screen there is an option to change the Passport for the arrival/dept country (not UK) . It is a facility for holders of multiple Passports/Ids.

the new release should be available towards the end of next week ( 1 may2026) it improves labels and field and on some platforms sorts out issues for saving aircraft/crew.

We’ve been asked to get around the UKBF limitation on sending a gar more than 48 hours in advance. there’s been numerous reports of sGar accepting a GAR more than 48 hours in advance but then operatives/officers (UKBF) insisting the GAR was invalid and needed resubmitting. MyGar.net app (Manifest6) will not allow you to send more than 48 hours in advance so this should not occur. If you dont get a receipt you have not submitted. We have been working on a facility to ‘hold’ the GAR and send it on 48 hours – This has proved problematic as it requires the user to authorise the release of the Gar when within the 48 limit. This is very difficult – it requires the user to respond to a notification and as we are working on 4+ different platforms the notification can be missed or fail. Until we can work out a reliable way of doing this, the facility is still a WiP.

The Gov sGar relies upon sms message to report to you the ‘authority to travel’ That authority to travel ‘code’ is returned in MyGar as part of the GAR receipt and can be viewed by clicking on the relevant GAR in the garlist and selecting ‘view’ it is reported as a ‘Drest code’ which is the name of the UKBF system which handles this. at present the UK gov sGAR system does not seem to be able to send sms to IoM/GSY/JSY telephone numbers

dateline 28 April

I am preparing a new release – the latest Android is already up there. It will be submitted to Apple and Microsoft Store in the next two days but they can take and Ice Age to process. The new version should be 3.5.7
Most of the work has been improving the UI based on received comments but there have been UKBF issues related to non icao arrival and departure points which derive from the complexity of their running two different servers (a) for the old GAR and b) for the permission to travel. The current version is a fix for that but shouldnt affect too many. please keep feeding back your issues via info @ mygar . net