API returns error code 1008

Help - Plug n Play
1

I sent a request to the API below, and received the following response. Was there a change to the API around early December? Error code is 1008. Are there any relevant documents I can refer to?

API: https://signer.tor.us/api/allow
response: {“code”:1008,“error”:“Network not present, You’re using a very old version. Please upgrade to latest”,“success”:false}

2

Hello bg.choi@wemade.com!

Thank you for reaching out! It looks like you’re experiencing an issue with the Plug n Play SDK while calling the API, which is returning error code 1008.

Here’s a summary of the details you provided for our support team:

  • SDK Details: Plug n Play
  • Issue: API returns error code 1008
  • API Used: https://signer.tor.us/api/allow
  • Response from API: {"code":1008,"error":"Network not present, You're using a very old version. Please upgrade to latest","success":false}

It seems that the error message indicates you’re using an outdated version of the SDK. I recommend checking if you can upgrade to the latest version to resolve the issue.

For relevant documentation, you might want to refer to the Web3Auth documentation here for any recent changes or updates, especially around early December.

If you need further assistance, please don’t hesitate to ask!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

3

Due to internal circumstances, we cannot modify the package. The service is completely down due to the above error. Has Web3Auth announced any changes regarding this modification? If so, please let me know about the announcement.

4

Hey, which SDK are you using? Can you also share the version? We had already done community announcements and send the mails for the upgrade.

Please check the Announcements - Web3Auth Community

5

The announcement states that support will end in the end of this year, but does this mean it’s effective immediately on December 2nd? Since we were already planning to shut down our service by the end of the year, we assumed there was no need for further action.

6

Can you please share the details of the SDK you are using?

7

An external developer delivered a program created as a JS file using the web3auth package. However, it’s obfuscated, so I can’t verify the exact version of the package being used. Since we planned to discontinue its use by the end of the year, we didn’t think it was necessary to verify.

I’ve noticed that when the same program is used to connect to sapphire instead of aquanet, it works without any issues. Would this information be helpful?

8

Hey without any information on the SDK, it’s really not possible to help here. Can you please ask the details from the developer. Also, please share the project information like link, where we can try out, and get information.

9

Thank you for your response, and here is the link.

Its environment is set to aqua mainnet (Asia). However, when I changed it to sapphire for a test project, it worked.
I encountered error code 1008 on endpoints such as signer.tor.us/api/allow and polygon-signer.tor.us/api/allow. I’m curious to know if these endpoints have been deprecated.

10

I posted a question on Discord and was asked to send ticket information via DM, which I did 3 days ago. However, I’ve since discovered that I’ve been blocked on Discord. I find this response to be very strange. I’ve been a paying customer for almost a year and had no idea that this level of service wouldn’t provide answers to my questions.

I have two main questions:

  1. Since early December, I’ve been getting a 1008 error code from signer .tor .us/api/allow. Have there been any announcements or notifications regarding this? I couldn’t find anything in the links you provided.
  2. Why am I not getting any responses beyond AI-generated answers when I submit service tickets? Have you discontinued service operations?
11

Hey @bg.choi, I understand the frustration, I already shared the links to announcement where we have announced the deprecation of the SDKS.

  1. You are getting 1008 since December because we have deprecated those services. We had announced the deprecations back in July giving enough time to update.
  2. It’s not a bot generated response, it’s the basic detail I need to help you. I can’t help you if you can’t share the details of the SDK and version you are using. We have more than 10+ client facing SDKs, and every SDK has a different version which was deprecated. The link that you shared was for the Web3Auth Dashboard which we can’t access, and we can’t get the SDK details and version you are using from that.
12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.