Author

Topic: Weird problem with Atomic wallet. Can't send money from Desktop (Read 239 times)

legendary
Activity: 2324
Merit: 1258
Heisenberg
It happened with me once. I was not able to send  a particular cryptocurrency and was not able to view those which I had deposited the same day. When I checked with support the told me to update it to the latest version. After updating it was working for me. Check the version of your wallet.
If you carefully check the messages he sent to the support, it's clear that he had his wallet updated but the problem was still persistent.
hero member
Activity: 2156
Merit: 803
Top Crypto Casino
It happened with me once. I was not able to send  a particular cryptocurrency and was not able to view those which I had deposited the same day. When I checked with support the told me to update it to the latest version. After updating it was working for me. Check the version of your wallet.
HCP
legendary
Activity: 2086
Merit: 4361
...
Can't help with the Atomic wallet issue, but just wanted to point out that if you're concerned with privacy (which I think you might be given the redacting in your screenshot)... it would appear that you left your (real?) name unredacted in the email correspondence Wink Shocked
hero member
Activity: 1092
Merit: 582
Which version you are using and what is your OS? Can you send me the log file?
I'm not sure if you have the log file now as you already uninstalled the software.

Just installed the wallet on my system to replicate the issue.
hero member
Activity: 1778
Merit: 764
www.V.systems
It would be really difficult to know what is the problem without any debug logs.

You might want to try it again and then take a look at the error.logs that's available since 0.1.29 Beta. Make a test transaction again and then save the logs via Settings.

Unfortunately, I got a standard response of 'We're looking into it" on the TG chat. I had provided them with the debug logs in a TG chat with one of the admins. I can't remember exactly who.


That's a standard response because they don't know what's the real cause of the issue. Submitting debug logs for the developer might help them to speed up fixing the problem.


Yeah, TG chat admins are not really tech people that are working on the project, they're just there to act as a communicating bridge between the users and the tech guys.




For now, I have Atomic Wallet uninstalled on my PC.

This issue might even force me to switch away from Atomic wallet on my android if left unfixed.
legendary
Activity: 2170
Merit: 1789
A quick search of 'please try again later' found many similar problems that other users had with the wallet so it doesn't seem like it's anything new.
The admins usually suggest, update to the newest version, restore your wallet and/or use VPN.   

That's a standard response because they don't know what's the real cause of the issue. Submitting debug logs for the developer might help them to speed up fixing the problem.

I wonder why they would ignore such a bug. I checked on their github profile and activity in most of the repositories last ended in May which explains why they haven't worked on the issue.

They forked a lot of repos. But their last update was for their website 25 days ago. It's weird to assume they don't have time to work on bugs, as their previous release was in August.
copper member
Activity: 2114
Merit: 1794
Top Crypto Casino
I wonder why they would ignore such a bug. I checked on their github profile and activity in most of the repositories last ended in May which explains why they haven't worked on the issue.

Someone even open an issue regarding the same problem back in June but it has never been worked upon or closed

https://github.com/Atomicwallet/atomicwallet.github.io/issues
legendary
Activity: 2730
Merit: 7065
Try explaining your problem in their Telegram chat > https://t.me/atomicwalletchat
Maybe one of their admins or a normal user had the same issue and they can help you fix it. Be careful who you talk to as scammers are very likely to contact you as soon as you join the group.

A quick search of 'please try again later' found many similar problems that other users had with the wallet so it doesn't seem like it's anything new.
The admins usually suggest, update to the newest version, restore your wallet and/or use VPN.   
legendary
Activity: 2170
Merit: 1789
It would be really difficult to know what is the problem without any debug logs.

You might want to try it again and then take a look at the error.logs that's available since 0.1.29 Beta. Make a test transaction again and then save the logs via Settings.
hero member
Activity: 1778
Merit: 764
www.V.systems
Okay so I faced this weird situation a few days ago with one of the tokens and now again with LTC.

It seems I can receive my coins perfectly fine but I cannot send anything.

The only error code I got was the anon id - which I could use to contact the support with, other than that I got this annoying little warning.



Cant' send XXX now, please try again later

Contact Atomic Support about this transaction



I hid my token cuz I don't want anyone to know which shitcoin I am talking about here, lest it be taken for some sort of endorsement or publicity stunt.


--

When I contact their support, all I get is a generic response. Which makes things more unbearable.




So as you can see, I resolved my situation by trying to send funds ONLY through my mobile. Which is weird.

Since then, I have tried doing this from a secured location in a different location / network than from my usual computer. I tried it from my Laptop even. All with the same result.

But, strangely enough the mobile wallet, regardless of which network I am on, always works.

I tried this again with LTC recently, same situation while mobile worked flawlessly.

Between these 2 events (first my token and now LTC) there has been a time span of about 3 months. And they have still left it unresolved.

Which makes me think that this might be a situation at my end alone because surely there are so many users at Atomic Wallet - not all of them could be having the same problem and the support leave this bug unfixed for so long..


So does anyone know what's going on?
Jump to: