Getting invalid json body from server

Issues
#1

image-19.png
image-19.png1885×353 104 KB

This should have been fixed?

#2

I have the same issue, it’s a different one I believe from the CORS one mentioned above.

@chungwu I think this is the same one I have from our DM’s :+1:

#3

Help? @yang this is our most important page that doesn’t work now

#4

Www.tabnine.com/pro

#5

@valid_chipmunk We’re looking now - are you still seeing that error when making requests to that endpoint? https://codegen.plasmic.app/app/v1/loader/code/published?platform=next&projectId=c9YBWngqQY8KasE2nLibmy

#6

Yes… it does work for the preview environment… which is weird

#7

staging.tabnine.com/pro - working
www.tabnine.com/pro - does not work

#8

what’s your nextjs / node version?

#9

@very_crab has run into similar issues before (still trying to chase down the root cause), but re-deploying seems to fix it for him

#10

node 16.13.1

#11

next 12.2.5

#12

We’ve updated plasmic package and redeployed… and it works now. Not sure if it’s related

#13

Good to know - thanks @valid_chipmunk, and apologies for the production impact on your page. We’ll need to keep digging into what happened here. Please let us know if you experience anything else with this in the meantime.

#14

Thanks guys

#15

Could you try upgrading to the latest loader package again? We’ve added some more logging to see exactly what response you’re receiving when json parsing fails

#16

It’s late evening (9PM) here - so I can do it only tomorrow

#17

hmm, I’m still seeing 500 on tabnine.com/pro :thinking_face:

#18

Weird… doesn’t happen to me now

#19

Oh… it does

#20

Dammit