kolap
Sr. Member
 Offline
Activity: 301
Merit: 250
In Crypto We Trust
|
 |
April 17, 2020, 05:22:53 AM |
|
|
|
|
|
|
|
|
|
|
|
|
In order to achieve higher forum ranks, you need both activity points and merit points.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
bangomatic
Legendary
Offline
Activity: 1246
Merit: 1000
ARK Team likes to ban and delete posts in reddit.
|
|
April 29, 2020, 08:12:57 PM |
|
Banned from Ark slack, now shadow banned from /r/ArkEcosystem/
These Ark snobs arent very hospitable unless you drink the kool-aide. be forewarned.
|
|
|
|
|
|
Totscha
|
|
April 30, 2020, 07:09:52 AM |
|
All this development and bright new shiny features are great. What's not? The desktop wallet client. It works fine for you? Well good for you.
I however get the "transfer transaction could not be created" from time to time. With no hint or explanation into the actual cause. And then it suddenly just works. This code should be much much more robust, or you could at least give us more detailed error descriptions. Thank you!
|
|
|
|
|
|
BoldNinja
|
|
April 30, 2020, 06:03:39 PM |
|
All this development and bright new shiny features are great. What's not? The desktop wallet client. It works fine for you? Well good for you.
I however get the "transfer transaction could not be created" from time to time. With no hint or explanation into the actual cause. And then it suddenly just works. This code should be much much more robust, or you could at least give us more detailed error descriptions. Thank you!
Hey, Totscha can you update Desktop Wallet to latest release and see if that resolves your problems ( https://ark.io/wallet v2.9.1 at the time of this post) and make sure that you are connected to the healthy peer (cloud icon) when you start to interact with your wallet. You can also join our Slack ( https://ark.io/slack) and post your error in our #help channel there. One of our developers will be able to help you out or help resolve the bug or alternatively, you can also open Github issue: https://github.com/ArkEcosystem/desktop-wallet/issues/new. |
|
|
|
|
GreXX
|
|
April 30, 2020, 06:11:11 PM |
|
All this development and bright new shiny features are great. What's not? The desktop wallet client. It works fine for you? Well good for you.
I however get the "transfer transaction could not be created" from time to time. With no hint or explanation into the actual cause. And then it suddenly just works. This code should be much much more robust, or you could at least give us more detailed error descriptions. Thank you!
The ARK Wallet doesn't force you to connect to a centralized peer like most wallets. Due to this, sometimes you can end up with a connection to a bad or outdated peer. Usually in that situation, updating the peer with the cloud icon will solve it. You can also select a dedicated peer from the community and set a custom peer with the cloud icon to help avoid it. |
|
|
|
|
|
kolap
Sr. Member
Offline
Activity: 301
Merit: 250
In Crypto We Trust
|
|
May 01, 2020, 05:24:42 AM |
|
Banned from Ark slack, now shadow banned from /r/ArkEcosystem/
These Ark snobs arent very hospitable unless you drink the kool-aide. be forewarned.
You got banned for a reason, you need to chill! You can always post here, Ark team can't ban you here. |
|
|
|
|
Totscha
|
|
May 01, 2020, 07:20:08 AM |
|
All this development and bright new shiny features are great. What's not? The desktop wallet client. It works fine for you? Well good for you.
I however get the "transfer transaction could not be created" from time to time. With no hint or explanation into the actual cause. And then it suddenly just works. This code should be much much more robust, or you could at least give us more detailed error descriptions. Thank you!
Hey, Totscha can you update Desktop Wallet to latest release and see if that resolves your problems ( https://ark.io/wallet v2.9.1 at the time of this post) and make sure that you are connected to the healthy peer (cloud icon) when you start to interact with your wallet. You can also join our Slack ( https://ark.io/slack) and post your error in our #help channel there. One of our developers will be able to help you out or help resolve the bug or alternatively, you can also open Github issue: https://github.com/ArkEcosystem/desktop-wallet/issues/new. Hi. I do have the latest client (2.9.1) and i did refresh the peer a bunch of times like it was suggested by the kind people of the interwebs. I guess I just got lucky after 10 minutes and found a good one.  I have two problems with this 'feature': 1 - In case of an error I have to: - close the Send dialog - go to the cloud icon to roll the dice on a new peer - open a new Send dialog and enter all the data again - cross my fingers and send 2 - When I connect to a new peer, all I get is the latency. There is no way to check if the peer is healthy. Am I the only one who finds this UX design problematic? |
|
|
|
|
|
GreXX
|
|
May 01, 2020, 02:56:07 PM |
|
All this development and bright new shiny features are great. What's not? The desktop wallet client. It works fine for you? Well good for you.
I however get the "transfer transaction could not be created" from time to time. With no hint or explanation into the actual cause. And then it suddenly just works. This code should be much much more robust, or you could at least give us more detailed error descriptions. Thank you!
Hey, Totscha can you update Desktop Wallet to latest release and see if that resolves your problems ( https://ark.io/wallet v2.9.1 at the time of this post) and make sure that you are connected to the healthy peer (cloud icon) when you start to interact with your wallet. You can also join our Slack ( https://ark.io/slack) and post your error in our #help channel there. One of our developers will be able to help you out or help resolve the bug or alternatively, you can also open Github issue: https://github.com/ArkEcosystem/desktop-wallet/issues/new. Hi. I do have the latest client (2.9.1) and i did refresh the peer a bunch of times like it was suggested by the kind people of the interwebs. I guess I just got lucky after 10 minutes and found a good one. I have two problems with this 'feature': 1 - In case of an error I have to: - close the Send dialog - go to the cloud icon to roll the dice on a new peer - open a new Send dialog and enter all the data again - cross my fingers and send 2 - When I connect to a new peer, all I get is the latency. There is no way to check if the peer is healthy. Am I the only one who finds this UX design problematic? If you are having that big of a problem I think it's abnormal and you may be running into some other kind of additional issue. I've only had a bad peer maybe 2-3 times in 2 years. |
|
|
|
TravisARK
Jr. Member
Offline
Activity: 66
Merit: 3
|
|
May 01, 2020, 03:01:44 PM |
|
All this development and bright new shiny features are great. What's not? The desktop wallet client. It works fine for you? Well good for you.
I however get the "transfer transaction could not be created" from time to time. With no hint or explanation into the actual cause. And then it suddenly just works. This code should be much much more robust, or you could at least give us more detailed error descriptions. Thank you!
Hey, Totscha can you update Desktop Wallet to latest release and see if that resolves your problems ( https://ark.io/wallet v2.9.1 at the time of this post) and make sure that you are connected to the healthy peer (cloud icon) when you start to interact with your wallet. You can also join our Slack ( https://ark.io/slack) and post your error in our #help channel there. One of our developers will be able to help you out or help resolve the bug or alternatively, you can also open Github issue: https://github.com/ArkEcosystem/desktop-wallet/issues/new. Hi. I do have the latest client (2.9.1) and i did refresh the peer a bunch of times like it was suggested by the kind people of the interwebs. I guess I just got lucky after 10 minutes and found a good one. I have two problems with this 'feature': 1 - In case of an error I have to: - close the Send dialog - go to the cloud icon to roll the dice on a new peer - open a new Send dialog and enter all the data again - cross my fingers and send 2 - When I connect to a new peer, all I get is the latency. There is no way to check if the peer is healthy. Am I the only one who finds this UX design problematic? It takes seconds not 10 minutes. If you're shown a latency number and it's green, there is nothing wrong with the wallet. That is not rolling the dice, it is loading a good peer. Also you might want to click force reload in the top menu, not sure what you might have running and this will start fresh. Anything after that is more than likely an internet connection issue or firewall problem. Could be a wifi issue if you are using wifi as well. The option to refresh your peer should not be needed for most, but sometimes during a network upgrade some peers go down while updating, so your wallet may have used this peer earlier and saw no issue, so a quick refresh just connects to a green peer and your good. Seconds, not minutes. |
|
|
|
|
|
|
|
|
|
Totscha
|
|
May 04, 2020, 05:36:15 AM |
|
All this development and bright new shiny features are great. What's not? The desktop wallet client. It works fine for you? Well good for you.
I however get the "transfer transaction could not be created" from time to time. With no hint or explanation into the actual cause. And then it suddenly just works. This code should be much much more robust, or you could at least give us more detailed error descriptions. Thank you!
Hey, Totscha can you update Desktop Wallet to latest release and see if that resolves your problems ( https://ark.io/wallet v2.9.1 at the time of this post) and make sure that you are connected to the healthy peer (cloud icon) when you start to interact with your wallet. You can also join our Slack ( https://ark.io/slack) and post your error in our #help channel there. One of our developers will be able to help you out or help resolve the bug or alternatively, you can also open Github issue: https://github.com/ArkEcosystem/desktop-wallet/issues/new. Hi. I do have the latest client (2.9.1) and i did refresh the peer a bunch of times like it was suggested by the kind people of the interwebs. I guess I just got lucky after 10 minutes and found a good one. I have two problems with this 'feature': 1 - In case of an error I have to: - close the Send dialog - go to the cloud icon to roll the dice on a new peer - open a new Send dialog and enter all the data again - cross my fingers and send 2 - When I connect to a new peer, all I get is the latency. There is no way to check if the peer is healthy. Am I the only one who finds this UX design problematic? It takes seconds not 10 minutes. If you're shown a latency number and it's green, there is nothing wrong with the wallet. That is not rolling the dice, it is loading a good peer. Also you might want to click force reload in the top menu, not sure what you might have running and this will start fresh. Anything after that is more than likely an internet connection issue or firewall problem. Could be a wifi issue if you are using wifi as well. The option to refresh your peer should not be needed for most, but sometimes during a network upgrade some peers go down while updating, so your wallet may have used this peer earlier and saw no issue, so a quick refresh just connects to a green peer and your good. Seconds, not minutes. I was on WiFi, and the latencies were not very good. Mostly > 100ms, but every now and then i found a good peer with <100 ms latency. I did exactly what you said. I refreshed the peer, this does take seconds, yes. But the whole process (open send dialog, enter data, try sending, fail, scratch head, disable/check firewall, go back and refresh the peer) takes 30-60s. Take that and multiply by 10-15 attempts and you get 10 minutes & annoyed. I most definitely got annoyed... What I think happened was: - i was connected to a peer that was borderline OK - when I tried sending, the attempt timed out, since I now had a higher latency to the peer So this happened 10-15 times. Guess I'm just that unlucky... Either that or you have a lower timeout value for sending commands, than you have for peer health check. |
|
|
|
|
|
|
|
