Altme shows "something went wrong, please try again later" and beacon shows "successfully signed payload"

[dansan566]

System: Altme Version: 2.5.3 (452) iPhone 12

Issue: When signing the member credential as a trust anchor, the beacon pop-up shows "successfully signed payload", within Altme "something went wrong, please try again later".

How to reproduce: It should be the same issue if Altme (approved member) wants to sign a new user credential.

[dansan566]

Hey @hawkbee1, any progress on this issue?

[hawkbee1]

I'm on vacation until August @dansan566

[bibash28]

I think this issue is occurring when the account list does not contain the required Tezos account.. @dansan566

[dansan566]

what do you mean by that @bibash28? can you elaborate? why does it work with another wallet?

[bibash28]

Can you again test with the latest builds? @dansan566

[dansan566]

Used Version 2.10.10 (493) Both accounts were also revealed (included in the blockchain storage) before and had some tez (ghostnet) on it.

Again, Beacon says successfully signed payload, Altme shows an error

[jdsika]

@ThierryThevenet high prio

[jdsika]

Please update beacon and try to fix this for next week. It is open since may @hawkbee1

[ThierryThevenet]

@hawkbee1

[hawkbee1]

@jdsika Currently I can't ask a credential with new account. When https://ascs.digital/redirect is called I get the following error in the browser:

This site can’t provide a secure connection ascs.digital uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH

[jdsika]

Please wait until the evening - you picked the one day where we redeploy contracts and purge the database :D

[dansan566]

@hawkbee1 please use https://staging.identity.ascs.digital/ and create a user identity. @ThierryThevenet registered Talao - he can approve you. Once he will try to sign your credential, it will result in this issue

[hawkbee1]

I'm not finished with preparing the build but it looks like there is good news for this ticket.

[jdsika]

Bravo 👏🏻