{"id":57,"date":"2026-01-14T16:55:43","date_gmt":"2026-01-14T16:55:43","guid":{"rendered":"https:\/\/balamurali.in\/blog\/?p=57"},"modified":"2026-02-23T14:25:57","modified_gmt":"2026-02-23T14:25:57","slug":"how-i-published-my-first-ios-app-a-guide-to-avoiding-app-store-rejections-case-study-paisaflow","status":"publish","type":"post","link":"https:\/\/balamurali.in\/blog\/learn-with-me\/how-i-published-my-first-ios-app-a-guide-to-avoiding-app-store-rejections-case-study-paisaflow\/","title":{"rendered":"How I Published My First iOS App: A Guide to Avoiding App Store Rejections (Case Study: PaisaFlow)"},"content":{"rendered":"\n

Building an iOS app is hard work, but submitting it to the App Store can feel like a whole different battle. Recently, I went through the process of publishing PaisaFlow<\/strong>, a privacy-focused expense tracker tailored for the Indian market.<\/p>\n\n\n\n

While the coding part was straightforward, the submission process threw several curveballs\u2014from bundle ID confusion to screenshot automation and encryption compliance.<\/p>\n\n\n\n

If you are about to hit that “Submit for Review” button, read this first. Here is a breakdown of the specific issues I faced and how you can avoid them to get your app approved faster.<\/p>\n\n\n\n

1. The Bundle ID Trap: App vs. Extensions<\/h2>\n\n\n\n

One of the first errors I encountered happened during the archiving process. My project includes the main app and a Widget extension. When I tried to upload the build, I saw two different bundle IDs listed (com.paisaflow.app<\/code> and com.paisaflow.app.widget<\/code>), which made me worry I had to register the widget separately in App Store Connect.<\/p>\n\n\n\n

The Mistake:<\/strong>
I initially tried to archive the Widget Extension scheme, thinking I needed to upload it individually.<\/p>\n\n\n\n

The Fix:<\/strong>
You only need to list the Main App Bundle ID<\/strong> in App Store Connect.<\/p>\n\n\n\n

    \n
  1. In Xcode, ensure your Scheme<\/strong> is set to the main application (e.g., BudgetApp<\/code>), not<\/em> the WidgetExtension.<\/li>\n\n\n\n
  2. When you archive the main app, Xcode automatically embeds the widget extension inside it.<\/li>\n\n\n\n
  3. You do not need to register the widget’s bundle ID separately in the App Store Connect portal.<\/li>\n<\/ol>\n\n\n\n

    2. Validating “Privacy-First” Features (Face ID)<\/h2>\n\n\n\n

    PaisaFlow uses Face ID to lock the Credit Card Vault. Even though the code was working perfectly in the simulator, I risked an immediate crash on real devices.<\/p>\n\n\n\n

    The Issue:<\/strong>
    I missed a critical key in the Info.plist<\/code>. Without this key, the OS terminates your app immediately upon a Face ID request, which is an instant rejection during App Review.<\/p>\n\n\n\n

    The Fix:<\/strong>
    If you use Face ID (via the LocalAuthentication<\/code> framework), you must<\/em> add the NSFaceIDUsageDescription<\/code> key to your Info.plist<\/code>.<\/p>\n\n\n\n

      \n
    • Key:<\/strong> NSFaceIDUsageDescription<\/code><\/li>\n\n\n\n
    • Value:<\/strong> A clear explanation of why<\/em> you need it.\n
        \n
      • Example:<\/em> “PaisaFlow uses Face ID to securely unlock your Credit Card Vault.”<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

        3. The Screenshot Struggle: Automation is Key<\/h2>\n\n\n\n

        App Store Connect requires screenshots for multiple device sizes (6.5″ and 6.7″). Taking these manually for every screen, in both Light and Dark modes, is a nightmare.<\/p>\n\n\n\n

        My Approach:<\/strong>
        Instead of manual capture, I set up an automated UI Test in Xcode (XCUITest<\/code>).<\/p>\n\n\n\n

          \n
        1. Dummy Data Seeder:<\/strong> I created a DummyDataSeeder.swift<\/code> that runs only when a specific launch argument is passed (-UITest_SeedDummyData<\/code>). This populates the app with realistic data (e.g., “HDFC Infinia” cards, “Swiggy” transactions) so the screenshots don’t look empty.<\/li>\n\n\n\n
        2. Keyboard Issues:<\/strong> A common mistake is taking screenshots with the keyboard covering half the UI. In my tests, I added code to explicitly dismiss the keyboard before the test snapped the picture.<\/li>\n\n\n\n
        3. Light Mode Enforcement:<\/strong> I realized halfway through that my simulator was stuck in Dark Mode. I added a flag to force ThemeManager.shared.currentTheme = .light<\/code> during tests to ensure consistent marketing images.<\/li>\n<\/ol>\n\n\n\n

          4. Export Compliance & Encryption<\/h2>\n\n\n\n

          When submitting, Apple asks a scary question: “Does your app use encryption?”<\/em><\/p>\n\n\n\n

          The Reality:<\/strong>
          PaisaFlow uses SwiftData, secure Keychain storage, and HTTPS. Technically, this is<\/em> encryption.<\/p>\n\n\n\n

          The Answer:<\/strong><\/p>\n\n\n\n

            \n
          • Question:<\/strong> Does your app use encryption? Yes.<\/strong><\/li>\n\n\n\n
          • Exemption:<\/strong> Does your app qualify for exemptions? Yes.<\/strong><\/li>\n\n\n\n
          • Reason:<\/strong> Select “Standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple’s operating system.”<\/strong><\/li>\n<\/ul>\n\n\n\n

            Because we rely on standard iOS frameworks (Keychain, HTTPS) rather than custom proprietary encryption, we are exempt from submitting heavy export documentation to the US government.<\/p>\n\n\n\n

            5. Privacy Policy & Support URL (The “No Website” Problem)<\/h2>\n\n\n\n

            You cannot submit an app without a Privacy Policy URL and a Support URL. Since PaisaFlow is an offline-only app, I didn’t have a dedicated website.<\/p>\n\n\n\n

            The Quick Fix:<\/strong>
            You don’t need to buy a domain or build a website just to launch.<\/p>\n\n\n\n

              \n
            1. Notion:<\/strong> I created two simple public Notion pages\u2014one for Privacy Policy and one for Support.<\/li>\n\n\n\n
            2. Content:<\/strong> The policy simply states: “PaisaFlow does not collect, store, or transmit any user data. All financial information is stored locally on your device.”<\/em><\/li>\n\n\n\n
            3. Submission:<\/strong> I used these public Notion links in App Store Connect. Apple accepted them without issue.<\/li>\n<\/ol>\n\n\n\n

              6. App Privacy Labels (The Questionnaire)<\/h2>\n\n\n\n

              Filling out the “App Privacy” section in App Store Connect can be confusing for local-only apps.<\/p>\n\n\n\n

              The Confusion:<\/strong>
              The questionnaire asks if you collect “Contact Info” or “Financial Info.” Since my app lets users input this data, do I say “Yes”?<\/p>\n\n\n\n

              The Solution:<\/strong><\/p>\n\n\n\n

                \n
              • Technically, the data never leaves the device, so you could<\/em> say “No Data Collected”.<\/li>\n\n\n\n
              • However, for transparency, I selected “Financial Info”<\/strong> and “Contacts”<\/strong>.<\/li>\n\n\n\n
              • Crucial Step:<\/strong> For every data type, I answered “No”<\/strong> to:\n
                  \n
                • Is this data used to track the user?<\/li>\n\n\n\n
                • Is this data linked to the user’s identity?<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

                  Since there is no user account or server, the data is not linked to an identity.<\/p>\n\n\n\n

                  7. The iPad Screenshot Block<\/h2>\n\n\n\n

                  When I first tried to submit, App Store Connect demanded iPad screenshots. I hadn’t optimized the UI for iPad yet.<\/p>\n\n\n\n

                  The Fix:<\/strong>
                  I changed the TARGETED_DEVICE_FAMILY<\/code> in Xcode Build Settings from 1,2<\/code> (iPhone, iPad) to just 1<\/code> (iPhone). This removed the requirement for iPad screenshots and allowed me to submit an iPhone-only app.<\/p>\n\n\n\n

                  \n\n\n\n

                  Conclusion<\/h3>\n\n\n\n

                  Submitting an app is less about code and more about configuration and compliance. By automating my screenshots and understanding the nuances of Apple’s privacy questionnaire, I was able to move from a “Processing” build to “Ready for Sale” smoothly.<\/p>\n\n\n\n

                  PaisaFlow<\/strong> is now live. If you are looking for a privacy-first way to track expenses, give it a try!<\/p>\n","protected":false},"excerpt":{"rendered":"

                  Building an iOS app is hard work, but submitting it to the App Store can feel like a whole different battle. Recently, I went through the process of publishing PaisaFlow,…<\/p>\n","protected":false},"author":1,"featured_media":146,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[8],"tags":[],"class_list":["post-57","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-learn-with-me"],"jetpack_featured_media_url":"https:\/\/balamurali.in\/blog\/wp-content\/uploads\/2026\/02\/ios_app_publishing.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/posts\/57","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/comments?post=57"}],"version-history":[{"count":1,"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/posts\/57\/revisions"}],"predecessor-version":[{"id":59,"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/posts\/57\/revisions\/59"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/media\/146"}],"wp:attachment":[{"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/media?parent=57"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/categories?post=57"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/balamurali.in\/blog\/wp-json\/wp\/v2\/tags?post=57"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}