The reason for this is that an account reset will create a new account key (QR code) for your account.
#MSECURE SYNC PASSWORD#
Was this a simple password change within mSecure 5 or did you go through an account reset? After an account reset, we ask that you remove the iCloud or Dropbox sync file if you were previously using one of those sync features. Perhaps you are using a mix of mSecure 4 and mSecure 5 here? Our system shows that you changed your account password on 06-10-2019 01:40:06 UTC. The error message of "the local account doesn't match remote account key" is an mSecure 5 message though. mSecure 5 will never prompt you for such a password because it simply does not exist in mSecure 5. If you are being prompted for a cloud sync password, you are not using mSecure 5. Those are the main reasons why mSecure 5 does not sync with the previous versions of mSecure. Note that mSecure 5 uses a completely different encryption algorithm, different data structure, and even different Dropbox data location. mSecure 5 syncs perfectly with mSecure 5 on all devices. I do not know what you mean about losing a record since there's no way for mSecure 5 to sync with the previous Dropbox information.
However, you'd want use mSecure 5 afterwards if you want to keep things up to date in mSecure 5 or have to regularly create and restore from backups if you are going to continue using mSecure 4: You can however create a backup of mSecure 4 and restore from that backup in mSecure 5 to have your mSecure 5 information be up to date. mSecure 5 will only sync with mSecure 5 so it makes sense that something you've done in mSecure 4.5.4 isn't syncing over to the latest version. mSecure 5 does not and will not sync with the previous versions of mSecure. I do not know what you mean about low info display density though. mSecure 5 on all platforms (Android, iOS, Mac, and Windows) includes Dropbox syncing support. What on earth were/are the developers thinking? Ignoring the sync issue I can't see the point of adding steps to the process of copying information and again the UI design changes just reduce information density. The desktop versions are functionally and visually inferior to what came before and it now looks as if the same is true of the iOS versions. The responses from EM above are not inspiring and if, as he suggests, v5 cannot be used in conjunction with previous versions then that's the final nail in the coffin for me and v5. 'Losing' a record has never happened to me before when using previous versions and has shaken my faith in a previously totally reliable product. Unlinking and re-linking to Dropbox has not worked (i.e. Turning off automatic sync and attempting to sync manually via the pull-down method is ineffective. The record was created on another iOS device using v4.5.4 and has evidently synced into Dropbox OK as it's present on all other instances apart from v5.6.0 on my phone.
The first sign of this was failing to find a record in v5 that I then found successfully in v4.5.4.
#MSECURE SYNC MAC#
I've recently been trying to use v5.6.0 on iOS (having quickly abandoned it on Mac for the usual reasons including low info display density and dropping Dropbox sync) and although after having initially got it to sync with Dropbox it now refuses to do so. I'm a longtime user of mSecure on iOS, Mac and Windows.
0 kommentar(er)
