Check Authencity "Transaction ocurred at time when issuing address was not considered valid"

hi i’ve seen this problem , in other post ,i followed them but i cant solve it

my cert-tools conf.ini

issuer information

issuer_url = https://cloudmex.io/

issuer_email = hola@cloudmex.io

issuer_name = Universidad Tecnologia de Cloudmex

issuer_id = https://raw.githubusercontent.com/chidoman321/profile/master/issuer.json

revocation_list=https://6073a6b0e4e0160017ddfc72.mockapi.io/revocation

issuer_signature_lines={“fields”: [{“job_title”: “University Issuer”,“signature_image”: “images/issuer-signature.png”,“name”: “Your signature”}]}

issuer_public_key=ecdsa-koblitz-pubkey:0x85fca60bBCb1ab6103AD89d176e407aFdCDEe914

my cert-issuer conf_ethtest.ini
issuing_address =0x85fca60bBCb1ab6103AD89d176e407aFdCDEe914

my issuer profile

“publicKey”: [
{
“id”: “ecdsa-koblitz-pubkey:0x85fca60bBCb1ab6103AD89d176e407aFdCDEe914”,
“created”: “2017-06-29T14:48:03.814936+00:00”
}
],

example transaction

Ropsten Transaction Hash (Txhash) Details | Etherscan

it only happens on mobile(wallet) , with the universal verifier it doesnt appear

can someone who already did this could help me please ?

Did you try the universal verifier on the same phone?
The error is thrown from this file: cert-verifier-js/ensureValidIssuingKey.js at fe86fc4ed497133e54d7d454ec8dc7fcf8c35e3b · blockchain-certificates/cert-verifier-js · GitHub, if that helps.
So it could be that: txTime = dateToUnixTimestamp(txTime); is returning something inconsistent, or something else. You can look at the conditions and hopefully debug the issue.

yes i tried the universal verifier and the issue doesnt show ,
the problem is at the blockcert wallet ,
aslo with cert-verifier-js ,it returns me the same error

getTransactionId
Code: getTransactionId Getting transaction ID - Status: starting
Code: getTransactionId Getting transaction ID - Status: success
Code: computeLocalHash Computing local hash - Status: starting
Code: computeLocalHash Computing local hash - Status: success
Code: fetchRemoteHash Fetching remote hash - Status: starting
{“error”: “Transaction 14cc4671bb0e5ca821038ca524386c88ffa713979b83ac7cfae870798c450451 not found.”}
Code: fetchRemoteHash Fetching remote hash - Status: success
Code: getIssuerProfile Getting issuer profile - Status: starting
Code: getIssuerProfile Getting issuer profile - Status: success
Code: parseIssuerKeys Parsing issuer keys - Status: starting
Code: parseIssuerKeys Parsing issuer keys - Status: success
compareHashes
Code: compareHashes Comparing hashes - Status: starting
Code: compareHashes Comparing hashes - Status: success
checkMerkleRoot
Code: checkMerkleRoot Checking Merkle Root - Status: starting
Code: checkMerkleRoot Checking Merkle Root - Status: success
checkReceipt
Code: checkReceipt Checking Receipt - Status: starting
Code: checkReceipt Checking Receipt - Status: success
DB connected established
Superuser is already created
Inmueble Super ya se esta en la bd
checkRevokedStatus
Code: checkRevokedStatus Checking Revoked Status - Status: starting
Code: checkRevokedStatus Checking Revoked Status - Status: success
checkAuthenticity
Code: checkAuthenticity Checking Authenticity - Status: starting
Code: checkAuthenticity Checking Authenticity - Status: failure
The step checkAuthenticity fails with the error: Transaction occurred at time when issuing address was not considered valid.

i’m checking ensureValidIssuingKey file

this is before calling ensureValidIssuekey image image

For all intent and purposes, the latest version of cert-verifier-js gives a more explicit error message to help figure out the issue.

However in your case, it seems to be beyond that error message. I don’t know why you would have a “invalid date” here and probably need to investigate on your side.

okay broh, i hope my team give me sometime to checkout the issue, also i didn’t tell you, but i am able to bypass the time check if i dont add the key created at profile.json , example image , also how do you get the time from the eth_ropsten blockchain ?

The time should be retrieved by the explorer, so if you are having problems around that piece, you could inspect what is being returned by the explorer API.