Hi everyone,
I'm updating this thread with a new development:
Previously, the verification failed with a "DCL account owner does not match the signed file" error. Now, the console no longer recognizes the VID at all, showing:
> "Can't verify. Please use your CSA-issued vendor ID."
CSA support has already confirmed that our VID `0x15FE` (5630) is valid and correctly bound to the new DCL account `cosmos1nep46y6hl2uqvq4zquv86y3z6uuyl74ma76qym` on the mainnet (confirmed via their official API).
The email as below:
@dengpeng wrote:
Hi everyone,
I'm with Senscomm Semiconductor, and I'm having trouble verifying our CSA-issued Vendor ID (VID) on the Google Home Developer Console.
Our VID is **0x15FE (decimal 5630)**. We have completed the DCL account change process with CSA, and the new account `cosmos1nep46y6hl2uqvq4zquv86y3z6uuyl74ma76qym` is confirmed as the active Vendor account on the DCL mainnet.
However, the verification keeps failing with these two errors:
1. DCL account owner does not match the signed file.
2. Signature does not match the public key in DCL.
The signature is generated correctly using the new account, but it seems the Google verification service is still checking against the old account data.
The issue may appear to be a cache synchronization issue on the Google side, as the DCL web UI confirms the new account is correctly bound to the VID.
Could you please manually refresh the cached data for my VID `0x15FE` so that the verification service recognizes the new DCL account?
Has anyone encountered this before? Is there a way to refresh the cached VID information on the Google side?
Thank you for your help!
This confirms the issue is entirely on the Google side, where the verification service is no longer able to retrieve the VID information from the DCL at all.
Could someone from the Google team please manually refresh the cached data for VID `0x15FE` to resolve this synchronization issue?
Thank you for your help.
