Important tips for publishing apps to app store

Unlike Appeon Workspace which is unsupported to be published to online application stores, you can publish the standalone mobile apps to the online application store (such as Apple App Store, Google Play etc.).

After compiling the mobile application into an iOS IPA file or Android AAB/APK file, you may upload the IPA or AAB/APK file to the online application stores to get the app approved. But be aware that Apple and Google follow strict guidelines to review the app before they approve and post the app to their online application store, therefore this will introduce much more work when preparing the app for distribution. Especially for Apple who has much more stringent rules on the app distribution, you may want to carefully read the App Store Review Guidelines (you will need to log in first to view the page) and verify the app is in compliance with these guidelines, in order to speed up the app approval process.

Before the app is available for download from the online application store, Apple/Google will need to review its code and may reject it if Apple/Google considers it not comply with their standards, therefore, be prepared that you may need to adjust and re-package the app according to their requirements and the entire approval process may take up to one or two weeks.

The following lists the most common areas and reasons we have found so far that will cause the app to be rejected by Apple or Google.

  1. Check that if your app includes UI controls for quitting the app. For example, a button labeling "Quit", "Exit", etc. You'd better remove any mechanism for quitting the app, as this is not in compliance with the iOS Human Interface Guidelines, as required by the App Store Review Guidelines (you will need to log in first to view the page).

  2. Check that if your app appears to be for demonstration or trial purposes only. For example, "demo", "trial", "test" or "beta" is displayed on the app UI, app description or release notes. You'd better remove any these references and complete or fully configure any partially implemented features.

  3. Google Play will check the OpenSSL version used in any library of the package. The current version of OpenSSL used in the Appeon library files are 1.0.1q and 1.0.1s. If you receive any message from Google Play about the OpenSSL version used in the package, please contact our Appeon Support team for suggestions.

  4. Apple does not allow multiple versions of the same app published on Apple App Store, therefore, you probably have only one version of the app on Apple App Store, which means if you have more than one PowerServer of different versions, you will need to plan which version of the app should be uploaded to App Store because the app can only work with the PowerServer of the same version.