Received Bitcoins but "not available for spending"

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Sent some BTC to myself
2.They showed up and my desktop BTC client was showing the transaction as 
confirmed.
3.The phone is saying "waiting for confirmations"??? The blockchain has been 
synching...

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
I am running the latest version (auto-update) on HTC EVO 4G

Please provide any additional information below.

Original issue reported on code.google.com by dmeda...@gmail.com on 16 Jul 2011 at 10:44

[GoogleCodeExporter]

Can you post the transaction hash? You can look it up in block explorer.

If Bitcoin Wallet starts synching the block chain, could you look for the date 
in the notification area? Is it up to date?

Original comment by andreas....@gmail.com on 16 Jul 2011 at 11:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Due to some recent distrust [1] in my android phone I tried to send all my 
coins to my desktop and get the same message for the last almost 5 BTC. 
Receiving the amount in question happened definitely long ago. I can't identify 
the exact address that's causing the issue.

[1] https://bitcointalk.org/index.php?topic=53445.0

Original comment by LWanders...@gmail.com on 1 Dec 2011 at 10:39

[GoogleCodeExporter]

@LWandersleb did you try reloading the block chain? Go to About->Reset 
Blockchain and reset just the block chain. Let the phone set for a while and 
let it download the whole blockchain again.

Original comment by andreas....@gmail.com on 1 Dec 2011 at 11:08

[GoogleCodeExporter]

Issue 56 has been merged into this issue.

Original comment by andreas....@gmail.com on 29 Feb 2012 at 3:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have this problem, it appears that Bitcoin Wallet is requiring 100 
confirmations before it will allow me to spend the Bitcoins.

Original comment by hark...@gmail.com on 12 Sep 2012 at 8:20

[GoogleCodeExporter]

Further information on the probably-related problem I was having. 

I have .08 bitcoins in my "Bitcoin Wallet" wallet. They have been there for 
over a week.

I sent .02 BTC to Satoshi Dice. I lost. Okay. Now I have .06 BTC in my wallet. 
I try to send another .02 BTC to SatoshiDice. And it tells me I have .06 BTC 
waiting for confirmation. 

Looking at my wallet address on blockchain.info it says that from my wallet, 
.02 was sent to SatoshiDice and .06 was sent to my same wallet address I was 
sending from. 

So I conclude that Bitcoin Wallet is waiting on confirmations for Bitcoins that 
were sent from my wallet back to the same wallet. 

That isn't supposed to be how it works, is it? If I spend part of my Bitcoins I 
shouldn't have to wait to spend the remainder of them.

Original comment by barbarou...@gmail.com on 23 Sep 2012 at 6:49

[GoogleCodeExporter]

Part of this issue will be resolved in the next version. You will be able to 
spend your own unconfirmed change. Incoming payments will however still need at 
least one confirmation before you can spend.

If you want, you can help test this version:

http://code.google.com/p/bitcoin-wallet/downloads/list
(look for the 'spendpolicies' versions)

Original comment by andreas....@gmail.com on 16 Feb 2013 at 10:02

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

The spending unconfirmed change problem has been fixed in release 2.41.

Original comment by andreas....@gmail.com on 24 Feb 2013 at 11:23

[GoogleCodeExporter]

Same problem. Sent 0.75 BTC on Android Waller, spent 0.15 BTC on Humble Bundle, 
wallet started to show incorrect balance (1.72 BTC). I tryed to send BTC out, 
but app terminated with error. Now it's balance "frozen" with no confirmations 
and balance 0.60 BTC. Help pls

Original comment by ZulZ...@gmail.com on 1 Aug 2013 at 7:01

[GoogleCodeExporter]

I think the original problem has long been fixed, given that the original 
reporter did not reply and more. Thus, I'm closing this issue. If you encounter 
something like this again, please open a new ticket.

Original comment by andreas....@gmail.com on 21 Aug 2013 at 1:26

• Changed state: Fixed