cadets-ca / ets Goto Github PK

To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.

If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.

For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue. For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue.

Resources

For information about testing your app and preparing it for review, please see Technical Note TN2431: App Testing Guide.

For a networking overview, please review About Networking.

Related #28

... so that pilot and student can enter their time in their respective log books (as a pilot, as a student, and as an instructor).

... generate by pilot and by student.

Do they want this in a CSV?

Under #28

Glider and Tow
As maintenance
I want a csv file
... so that they can use the numbers in other systems (AMS) or manual reports.
... use in Excel.

The Share Database menu option can only be used to share one region at a time. To be able to share every region, the recipient of the share link would have to go through a collection of share links, not only look at the first (arbitrary) one.

Any other issues with that concept?

Related to #28

... so that they can input those numbers into what??

Final TTSN: Total Time Since New
TNI : Time to Next Inspection
TTNI : Total Time of the Next Inspection
Issues per glider per day (instead of only per glider). Confirm with ETS how it is filled.

Why are there negative TNI numbers?
What is the purpose of having the number of flights on the top of the report? Could we export total flight / day / glider instead of a grand total? Does the total of Tow plane flights excluded?

Debert-Stats-Report-17-Jul-18-17-Jul-18.pdf

Porting this from #41 (comment).

The current interface for managing aircraft's TTNI, TTSN, & TNI is apparently confusing to some users, leading to incorrect values being entered and used.

We could probably help prevent that error from happening in the future by improving the language used on those fields to make it more explicit what they are for and how to use them (although there's still the problem of TTNI not being updated after an inspection all of the time).

Next Steps

To resolve this issue, please revise your app and test it on a device to ensure that it runs as expected.

Resources

For information on how to symbolicate and read a crash log, please review Tech Note TN2151 Understanding and Analyzing Application Crash Reports

crashlog-D7F31864-0F66-4891-88B9-B0B114F07DC2.txt
crashlog-8828296F-280C-4A22-9130-5063A8E0F4EE.txt

crashlog-167FA461-B180-4058-B005-0228E7C870AF.txt

Bring aircrafts and their TTNI.
When the aircraft release for service.

It should tell what ets is for and how people can contribute.

Currently all flights with a student glider pilot are automatically forced to have the Student Trg sequence, even when that sequence doesn't make sense (i.e. student is getting a ride in the tow plane, student is with a pilot that is not an instructor, etc). While you can go back to the flight and edit it after the fact it would be better to make the following changes:

• Narrow the cases that the autodetection of student pilots kicks in. For example, this feature should only trigger when the student pilot is in a glider, and the PIC is an instructor
• Make it an opt-in change instead of an opt-out change. A window should popup saying something along the lines of "PILOT X is a student and PILOT Y is an instructor, you mean to make this flight a Student Trg flight?" Options would be "Keep SEQUENCE Z" and "Change to Student Trg"

In reviewing the new version of the app, I have a few recommendations that I think we should take before releasing it to the CTCs:

• Remove personal info from the list of pilots (emails and names from the default entries are real)
• Replace the background image with a different image (no contact info, I think) #13
• Replace the app icon and app name with a new one (having both apps installed makes it very hard to tell the difference between the two) #13

Choose and tell which open source licence we use.

So they can import the data in other systems easily (for record keeping and AMS).

Pacific Region conducts fam flying in their 182 tow planes that can accommodate up to 3 passengers. The app currently only supports 1 passenger. They need the ability to log all passengers in the plane while conducting fam ops with these aircraft.

Might be easier to export and import when doing yearly validation of aircraft available.

In Central Region, each flight changes airports every week. When they move to a new airport, each pilot needs to have their profile updated individually to move them to the new site. This is upwards of 100 individual actions to move flight A to site B and flight B to site A each week.

The desired functionality is that the pilots at site 'A' in flight 'A' can be moved in bulk to site B using one action.

When adding flights from previous days, the Total Time Since New (TTSN) and the Time to Next Inspection (TNI) are not updated to indicate the new times.

• Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSBluetoothAlwaysUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).
  After you’ve corrected the issues, you can upload a new binary to App Store Connect.
  Best regards,
  The App Store Team

additional description would remove some ambiguity in reports

in glider: currently

• P - Proficiency
• U - Upgrade
• F - Famil
  additional breakdown required, will require discussion with Air Ops

in Tow Currently
TOW - Towing
P - Proficiency
U - Upgrade

P and U can cause confusion (as seen in the preliminary info that joé is reviewing.

This will need to be reviewed with Air Ops as there may be specific language and additional classifications required.

AirForce has a requirement that all glider and tow plane launches have Mission Acceptance and Launch Authorization.
Currently done on paper.

As a Pilot and Supervisor
we want to accept and authorize a launch
So that
... meet AirForce requirements (what are those req exactly?).... in case of an incident or accident

Q. What would make acceptance and authorization valid for the app stand point?

Q. What verification would need to be sent to AirForce if requested?

6.2.5 (631)
Thought the iCloud environment was not set correctly. After verification in the log on AppStore Connect, it seems it is ok. Now I can't access the crash log from the Organizer - not sure if more information is available than from the downloadable crash log from AppStore Connect site.
A new version has been published for testing.

We need to test ETS with the Public Beta release of iPadOS 13 to make sure any new features of iPadOS 13 won't interfere with ETS.

We need to especially test how ETS behaves with Slide Over (multitasking of apps) and how the application looks when in the new Dark mode. Chances are the text won't be readable in the iPad is in Dark mode AND the text is in Black.

Other upcoming task might be opened depending of the outcome of the current testing.

Test business logic.
Test UI
others

Create new Apple ID for NW and ATL iPads or reuse them.

• Limit of 10 device per AppleID
• Want to use the old app in parallele with new app?
• Sync of the data from old app to new app?

When logging a flight less than 3 minutes, the app rounds this time down to 0.0 minutes (when converting to decimal notation).

Easier to export and import data when confirming any changes needed.
How could maintaining flying center easier to manage for regions where they use any airport available in their region? PAC seems to have that issue, and find it cumbersome to have to enter every place they do flight familiarisation with cadets. Or did I misunderstood the issue raised? @markmacpherson @kirvanp

While the towplane is towing a glider, it can also be conducting Familiarization, Proficiency, Upgrade, PR, Wx, or Tow Course.
These need to be captured for stats

An error occurs when we try to share the database. Probably due to lack of schema in both development and production environments.

Error saving record <[...]> to server: Cannot create new type Region in production schema
Fatal error: Unexpectedly found nil while unwrapping an Optional value

Do we need to change? How complex is it? Have time?

The goal would be to have sqn list of cadets.
Put info back to Fortress when cadets have flown.

How is it possible that while generating the report for Brandon, we get information from ATL region? Ex.: In Towplane usage, TOW 1,2,3,and 4, and in Glider usage, GCLX and GBZG are ATL too.

The main goal is this split is to help maintenance to the application story boards. Working on a single big storyboard is not practical if we want to work collaboratively ad not source control friendly.
It will also help understand the interactions by reducing complexity of storyboards and storyboards will load more quickly.

From a central database.

Q.
Find out what reports reg AirOps uses from AMS (and other systems).

The submit feedback link: https://github.com/cadets-ca/ets/issues/new
The privacy policy link : TBD (inside the doc)

After some trial and following few courses, here are the steps we should follow:

Add french canadian as a language for the project (French, German, Japanese should be removed)
Replace string to be translated with NSLocalizedString(key, comment): This will be the most cumbersome task of all.
Must do that only for those that really need to be translated. Logs and debugging string should not be impacted. We may want to make logs bilingual though.
The comment argument to NSLocalizedString is very important. The translator may not have access to our developers in a timely fashion.
Interpolated string to be translated will need to be change to string format with positional parameters.
This:
let errorTitle = "Can't Sign Out (pilotToRemove.name)"
Must be change to this:

let errorTitle = String(format: NSLocalizedString("Can't Sign Out %1$@", comment: "Error message title when cannot signout pilot"), arguments: [pilotToRemove.name])
Export strings files
Not sure if it should be a single file or multiple files. Probably a single file is good enough for now.
Generate XLIFF files to be used by translation tools.
There is few tools that can read/write to XLIFF
Once translation result received, import the XLIFF file(s)
The biggest issues I see will be to test the application. Constraints may cause few headaches to fix, layout issues etc.

Asked to @kirvanp the file and version of Excel and OS.

Column to enter the flight number in for the course cadets – to keep track of the missions flown
Q. Only successful or both failed and successful?
Q. What about flight not in the syllabus?
Q. What is the purpose of tracking these numbers?