Sunsetting Incognito   

[Solved] -6005 error

#25

Any update on this? Any tips or tricks would be greatly appreciated!

1 Like
#26

How much interest do we earn on funds that are locked up with this bug :wink: At least mine is in PRV so with the recent increase in price it is in my favor :joy:

Security audit is a MUST!
Transaction timed out as usual, please help me withdraw my money
#27

You can reimport your account to fix the issue. The issue will be fixed on this thursday.

3 Likes
#28

I just reimported my account to a different phone. I then tried to send to an outside wallet and got the same exact error. Your post claims this would have fixed the issue. After buying, selling, and trading over 4000 PRV in the past couple months I am somewhat familiar with the app. Did you mean to say I can “try” to import my account but it still won’t be fixed until Thursday? @Ducky @Peter

#29

To confirm your comment @tien about a reimport fixing the issue, I decided it would be more useful to see if this would resolve my issue, rather than waiting for the fix at the end of the week and confirming that it would fix. I did the following and it resolved my issue! Thanks!

FYI this is on an Android 10 device running the latest update of the 3.10 app from the Android store.

Steps to resolve:

  1. Back up keys
  2. Force stop app, clear cache, clear storage
  3. Open app, allow it to install latest updates
  4. Reimport keys
  5. Transfer the locked funds, no more -6005 error!

@dpglobal, if this is different than what you did maybe give it a try? Its sounds like you are more experienced with Incognito than I am, so you have probably done the above. Hopefully you are able to get this resolved soon!

2 Likes
#30

Did you get (WEB_JS_ERROR(-5)) error?

#31

I’m sorry to inform you that the fix for this issue will be delayed to next Tuesday.

2 Likes
#32

Hello, any update on this fix? It started happening randomly and now I can’t make any trades on pDex or even moves from one incognito account to another.

image

1 Like
#33

I’ve been waiting weeks for an update. I wish you well my friend :rofl:

Quest wheel spin issue [ghost pending transaction]
#34

Update: I was able to import my private key on another device, transfer funds to a second incognito account, go back to my main device, move funds from the second account to the pDex, trade some PRV for another coin, and then transfer the coin to the first incognito account. After that I was able to make multiple trades on the pDex, so it seems it’s been unstuck for now.

4 Likes
Quest wheel spin issue [ghost pending transaction]
#35

I’m sorry for the delay. The fix will be released on this Friday.

4 Likes
#36

This issue will be fixed and release with the full disk issue on next Thursday.

3 Likes
#37

I had this error but I could fix it by saving my private key and reinstalling the app.

I hope it doesn’t come back :sweat_smile:.

1 Like
#38

Hi there, glad to join the community! Unfortunately my first post is going to confirm this bug/error…
I tried to unshield some BTC but was unsuccessful (Expired - Timed out). Now I cannot submit a new send/unshield request, nor provide liquidity for any token: “-6005 error message”.
UTXOs have been consolidated and I reinstalled Incognito App + imported my Master Key but it did not fix it. Still stucked…
Is the next App release on its way?
Thanks

2 Likes
#39

Hi @tmlc Welcome to incognito!!

There will be a hotfix shortly to solve this issue. apologies for any inconvenience this may bring.

3 Likes
#40

Thanks for the update! Hopefully the hotfix will be shipped very soon as Trade transactions are blocked as well because of this error and the market is moving fast… Any ETA please?

2 Likes
#41

I too am suffering from this. Guess we are all just in it for the wait.

3 Likes
#42

Update: It seems to be working again without any action from my side (no App update, no reinstall)… No more -6005 error message on Provide/Trade and I could send/unshield ptokens back to public space again.

As I am trying to catch up with Incognito s tech and docs it would be great to get some feedback on this stressful user experience:

  • Initial unshield request was tagged as Expired/Timeout. Does it mean that there were no custodian who could match my request (no public token available)? (cf. Portal´s api specs)
  • Then the -6005 error has been displayed, and “blocked” every new transaction. Because of a 24h delay ? (Unshield step 4 or auto-liquidation in the api docs)

Does it make sense or this is not related to Portal ops and I should dig deeper into Incognito s docs? :slight_smile:

2 Likes
#43

Mine seems to have fixed itself today too, was able to unshield successfully. It’s almost as if it was hung up, with a full disk. Weird! Haha :laughing:

2 Likes
#44

The fix has been released. Please update to the latest version (4.1.0). Thanks. :sweat_smile:

7 Likes