Locating wallet on Mac ios?

Tech Support
#22

also have the same problem.
Does someone know how can i restore the local storage library in mac???

#23

Anyone found anyway to solve this yet? - It would be good to tell anyone who is buying NEM for the first time not to use Safari!! This should be highlighted in bold red to stop another unlucky person stumbling on the same problem.

For those that have been caught in this trouble, is there anyway to get our funds back without the private key file?

#24

@Quantum_Mechanics will this “bug” be fixed in future versions of the NanoWallet (re. Safari/MacOS - no .WLT download)?

For those who lost their browser’s local storage (which contains the wallet info - until you purges it intentionally or unintentionally): You may try to use http://www.easeus.com/mac/mac-undelete-free/ or https://www.stellarinfo.com/data-recovery-mac.php
(or check http://www.techrepublic.com/article/3-data-recovery-applications-for-os-x/ )

However, don’t change too much on your harddrive because every write operation may sooner or later overwrite the freed-up space where the “deleted” contents reside.
We need to recover the files from ~/Library/Safari/LocalStorage/ or similar folders.

Try to keep Safari OFF, so it doesn’t mess with the “new” Local Storage files…!
Good luck. We all learn our lessons one way or the other.

Remember: Back up your private keys. If needed, do it manually - it’s easy.

1 Like
#25

Hi @r3n3,

I have looked and did not found any alternatives for older versions of Safari.

I know exactly what is the problem: https://github.com/NemProject/NanoWallet/blob/master/src/app/modules/signup/signup.controller.js#L103

Support for the download attribute is only since Safari 10.1: https://caniuse.com/#feat=download

Users must use the latest version of the browser as mentionned here: Nano Wallet Beta 2.0.14 - Mandatory update - Bug bounty paid in XEM

I want to add a lock if version below 10.1 but all our current users with Safari will have to update their browser to use the app again

#26

Thanks for the good explanation. @Quantum_Mechanics - This helps to understand the cause of the issue.