Skip to content
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

[BUG] In-App sync request - Error 500 #2365

Closed
1 of 2 tasks
saenzramiro opened this issue Mar 29, 2024 · 1 comment · Fixed by #2366
Closed
1 of 2 tasks

[BUG] In-App sync request - Error 500 #2365

saenzramiro opened this issue Mar 29, 2024 · 1 comment · Fixed by #2366
Labels
bug Something isn't working

Comments

@saenzramiro
Copy link

Issue Summary

Since a few days, I started to experience an internal server error when trying to sync the configurations from https://app.formbricks.com. I tested this using the npm package and also the CDN library.

Steps to Reproduce

  1. Initialize a base project.
  2. Add the HTML CDN library using the Formbricks Cloud services.

Expected behavior

To work as expected.

Other information

The response of the request:

https://app.formbricks.com/api/v1/client/{envId}/in-app/sync/{idHidden}?version=1.6.5

{
    "code": "internal_server_error",
    "message": "Unable to handle the request: [\n  {\n    \"code\": \"invalid_type\",\n    \"expected\": \"date\",\n    \"received\": \"string\",\n    \"path\": [\n      \"segment\",\n      \"createdAt\"\n    ],\n    \"message\": \"Expected date, received string\"\n  },\n  {\n    \"code\": \"invalid_type\",\n    \"expected\": \"date\",\n    \"received\": \"string\",\n    \"path\": [\n      \"segment\",\n      \"updatedAt\"\n    ],\n    \"message\": \"Expected date, received string\"\n  }\n]",
    "details": {}
}

Screenshots

image

Environment

  • Formbricks Cloud (app.formbricks.com)
  • Self-hosted Formbricks

Desktop (please complete the following information)

- OS: Windows 10
- Node: v18.16.0
- npm: v9.5.1
@mattinannt
Copy link
Member

@saenzramiro thanks for pointing this out 😊 I just pushed a fix that should solve the issue :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants