GetIpInfoBatch: panic: interface conversion: interface {} is *interface {}, not *ipinfo.Core

[ipinfo]

GetIpInfoBatch: panic: interface conversion: interface {} is *interface {}, not *ipinfo.Core

[jcace]

thanks! looks like it works now. Tested v2.9.1

Must've been an invalid IP address because I'm getting expected result now. Error message is much better too when I pass in an invalid one.

[UmanShahzad]

Are you putting a real token and not getting rate limited? Either of these may cause the issue, but please do confirm.

[rm-Umar]

I just checked and I was able to replicate the error if you put an empty string in the client as token then it throws this error

client := ipinfo.NewClient(nil, nil, "")

So putting the token should solve your issue.
cc: @UmanShahzad

[UmanShahzad]

I see. Can we fix so that it doesn't panic, and instead just returns an error?

[jcace]

I am using my real token - just redacted it for the post:

	client := ipinfo.NewClient(nil, nil, "39b807185xxxxx")

Doesn't seem like I'm being rate limited - brand new account and testing with only a single IP in the request

[rm-Umar]

I see. Can we fix so that it doesn't panic, and instead just returns an error?

I think a simple check on the token can solve this issue.

[rm-Umar]

I am using my real token - just redacted it for the post:

	client := ipinfo.NewClient(nil, nil, "39b807185xxxxx")

Doesn't seem like I'm being rate limited - brand new account and testing with only a single IP in the request

I am unable to replicate this error I've tried different scenarios and the only scenario giving me this error is when you pass "" as token. I also noticed you are using SDK version 2.8.0 you can try updating to 2.9.0 meanwhile I'll look into it further and try to find the cause of this problem.

[rm-Umar]

The error also occurs if we put an invalid IP in the batch request

batchResult, err := client.GetIPInfoBatch(
		[]net.IP{
			net.ParseIP("1.1.1.1"),
			net.ParseIP("8.8.8.8"),
			net.ParseIP(""),
			}

[UmanShahzad]

Will do a patch release then you can try again.

[rm-Umar]

@jcace just released v2.9.1 your error should be fixed in this patch.
Thank you for your feedback! 😃