Skip to content
This repository has been archived by the owner on Sep 5, 2019. It is now read-only.

Last key redeemed is not removed from listing #8

Open
r6d2 opened this issue Dec 17, 2016 · 4 comments
Open

Last key redeemed is not removed from listing #8

r6d2 opened this issue Dec 17, 2016 · 4 comments

Comments

@r6d2
Copy link

r6d2 commented Dec 17, 2016

I don't know if this is a new behavior to 0.5 or not. I had not noticed it before anyway, but when a list is pasted to redeem, and all keys get redeemed, the last key remains on the window no matter the result of the previous operation.

@KlappPc
Copy link

KlappPc commented Jan 17, 2017

I can further specify, that if only the last key should be removed, it stays and the second last key, gets removed (even if that one should stay).
But I currently don't get, why thats happening ;->

@SoulReaver
Copy link

SoulReaver commented Jan 23, 2017

I had 4 keys from recent massive giveaways but decided to wait for something bigger with debugging in VS and simply tried using the keys through your app and I had reproduced this bug (it can be actually related to my issue #10)

3 bots, 3 times the same input (I have changed actual keys to something more readable :) ):

HEAD-SHOT-KEY1 <- I did not know it was already used ... giveaways with used up keys :P
WHY-SO-EVIL1
HEAD-SHOT-KEY2
WHY-SO-EVIL2

<bot1> Key: HEAD-SHOT-KEY1 | Status: DuplicatedKey | Items: [109138, Head Shot]
<bot1> Key: WHY-SO-EVIL1 | Status: OK | Items: [54017, Why So Evil + Why So Evil 2: Dystopia + Brilliant Bob]
<bot1> Key: HEAD-SHOT-KEY2 | Status: OK | Items: [109138, Head Shot]
<bot1> Key: WHY-SO-EVIL2 | Status: AlreadyOwned | Items: [62412, Why So Evil 2: Dystopia + Why So Evil + Brilliant Bob]

in text box remains:
HEAD-SHOT-KEY2 <- this one shouldn't be here
WHY-SO-EVIL2


<bot2> Key: HEAD-SHOT-KEY1 | Status: DuplicatedKey | Items: [109138, Head Shot]
<bot2> Key: WHY-SO-EVIL1 | Status: AlreadyOwned | Items: [54017, Why So Evil + Why So Evil 2: Dystopia + Brilliant Bob]
<bot2> Key: HEAD-SHOT-KEY2 | Status: DuplicatedKey | Items: [109138, Head Shot]
<bot2> Key: WHY-SO-EVIL2 | Status: AlreadyOwned | Items: [62412, Why So Evil 2: Dystopia + Why So Evil + Brilliant Bob]

remains
HEAD-SHOT-KEY2 <- again, why it stays here?
WHY-SO-EVIL2


<bot3> Key: HEAD-SHOT-KEY1 | Status: DuplicatedKey | Items: [109138, Head Shot]
<bot3> Key: WHY-SO-EVIL1 | Status: DuplicatedKey | Items: [54017, Why So Evil + Why So Evil 2: Dystopia + Brilliant Bob]
<bot3> Key: HEAD-SHOT-KEY2 | Status: DuplicatedKey | Items: [109138, Head Shot]
<bot3> Key: WHY-SO-EVIL2 | Status: OK | Items: [62412, Why So Evil 2: Dystopia + Why So Evil + Brilliant Bob]

remains
WHY-SO-EVIL2 <- now this one ...

@aresda
Copy link

aresda commented May 10, 2017

Same problem after update ASF.
Status message was changed.
Like this. [ Status: OK/NoDetail ] , [ Status: Fail/AlreadyPurchased ]

@KlappPc
Copy link

KlappPc commented May 10, 2017

@aresda already fixed in #13 but not yet merged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants