Cairo Airport App

Cairo International Airport App is an application aimed at providing flight schedules to different countries with the ability to book tickets at discounted prices and take advantage of offers.
Fazkrony App

Fazkrony App is an application aimed at easy access to morning and evening supplications and all the essential supplications that Muslims need in their daily lives. It also allows users to perform daily tasbeeh easily.
Hajj Guide App

Hajj Guide App is an application aimed at understanding the rituals of Hajj and Umrah with simplified audio and visual explanations. It also helps you access most of the Kingdom’s services and everything you need during the Hajj and Umrah period, in addition to other services like prayer times and a compass.
Hassan App

Hassan App is an application aimed at making it easier to find technicians in various fields to fix any malfunction at home or work with the ability to track the technician and repair steps at the best competitive prices. You can also schedule and determine the appropriate times for the maintenance tasks to be carried out.
Enaba App

Enaba App is an application dedicated to performing Umrah on behalf of others. The app is designed for those who cannot perform the Umrah ritual for their deceased relatives, and it provides verified individuals to perform Umrah on their behalf at a nominal cost. The app also allows tracking the pilgrim on the map for reassurance.

Thursday,24 Sep 2026

Reasons for App Store Rejection: What We Encountered and How We Resolved It

Privacy and User Data Issues as Reasons for App Rejection

Apple places great importance on how apps collect, use, and share user data; consequently, failure to meet privacy requirements can lead to review delays or release rejection—particularly when an app collects information such as names, email addresses, phone numbers, location data, or data linked to app usage. Project owners must therefore have a clear understanding of the data their app collects and the reasons for doing so. It is also essential to ensure that the privacy policy clearly explains the types of data collected, the methods of collection and usage, and any third parties that may access the data when required. Apple requires a link to the privacy policy to be provided both within the app and in App Store Connect, alongside a clear explanation of data retention and deletion practices and the process for users to request the deletion of their data. Furthermore, developers must review analytics services, advertising platforms, and any third-party SDKs integrated into the app, as the developer bears responsibility for ensuring these components comply with Apple's guidelines.

Why might Apple reject an app due to payment and subscription issues?

Determining the in-app monetization strategy early in the planning phase is crucial because Apple enforces specific rules regarding digital purchases, subscriptions, and paid features. Issues can arise if an unsuitable payment method is used for a product or service that falls under the category of purchases requiring Apple’s own system. For instance, Apple’s guidelines mandate the use of "In-App Purchase" for unlocking digital features or functions—such as subscriptions, premium content, or the full version of an app—whenever the rule applies. Therefore, the nature of the items being sold must be defined before selecting a payment gateway, as the appropriate payment method for a real-world service differs from that used for digital content or functionality. It is also essential to ensure that products and subscriptions configured in App Store Connect appear correctly within the app and are accessible to reviewers; Apple requires in-app purchase flows to be fully implemented, up-to-date, visible, and testable upon submission. Common errors that complicate the review process include failing to clearly explain the monetization model or having discrepancies between the prices or subscriptions displayed in the app and those recorded in the store data. Consequently, the entire purchasing journey should be reviewed prior to submission to ensure clarity regarding pricing, subscription duration, and renewal or cancellation procedures where applicable. Furthermore, developers must test both successful and failed payment scenarios—rather than just successful transactions—to ensure the app clearly handles any issues that may arise during the process, thereby minimizing the likelihood of receiving payment-related feedback during the review.

Discrepancies between an app's description and its actual features can lead to issues during the review process.
One common error that triggers feedback during app review is a mismatch between the information on the App Store page and the actual in-app experience. For instance, the description might claim the app offers a specific function that the reviewer cannot find, or screenshots might display features absent from the submitted version. Similarly, the app's name or marketing copy might convey information that does not reflect the true user experience. Apple mandates that app details—such as descriptions, images, previews, and privacy information—must be accurate, up-to-date, and reflective of the core user experience. Therefore, before submission, you should review the app page as if you were unfamiliar with the project, comparing every piece of information against what the user can actually do within the submitted build. Screenshots must be updated if interfaces or features change; outdated images showing screens that no longer exist should be avoided. It is also crucial to avoid listing future features in the description as if they were currently available, as reviewers must be able to access the functions being described. New features should be specifically explained in the "Review Notes" when necessary; Apple requires that new features and changes be clearly detailed in these notes and accessible for review. Aligning the app with its store listing prior to submission helps identify minor inconsistencies that could otherwise result in review feedback. This practice also ensures a clearer page for the end user post-launch, aligning marketing information with the actual customer experience rather than presenting promises that cannot be fulfilled within the app.

In-App Account Deletion: A Key Factor in App Review

If an app allows users to create an account, providing a clear mechanism for account deletion is a crucial consideration when preparing the app for the Apple App Store. Since June 2022, Apple has required that apps supporting account creation enable users to initiate the deletion process directly within the app. Merely offering an option to temporarily deactivate the account is insufficient; there must be a clear path to delete both the account and its associated data in compliance with applicable requirements. Consequently, it is best to design this feature during the app analysis phase rather than adding it at the last minute before submission. It can be placed within account settings or in a prominent location that is easily accessible to the user without unnecessary steps. Furthermore, the process must specify what happens to the data following a deletion request and identify any data that must be retained due to legal obligations preventing immediate deletion. Information regarding deletion must align with the app's privacy policy. It is also essential to actually test the deletion process to ensure the request reaches the backend system and is handled as intended; simply placing a superficial button in the interface without actual implementation will not suffice. Testing confirmation and cancellation scenarios is equally important to prevent accidental account deletion. If external services are linked to the account, the handling of associated data must be reviewed in accordance with project requirements and applicable regulations. Ultimately, implementing a genuine and clear account deletion feature prior to submission helps avoid review delays while simultaneously giving users greater control over their data and accounts.