Back to rankings

Base44 Auto-Generates iOS Permission Strings to Cut App Store Rejections

Base44View original changelog

Base44 now automatically generates and localizes iOS permission usage descriptions for every native app build, addressing a long-standing pain point where Apple rejected Base44-built apps under Guideline 5.1.1 for missing or generic purpose strings. Builds now always include the required reasons, written in the app's own language, so developers no longer hit App Store rejections for this specific issue.

Key Takeaways

  • Base44 iOS builds now always include Apple's required permission usage descriptions, generated automatically from what the app actually does.
  • Purpose strings are localized into the app's own language, not just generated in English.
  • The change directly addresses Guideline 5.1.1(ii) rejections, previously a hard blocker with no workaround in the Base44 interface.
  • This was a critical, user-reported issue on Base44's public feedback board before being fixed.
  • Developers publishing native apps no longer need to manually edit Info.plist to pass this specific review step.
  • The fix reduces rejection-driven delays for any team taking a Base44 app from build to live App Store listing.

Closing a Recurring App Store Rejection Gap

Base44 addressed one of the most requested fixes from developers publishing native iOS apps: App Store rejections caused by missing or generic permission usage descriptions (the strings shown to users when an app requests access to location, camera, contacts, and similar protected resources). Apple's Guideline 5.1.1(ii) requires every purpose string to clearly and specifically explain why an app needs a given permission, and Base44's builds previously used a generic, non-editable string that frequently failed this review.

What Changed

iOS builds now always include the permission usage descriptions Apple requires, with the reasons generated automatically based on what the app actually does, and localized into the app's own language. Developers no longer need to manually edit Info.plist or work around a hard blocker just to get past App Store review for this reason.

Why It Matters

This had been tracked as a critical, user-reported blocker on Base44's own feedback board, since apps that couldn't clear 5.1.1(ii) simply could not ship to the App Store at all. For any team using Base44 to build and publish native mobile apps, this removes a recurring source of rejection and delay in getting an app live, without requiring developers to understand Apple's purpose-string requirements themselves.