AlexandreS

@D8H's answer is more pertinent than my Pull Request (I've been too hasty), you should apply their recommendations

Hi @cfrikke, Sorry for the inconvenience and thank you for taking the time to report this crash. If the window is still open after the crash, you should be able...

If you go in the Network tab of the developer tools and refresh with Ctrl + R, it should crash again and you should be able to see the network...

Thanks for the screenshot. When you're at that point, could you click on the first line and send the content of the tab called "Preview"?

Could you send the content of both Headers and Payload tabs, for both lines? Sorry, this is a bit cumbersome to do. We will soon release version 5.2.174. You could...

And could you send the Response tab content as well? Sorry for all those steps 😅

That's weird you're getting a 302 HTTP response code on this API call. In which country are you located?

Do you still have the issue? Your bug might have been caused by a cache issue from our underlying supplier.

Reopening the issue, let's wait for the next version to confirm the issue is gone.

Hi @cfrikke, Does this issue still happen?