BIP39 Keystore not accessible from keystore parameter path

[pandeyshivang]

let userDir = NSSearchPathForDirectoriesInDomains(.documentDirectory, .userDomainMask, true)[0]

     let ks = KeystoreManager.managerForPath(userDir + "/keystore")
    self.keystoreManager = ks
    web3rinky?.addKeystoreManager(ks)
  
    address = ks?.addresses?[0].address

crash when getting address from keystoremanager.
Error in latest version in CryptoSwift?

[shamatar]

Did you previously create a BIP32 keystore and save it to that directory? Just in case

[pandeyshivang]

yeah i want to create hd wallet
let mnemonic = try! BIP39.generateMnemonics(bitsOfEntropy: 256)!
let keystore = try! BIP32Keystore(mnemonics: mnemonic, password: password, mnemonicsPassword: "")
let keydata = try JSONEncoder().encode(ks?.keystoreParams)
FileManager.default.createFile(atPath: userDir + "/keystore"+"/key.json", contents: keydata, attributes: nil)

[pandeyshivang]

@shamatar I have just solved it...

 let data = try Data(contentsOf: URL(fileURLWithPath: path), options: .mappedIfSafe)
  let jsonResult = try JSONSerialization.jsonObject(with: data, options: .mutableLeaves)
  let bip32keystore = BIP32Keystore.init(data)

@shamatar thanks giving me this fantastic lib.

[shamatar]

Oh, I didn’t understand a question. Yes, you can either create a keystore from phrase and lib will save a necessary information to JSON that you can write to disk, or you can supply either Json string or data to recreate it from saved copy.

[shamatar]

Please keep in mind that BIP 32 keystore JSON format is not standartized, so files are not compatible with other libs. For BIP32KEYSTORE keystore everyone just backups a seed phrase, it’s enough. Be sure to allow your users to backup a seed phrase after creation and destroy it after

[pandeyshivang]

@shamatar but get connectionError in Send ether.
responseSerializationFailed(Alamofire.AFError.ResponseSerializationFailureReason.inputDataNilOrZeroLength)
2018-04-20 17:06:54.178363+0530 Ethereum-ERC20-Tokens-Wallet[10263:227250]

[shamatar]

Please check your internet connection (if using Infura) or connection to the local node. If you are using Geth be sure to have —rpc flag and —rpccors if necessary

…

________________________________ From: Shivang Pandey <notifications@github.com> Sent: Friday, April 20, 2018 2:39:50 PM To: BANKEX/web3swift Cc: Alexander; Mention Subject: Re: [BANKEX/web3swift] BIP39 Keystore not accessible from keystore parameter path (#68) @shamatar<https://github.com/shamatar> but connectionError in Send ether. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#68 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGKv9-nMX08amXAl0eB0Bh9-LSZXEsJFks5tqckFgaJpZM4TdJo7>.

[pandeyshivang]

my internet is working fine and i am using infura and whenever i send i got invalid address.

[shamatar]

Would you try a latest commit in master?

…

________________________________ From: Shivang Pandey <notifications@github.com> Sent: Friday, April 20, 2018 4:59:34 PM To: BANKEX/web3swift Cc: Alexander; Mention Subject: Re: [BANKEX/web3swift] BIP39 Keystore not accessible from keystore parameter path (#68) my internet is working fine and i am using infura and whenever i send i got invalid address. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#68 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGKv91l8470lmDWbiGVZp5x2cBip_aLnks5tqenGgaJpZM4TdJo7>.

[pandeyshivang]

@shamatar yeah i installed latest version of web3swift. my code is send ether in bip32keystore...

let contract = self.web3rinky?.contract(Web3.Utils.coldWalletABI, at: toaddress) var options = Web3Options.defaultOptions() options.value = Web3.Utils.parseToBigUInt(amount, units: .eth) options.from = self.bip32keystore?.addresses?.first let intermediate = contract?.method("fallback", options: options) let result = intermediate?.send(password: pass)

[pandeyshivang]

@shamatar Yeah it works in 0.5.6 version...