I will also add that the problem is with nicehash for choosing google auth app as a compulsory 2FA verification process with withdrawing from a account.
Since no one has pointed you to these information, I'll reply one last time:
You can use any Authenticator app that supports "
TOTP" protocol, example is "
Aegis Authenticator" with 4.9 rating in Play Store.
However, any other Authenticator app aren't any different with Google's since all of them are using the same
RFC-6238 standard to generate OTP codes.
Sigh!!
Edit: with the google app it keeps sending a new code every 30sec
Google isn't sending you new codes, the app is generating codes in every 30 seconds within the app/phone.
(
it can even do it while offline since Google isn't involved with its OTP code generation, read the link to RFC-6238 above to see how it works)
ELI5 explanation: the code is generated using the time and your secret code (
from the QR) within the device.
Since Nicehash also has your secret code, it can generate the same OTP code by following the same algorithm as described in RFC-6238.
That 30 second is the set delay by the RFC-6238 standard and setting a higher limit will make it generate a different code than what Nicehash is expecting.
The trick is to use the displayed code when it just changed; do not use the code if it's almost 30 second, wait for it to change.
-snip- and i put in the email code and the google app code but it keeps saying "invalid"
If it's within that 30 second timer of the OTP Code, you're probably using an old email Verification Code which was sent by Nicehash the second last time you clicked "
Enable 2fa verification" button.
Because each time you click it, Nicehash will send you a new verification code, the old ones wont work.
P.S.: This will be my last reply to this tread.