 Posted: Tue Jan 24, 2012 6:24 pm Post subject: |
|
| Amanico,
Thank you for reporting this. I found the reason why the final price update failed. It's hard to explain in a few sentences, but it was located in the mobile version of Gixen that you used. I don't expect this will happen again for this reason. |
|
| Posted: Tue Jan 24, 2012 4:25 pm Post subject: |
|
| Just happened to me too for auction 180802152883.
My snipe went in 7 seconds before end and the winner outsniped me 1 second before end (!) Gixen incorrectlyt says I won. Thanks. |
|
| Posted: Mon Jan 23, 2012 7:56 am Post subject: |
|
| You are all correct, this does happen from time to time, that Gixen fails to detect when a user is outsniped, and that this may result in group bids being incorrectly canceled. This, however, is relatively rare, so it hasn't been a big problem in practice. I'll take a look if it can be prevented nevertheless. | |
| Posted: Mon Jan 23, 2012 7:34 am Post subject: Incorrect Staus on Won/Lost Item |
|
| I placed a snipe for GBP 3.58 for the following item; 150733937022, and was outbid. Fair enough, it wasn't all that important.
However, I noticed afterwards that despite being outbid on ebay, the Gixen screen (and the confirmation email Gixen sends me) both seem to think that I was the high bidder. It is currently reporting that the "current" price is GBP 1.77, and the the "status" as "won" - yet both are wrong. I have known the final sale price to be out-of-date before, but I've never noticed Gixen get the won/lost aspect wrong before. While the incorrect status is not a problem in this instance, I do use both the "group" and "contingency group" bidding mechanisms, and I suspect that if this snipe were a member of one of those, Gixen would have acted based on incorrect information on the rest of the grouped bids, so I thought this was best reported just in case. |
|