<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Coding on QuickCoder</title>
    <link>https://quickcoder.org/tags/coding/</link>
    <description>Recent content in Coding on QuickCoder</description>
    <image>
      <title>QuickCoder</title>
      <url>https://quickcoder.org/images/papermod-cover.png</url>
      <link>https://quickcoder.org/images/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>xeladu</copyright>
    <lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://quickcoder.org/tags/coding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How To Enable Test Purchases For Your Android Apps</title>
      <link>https://quickcoder.org/posts/how-to-enable-test-purchases-for-your-android-apps/</link>
      <pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://quickcoder.org/posts/how-to-enable-test-purchases-for-your-android-apps/</guid>
      <description>&lt;h3 id=&#34;introduction&#34;&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Many developers want to monetize their apps to cover development costs. One common approach is a subscription-based app model. In this article, I am going to show you how to enable test purchases for your Android apps to easily test your subscriptions and digital products.&lt;/p&gt;
&lt;h3 id=&#34;what-you-need&#34;&gt;What you need&lt;/h3&gt;
&lt;p&gt;To get started, you need a working Android app in the internal test track and test users.&lt;/p&gt;
&lt;p&gt;To allow test purchases for your test users, go to the &lt;strong&gt;Play Console&lt;/strong&gt; -&amp;gt; &lt;strong&gt;Settings&lt;/strong&gt; -&amp;gt; &lt;strong&gt;License testing&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Fix CORS Errors in Web Applications</title>
      <link>https://quickcoder.org/posts/how-to-fix-cors-errors/</link>
      <pubDate>Tue, 08 Aug 2023 00:00:00 +0000</pubDate>
      <guid>https://quickcoder.org/posts/how-to-fix-cors-errors/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;We&amp;rsquo;ve all been there, cursing because of CORS. You make an HTTP request only to be greeted by a frustrating error message in your browser. With this short article, I want to show you how to fix CORS errors in web applications.&lt;/p&gt;
&lt;h1 id=&#34;what-is-cors&#34;&gt;What is CORS?&lt;/h1&gt;
&lt;p&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/Cross-origin_resource_sharing&#34;&gt;Cross-Origin Resource Sharing&lt;/a&gt; (CORS) is a mechanism that allows web browsers or other web clients to make cross-origin requests, which are normally prohibited by the Same-Origin Policy (SOP). CORS is a compromise that provides greater flexibility on the Internet while maintaining high security measures. The &lt;a href=&#34;https://en.wikipedia.org/wiki/Same-origin_policy&#34;&gt;Same-Origin Policy&lt;/a&gt; (SOP) is a security feature implemented by web browsers that restricts web pages from making requests to a different origin than the one that served the web page. In simple terms, SOP prevents malicious web pages from stealing data or executing actions on behalf of a user without their knowledge or consent.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How To Fix A Broken Branch After A Git Merge Or Git Rebase</title>
      <link>https://quickcoder.org/posts/git-rebase-fix/</link>
      <pubDate>Sun, 13 Mar 2022 00:00:00 +0000</pubDate>
      <guid>https://quickcoder.org/posts/git-rebase-fix/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction.&lt;/h1&gt;
&lt;p&gt;Problems when merging or rebasing branches in a version control system like git can happen to anyone. I want to show you one way that works pretty good to resolve the issue. Of course, there are other ways like reverting the rebase and doing it again, but I like this approach more.&lt;/p&gt;
&lt;h2 id=&#34;relevant-gitcommands&#34;&gt;Relevant git commands&lt;/h2&gt;
&lt;p&gt;▶ &lt;a href=&#34;https://git-scm.com/docs/git-cherry-pick&#34;&gt;git cherry-pick&lt;/a&gt;&lt;br&gt;
▶ &lt;a href=&#34;https://git-scm.com/docs/git-log&#34;&gt;git log&lt;/a&gt;&lt;br&gt;
▶ &lt;a href=&#34;https://git-scm.com/docs/git-checkout&#34;&gt;git checkout&lt;/a&gt;&lt;br&gt;
▶ &lt;a href=&#34;https://git-scm.com/docs/git-branch&#34;&gt;git branch&lt;/a&gt;&lt;/p&gt;
&lt;h1 id=&#34;1-create-a-new-branch-from-the-mergerebase-target&#34;&gt;1 Create a new branch from the merge/rebase target&lt;/h1&gt;
&lt;p&gt;Let’s assume you wanted to rebase the &lt;code&gt;main&lt;/code&gt; branch onto your &lt;code&gt;dev&lt;/code&gt; branch and something went wrong because the application does launch anymore.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
