Realm migrations setup improvements

[laumair]

Description

Fixes #1162

Type of change

• Enhancement (a non-breaking change which adds functionality)

How Has This Been Tested?

• Manually tested
• Unit tests update

Checklist:

• My code follows the style guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• For changes to mobile that include native code (including React Native modules): I have verified that both iOS and Android successfully build in both Debug and Release modes
• For changes to shared: If applicable, I have verified that my changes are implemented correctly in desktop and mobile

[rajivshah3]

Not sure if this is intentional or a bug:

If I start with a fresh simulator, run Trinity on the develop branch, and complete the onboarding, the Documents directory looks like this (run open $(xcrun simctl get_app_container booted com.iota.trinity data)/Documents to open it):

Then, I checkout feat/realm-migrations and run the app again. When I reach the login screen, it looks like this:

If I don't log in, but simply run the app again, it looks like trinity-1 is recreated:

[laumair]

If I don't log in, but simply run the app again, it looks like trinity-1 is recreated:

On which branch are you facing this?

[laumair]

This PR changes the storage path for realm but it should also remove the realm files on old paths.

[rajivshah3]

On which branch are you facing this?

I think this one

[laumair]

@rajivshah3 I'll investigate.

[cvarley100]

@laumair Perhaps we should add some documentation on how to write a migration, and which variables need updating?

[rajivshah3]

Looks good. Could you reset the changes to the shrinkwrap? It looks like there weren't any changes to desktop/package.json so I don't think changes to the shrinkwrap are necessary

[laumair]

@rajivshah3

Looks good. Could you reset the changes to the shrinkwrap? It looks like there weren't any changes to desktop/package.json so I don't think changes to the shrinkwrap are necessary

Done

[laumair]

@cvarley100

Perhaps we should add some documentation on how to write a migration, and which variables need updating?

Good idea. I've created an issue. Will do a separate PR for this.