<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hotfix on Codemagic blog</title><link>https://blog.codemagic.io/tags/hotfix/</link><description>Recent content in Hotfix on Codemagic blog</description><generator>Hugo</generator><language>en</language><copyright>©Nevercode Ltd | All Rights Reserved | Codemagic is pending trademark of Nevercode Ltd.</copyright><lastBuildDate>Wed, 13 May 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://blog.codemagic.io/tags/hotfix/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Fix a React Native Production Bug Without Waiting for App Store Review</title><link>https://blog.codemagic.io/react-native-hotfix-without-app-store-review/</link><pubDate>Wed, 13 May 2026 00:00:00 +0300</pubDate><guid>https://blog.codemagic.io/react-native-hotfix-without-app-store-review/</guid><description>&lt;blockquote>
&lt;p>This article is written by &lt;strong>Karl Suhajda&lt;/strong>&lt;/p>
&lt;/blockquote>
&lt;p>There is a specific kind of dread that comes with finding a critical bug in a production React Native app. The fix is usually straightforward: a broken API call, a logic error, a UI state that did not account for an edge case. You can see exactly what went wrong and exactly how to correct it. The code change might take an hour.&lt;/p></description></item></channel></rss>