Kartik
Kartik
This is all on local testing the request goes straight from node-fetch to the uWS/HyperExpress webserver so no proxies involved. I don't think the `content-length` header is provided by applications...
I see, that makes sense. Seems like it's low priority at the moment. I guess I'll wait on Alex's response to see whether I should push out the file uploading...
Ohh I didn't even know that, in that case I can see why this is low priority.
I see, I implemented file uploads with multipart forms using busboy parser and it seems browsers provide a content-length header so should be no problem there.
@Codelica I am currently on Expo SDK v47 and none of the solutions above or the ones from related issues seem to fix my issue for receiving the notification response...
@peterzanetti and anyone else that encounters this issue for the future. I was able to resolve this issue by properly implementing the layout provider as the documentation does not do...
Hello, I was able to achieve this by putting pointerEvents="none" on the top most view of the header. Note! If you have any kind of touchables or switches, they will...
Hey, this is a good idea and can certainly be implemented but it will be done in a non breaking way as the current Server.close() method is meant to be...
Hey, which signature do you think would be a better API going forward: ```js // This simply adds the `graceful` argument and changes the return type to now potentially return...
The `Server.shutdown()` method has been implemented in the latest version `6.15.0` which should resolve your issue.