!2faok not working + (auto) !loot isn't getting confirmed

[px]

Right now, i need to confirm every !loot request with WinAuth manually. I've done all the .maFile and android: shenanigans but nothing gets confirmed by asf. Also when typing !2faok they all say success, but they don't really get confirmed and i still need to confirm them with WinAuth.
If there is any setting i'm missing, please tell me.
example config as follows:

Originally posted by config:

{
"AcceptConfirmationsPeriod": 0,
"AcceptGifts": false,
"CardDropsRestricted": true,
"CustomGamePlayedWhileFarming": "[FARM]",
"CustomGamePlayedWhileIdle": "[IDLE]",
"DismissInventoryNotifications": true,
"Enabled": true,
"FarmingOrder": 0,
"FarmOffline": false,
"GamesPlayedWhileIdle": [],
"HandleOfflineMessages": false,
"IsBotAccount": true,
"LootableTypes": [
1,
3,
5
],
"PasswordFormat": 0,
"Paused": false,
"RedeemingPreferences": 3,
"SendOnFarmingFinished": true,
"SendTradePeriod": 0,
"ShutdownOnFarmingFinished": false,
"SteamLogin": "XXXXXXXXXXXXXXXX",
"SteamMasterClanID": 0,
"SteamMasterID": 76561198122314569,
"SteamParentalPIN": "0",
"SteamPassword": "XXXXXXXXXXX",
"SteamTradeToken": "_nrX0gQ3",
"TradingPreferences": 0
}

And yes, this is a straight port from the issues, so it is written like it was a bug, apparently it isn't.

[Archi]

If !2fa works and gives you the same code as your authenticator, but !2faok is not working, then it means that you inputted invalid deviceID, as stated in wiki/escrow section.

There is no 7 days delay or anything else for ASF 2FA import, it works right away. If it doesn't then you screwed up something during import. Also keep in mind that if one copy of authenticator gets given confirmation, then no other copy will, so if you expect ASF 2FA to work properly then you shouldn't do any other auto-pooling, unless you're also willing to accept them from that source.

[px]

Originally posted by Archi:

If !2fa works and gives you the same code as your authenticator, but !2faok is not working, then it means that you inputted invalid deviceID, as stated in wiki/escrow section.

There is no 7 days delay or anything else for ASF 2FA import, it works right away. If it doesn't then you screwed up something during import. Also keep in mind that if one copy of authenticator gets given confirmation, then no other copy will, so if you expect ASF 2FA to work properly then you shouldn't do any other auto-pooling, unless you're also willing to accept them from that source.

Okay - this might be the issue. I have CTRL+V'd the android:... Into CMD and now heavily suspect that that didn't work... I thought it did as asf didn't complain (lol).
Sooo... How do i paste something into CMD? And what do i need to do to be able re-enter the android part?

Edit: WinAuth only auto-confirmes when it's running, which it isn't by default, so it does no auto-pooling unless i ask it to do so, so i hope that isn't a problem.

[Archi]

Everything is explained in escrow section on the wiki, why you won't bother reading it?

And answer how to copy-paste in cmd is somewhere on the google I guess .

[px]

okay, i did all of it, but now ASF keep crashing when i use !2faok (BOT) on any bot.

Originally posted by log:

2017-02-09 12:42:16|ASF-8836|FATAL|ASF|UnhandledExceptionHandler() System.FormatException: Invalid length for a Base-64 char array or string.
at System.Convert.FromBase64_Decode(Char* startInputPtr, Int32 inputLength, Byte* startDestPtr, Int32 destLength)
at System.Convert.FromBase64CharPtr(Char* inputPtr, Int32 inputLength)
at System.Convert.FromBase64String(String s)
at ArchiSteamFarm.MobileAuthenticator.GenerateConfirmationKey(UInt32 time, String tag)
at ArchiSteamFarm.MobileAuthenticator.<GetConfirmations>d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ArchiSteamFarm.Bot.<AcceptConfirmations>d__66.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ArchiSteamFarm.Bot.<Response2FAConfirm>d__126.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ArchiSteamFarm.Bot.<Response2FAConfirm>d__127.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at ArchiSteamFarm.Bot.<Response>d__75.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ArchiSteamFarm.Bot.<HandleMessage>d__85.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ArchiSteamFarm.Bot.<OnFriendMsg>d__106.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_1(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

[Archi]

> Invalid length for a Base-64 char array or string

Which means you again imported wrong data .

[px]

dangittttt
i took the data out of the program used to extract the steam stuff out of the ios stuff (backup-ed obv). Done some checking, same account also doesn't work in winauth. maybe it is the formatting? i'll put the thing in here with all stuff replaced with X's

Originally posted by authdata:

{
"shared_secret": "XXXXXXXXXXXXXXXXX",
"uri": "XXXXXXXXXXXXX",
"steamid": "XXXXXXXXXXXXXXXXXXXXXXXX",
"revocation_code": "XXXXXX",
"serial_number": "XXXXXXXXXXXXXXXXXXXXX",
"token_gid": "X",
"identity_secret": "XXXXXXXXXXXXXX",
"secret_1": "otpauth://totp/Steam:hennihenner?secret=XXXXXXXXXXXXXXXXXXXXXXXXXX&issuer=Steam",
"server_time": "hennihenner",
"account_name": "XXXXXXXXXXXXXXX",
"steamguard_scheme": "XXXXXXXXXX",
"status": "Claunia.PropertyList.NSDictionary",
"device_id": "android:XXXXXXXXXXXXXXXXXXXXXXXXXXX"
}

Should the device_id really be in there?
i doubt that the breaks after and before { & } change anything.

I've just realized that the server time is hennihenner. Something went wrong. Really wrong.

[Archi]

I don't know if the program generated proper data or not, I'm not a developer of it, so it's best to ask developer himself if your data is correct.

You firstly import authenticator to WinAuth, then verify that BOTH generating tokens as well as receiving and accepting confirmations work, and then you export that data and import to ASF. If you import invalid data to ASF then you can only get not-working authenticator in best case, or ASF crash on invalid data in worst case (like you did).

Like stated on the wiki ASF makes use only of 3 properties - identity_secret, shared_secret and device_id (if it exists, if not you'll be asked about it). If it imports correctly then it means that ASF is able to read the data and convert it, which is good, but ASF can't check on it's own whether your provided data is correct or not - you're responsible of ensuring that the data you're importing is correct.

[Archi]

Although thanks for spotting legit ASF crash, I fixed it (caused by invalid shared_secret/identity_secret). It's not like it helps you in any way, as ASF 2FA would simply not work instead of crashing.

[px]

I did it! Just looked for another Base64 formatted entry and went with it. !2faok works fine with the account now.
Small alongside suggestion: Allow to mention all bots within <Bots> at once, maybe have !2faok * confirm all accounts at once, for example. Right now i just made a deactivated bot called AAA and ZZZ, so i type !2faok AAA..ZZZ, but it would obviously be better with a syntax for "all".

[Archi]

You already have !2faok ASF.

[px]

Originally posted by Archi:

You already have !2faok ASF.

oh. okay, thanks

[Frost]

Originally posted by Hennihenner farmskins.com:

I did it! Just looked for another Base64 formatted entry and went with it. !2faok works fine with the account now.
Small alongside suggestion: Allow to mention all bots within <Bots> at once, maybe have !2faok * confirm all accounts at once, for example. Right now i just made a deactivated bot called AAA and ZZZ, so i type !2faok AAA..ZZZ, but it would obviously be better with a syntax for "all".

Could you tell me how did you solve this problem? I have the same problem right now.
Thank you.