-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
json: cannot unmarshal object #981
Comments
Hi, thanks for opening an issue 🙏🏻 Please don't disclose your API token next time. I cannot reproduce this issue, without disclosing sensitive data, do you have a sample of phone number that triggers this error ? Which country code is it ? |
Hi, thank for the helpful tool. ovh: json: cannot unmarshal object into Go value of type []suppliers.OVHAPIResponseNumber country code is +84 (Vietnam) |
Should be fixed in v2.4.1, I'd appreciate if you guys could try it, thanks! |
And as I do to update to version 2.4.1 having installed and cloned version 2.4.0 on kali linux?.. I delete the directories and clone d new? (example: Git clone......) |
@ManuelQ59 Just run |
1734277#### |
@beelzebro Did you try the latest version ? |
yes |
The Error is still showing for me how do i fix it? |
Hey I still have the same error as the first message the country code is +359 |
I too am receiving OVH Telecom scan: json: cannot unmarshal object into Go value of type []suppliers.OVHAPIResponseNumber |
I have the same issues for Romania numbers (+40) |
Duplicate of #1106 |
Sorry I still have this Issue on Version v2.7.0 with German numbers (+49). |
Hi, I still have the same error as the first message the country code is (+57) |
error i have:
The following scanners returned errors:
ovh: json: cannot unmarshal object into Go value of type []suppliers.OVHAPIResponseNumber
i ran the following command:
NUMVERIFY_API_KEY=<redacted> phoneinfoga scan -n
i'm assuming that json is supposed to supply some sort of data, which its not. would like to know how i fix this error.
DE:
kali linux
The text was updated successfully, but these errors were encountered: