<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wails on Carlos Urreta&#39;s Weblog</title>
    <link>https://urreta.com/tags/wails/</link>
    <description>Recent content in Wails on Carlos Urreta&#39;s Weblog</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 06 Aug 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://urreta.com/tags/wails/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TIL: HTML Error Responses Can Crash Wails JavaScript Bindings</title>
      <link>https://urreta.com/2025/08/06/til-html-error-responses-can-crash-wails-javascript-bindings/</link>
      <pubDate>Wed, 06 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://urreta.com/2025/08/06/til-html-error-responses-can-crash-wails-javascript-bindings/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Problem:&lt;/strong&gt;&#xA;I was working on a Wails desktop application and had the Go backend upload a photo to my own API (another service). When the photo failed to upload I didn&amp;rsquo;t catch that my own upload endpoint was returning an HTML error response instead of JSON. This caused the Javascript VM to show &amp;ldquo;NeedDebuggerBreak trap&amp;rdquo; and promises never resolved.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Solution:&lt;/strong&gt;&#xA;I didn&amp;rsquo;t fully debug whether the issue was because the HTML was too large or special characters in the response were causing an issue. The solution was to have the API return a proper JSON response.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
