cyclux
commented
7 years ago I found the source of the problem: https://github.com/iotaledger/wallet/pull/365 Devs, please review. Would be nice to see this fixed in the new release this week.
Open Shivanzh opened 7 years ago
cyclux
commented
7 years ago I found the source of the problem: https://github.com/iotaledger/wallet/pull/365 Devs, please review. Would be nice to see this fixed in the new release this week.
andrewg12345
commented
7 years ago i get this error with ANY amount. Lots of other people reporting the same on other support threads. Needs fixing. Thanks
cyclux
commented
7 years ago @andrewg12345 which OS?
andrewg12345
commented
7 years ago On Win10. Wallet 2.5.1. I transfered TO from bitfinex, but can not do a wallet to wallet transfer.
Shivanzh
commented
7 years ago I'm facing the problem in Windows 7...can't transfer from wallet to exchange.
andrewg12345
commented
7 years ago So the developer needs to fix this. Good place to start ? https://github.com/iotaledger/wallet/pull/365
cyclux
commented
7 years ago @Shivanzh @andrewg12345 could you please post your console output, while this error occurs. (View -> Web inspector -> console) Important is the part Server.transfer:
Shivanzh
commented
7 years ago The below I've got from the console when transferring 10 Miotas to an exchange.
Server.transfer: DURDGZNJZVMJWOVRFIAKPHAIOOSHNZIEKAOJJBYETBGZAVCKYFU9MCBGSHQ9MADVCPZEZCYUMKOFQSUHCLTEOMKMBC -> 10000000
ui.utils.js:305 UI.parseMessage
ui.utils.js:306 sending
ui.transfers.js:104 Error: Invalid transfers object
at Object.invalidTransfers (iota.js:3502)
at api.prepareTransfers (iota.js:1030)
at api.sendTransfer (iota.js:594)
at filterSpentAddresses.then.filtered (ui.transfers.js:101)
at
andrewg12345
commented
7 years ago So what does all this mean, and can it be fixed? I've got iota trapped in my wallet. Mean time watched BTC shoot up and couldnt do anything but watch.
Would be nice to get some sort of response, thanks.
cyclux
commented
7 years ago @andrewg12345 @Shivanzh I can understand your frustration. As there is no official statement from the devs regarding this issue I'll go ahead and post a compiled version which includes my proposed fix ( https://github.com/iotaledger/wallet/pull/365 ) . Unfortunatelly @Shivanzh's console output seems to indicate another issue not related to my fix, but you can try it anyway. I'm not an IOTA dev. Try out on your own responsibility: https://github.com/cyclux/wallet/releases/download/2.5.1.2/IOTA.Wallet.Setup.2.5.1_transfers_error_fix.exe
andrewg12345
commented
7 years ago What was your fix .. roughly
cyclux
commented
7 years ago You can see here: https://github.com/iotaledger/wallet/pull/365 If you have something like Server.transfer: OW9OJKLJFFUFLFWXL9GUXVVHLWTNTDCPOKWAIKPPJXUGVXEVZNEAZFTGUDDBTXB9GONOBPXFRITISBITXSVYTJJDRX -> 2019000.0000000002 in your console output while trying to transfer, this fix will most probably work. "Unfortunatelly" @Shivanzh post of console output does not show this odd output, so I guess there is also another cause for this error.
cyclux
commented
7 years ago BTW: @Shivanzh should post his complete console output, I think there may be important info in the remaining "exception text". at filterSpentAddresses.then.filtered (ui.transfers.js:101) at ...
andrewg12345
commented
7 years ago tried it, same error, did not work, what next?
UI.start: Initialization
(unknown) Light Wallet: localInterruptAttachingToTangle
ui.login.js:13 UI.showLoginScreen
ui.update.js:53 UI.createStateInterval: 60000, 0
ui.update.js:54 Sat Oct 14 2017 15:28:33 GMT+0100 (GMT Summer Time)
ui.app.js:3 UI.inAppInitialize
ui.app.js:15 UI.startStatusBarTracking
ui.update.js:57 In update interval: false, false, false
ui.update.js:58 Sat Oct 14 2017 15:28:33 GMT+0100 (GMT Summer Time)
ui.update.js:63 Execute interval
ui.update.js:68 Got node info
ui.update.js:69 Sat Oct 14 2017 15:28:33 GMT+0100 (GMT Summer Time)
ui.update.js:53 UI.createStateInterval: 60000, 60000
ui.update.js:54 Sat Oct 14 2017 15:28:33 GMT+0100 (GMT Summer Time)
ui.update.js:119 We have an initial connection.
ui.update.js:53 UI.createStateInterval: 60000, 60000
ui.update.js:54 Sat Oct 14 2017 15:28:33 GMT+0100 (GMT Summer Time)
ui.login.js:283 UI.updateLoginForm: Fade in
ui.utils.js:305 UI.parseMessage
ui.utils.js:306 logging_in
loading-btn.js:199 $.fn.loadingReset: login
ui.utils.js:305 UI.parseMessage
ui.utils.js:306 login
ui.login.js:154 UI.showAppScreen
ui.update.js:53 UI.createStateInterval: 60000, 60000
ui.update.js:54 Sat Oct 14 2017 15:28:51 GMT+0100 (GMT Summer Time)
ui.update.js:57 In update interval: false, false, false
ui.update.js:58 Sat Oct 14 2017 15:29:51 GMT+0100 (GMT Summer Time)
ui.update.js:63 Execute interval
ui.update.js:68 Got node info
ui.update.js:69 Sat Oct 14 2017 15:29:51 GMT+0100 (GMT Summer Time)
ui.update.js:73 Got account data
ui.update.js:74 Sat Oct 14 2017 15:30:00 GMT+0100 (GMT Summer Time)
ui.update.js:53 UI.createStateInterval: 60000, 60000
ui.update.js:54 Sat Oct 14 2017 15:30:00 GMT+0100 (GMT Summer Time)
ui.transfers.js:8 UI.handleTransfers: Click
ui.transfers.js:61 Server.transfer: ADRESSNUMBXXXXX....XXXXXXX -> 1000000
ui.utils.js:305 UI.parseMessage
ui.utils.js:306 sending
ui.transfers.js:104 Error: Invalid transfers object
at Object.invalidTransfers (iota.js:3502)
at api.prepareTransfers (iota.js:1030)
at api.sendTransfer (iota.js:594)
at filterSpentAddresses.then.filtered (ui.transfers.js:101)
at
andrewg12345
commented
7 years ago I did transfer a small amount via the android app, [myWallet1] to [myWallet2].
created a recieve address in windows[myWallet2] , copied that address in to the android app [myWallet1], then sent to [myWallet2] ... eventually. just going to try android again the reverse way round [myWallet2] to [myWallet1].
Is it a fire wall issue in windows, I just don't get why it works for some people but not others
Please look into the issue as whenever I do a transaction it comes as Invalid Transfers Object. Tried many times as I can. Thanks,