resolve initialization failure when encryption directory exists

[Miduo666]

Pull Request Details

What issue does this PR address

• [Description]

Associated Issue

• This PR relates to issue Bug: init_helper.dart fails if encryption directory already exists on the server #604

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

Complete the check-list below to ensure your branch is ready for PR.

• Screenshots included in linked issue #
• Changes adhere to the style and coding guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Any dependent changes have been merged and published in downstream modules
• The update contains no confidential information
• The update has no duplicated content
• No lint check errors are related to these changes (make prep or flutter analyze lib)
• Integration test dart test output or screenshot included in issue #
• I tested the PR on these devices:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
  • Web
• I have identified reviewers
• The PR has been approved by reviewers

Finalising

Once PR discussion is complete and reviewers have approved:

• Merge dev into the this branch
• Resolve any conflicts
• Add a one line summary into the CHANGELOG.md
• Push to the git repository and review
• Merge the PR into dev

[gjwgit]

Needs to be tested to ensure all continue to work as expected. Generally seems to be working. Good to have a check from @tonypioneer and @cdawei.

• geopod
• notepod
• healthpod
• movistar
• riopod
• riodash
• innerpod - it is starting up as if I had not already initialised the app? Now back on dev it is doing the same, though before trying this PR it was loading just fine.

[Miduo666]

Needs to be widely tested across multiple apps to ensure all continue to work as expected.

• geopod
• innerpod - it is starting up as if I had not already initialised the app? Now back on dev it is doing the same, though before trying this PR it was loading just fine.

Hi Graham,

Thank you for the detailed feedback.

I have tested the PR on notepod as well, and it is working correctly without triggering a re-initialization.

A typical test case is to modify app.dart as shown in the attached screenshot. You can try adding a new directory to the customFolderPathList and verify if the app handles the initialization as expected without regressing existing setups.

I will continue to investigate why innerpod specifically is failing to recognize its initialized state.

[gjwgit]

THanks. It may be that innerpod is an older app and not correctly using the new functionality.