Build

When developing iOS applications for iPhone/iPad, is it necessary to register to the iOS Developer Program?

Yes, normally it is necessary to register to the iOS Developer Program in order to develop iOS applications. Actually, in iOS app development, it is not necessary to register the Mac environment to the iOS Developer Program, but you need to register to the program in order to install the developed application on an actual device and make it run.

The application that was developed using Monaca does not function well on mobile device.

In this case, please run and check the application again after stopping all the applications running on the device.

I can't successfully build iOS (iPhone/iPad) applications.

When developing iOS applications, you need to follow the instructions provided by Apple. Register properly the information of the device and developer, and then prepare the necessary files. For a step-by-step guide, please refer to Building an iOS App.

I was able to build iOS (iPhone/iPad) apps before, but now I can't do it anymore.

This may caused by the expiry of certificates, reissuing certificates requirement or other factors. Therefore, you need to recreate the provisioning profiles. Please recreate the required files like certificates and provisioning profiles by using the same procedures as before, and then use the new files. You may read about Generate Certificates and Create Provisioning Profiles for more details.

The procedures can be found in Building an iOS App.

Can I build an application for only iPhone using Monaca?

You can build an application just for iPhone by setting the target device family in iOS App Settings. By default, iPhone, iPod touch and iPad is selected.

Can I develop Windows Store apps?

It is possible to develop a Windows Store app as a debug build. But in this case, you can't release the app in the Windows Store. (We will tackle this issue in the future.)

How to import/export private keys and certificates that are using Xcode?

You can import private keys on your local Mac and export Monaca's private keys and certificates. For details, please refer to Build Settings between Monaca and Xcode.

The built application crashes right after starting up.

The following reasons might cause the application to crash after starting up. Please double-check them and rebuild your application.

  • An inappropriate image may have been assigned to the splash screen.

  • There might be a description error in the MonacaApp-Info.plist in case of iOS or AndroidManifest.xml in case of Android.

  • Please check in particular if there is an error in the specified

    permission, especially whether the required permission settings have

    been made. For example: even though components/loader.js file is

    loaded, ACCESS_NETWORK_STATE cannot be accessed or in the case

    that application uses location information but

    ACCESS_COARSE_LOCATION is not permitted and so on.

Can I use Japanese for the app name?

You can use Japanese. Please set Japanese for the app name from Build Settings in Monaca Cloud IDE.

What kind of character string should be used for iOS App ID?

You can set it with your own preference; however, we recommend that the App ID is your own domain name but written in reverse. Please see our blog article (Japanese) for details.

During the iOS build, an internal server error (71) occurs.

This is an error that occurs when your App ID or application name contains one-byte space. Please recheck them again.

Can I share my iOS certificates and private key?

Yes, it is possible to share iOS private key and certificates among other users and environments. Please refer to Build Settings between Monaca and Xcode.

Can I share my Android KeyStore?

Yes, you can share your Android KeyStore. You can download your Android KeyStore from Monaca Cloud IDE. Please always back up and keep the KeyStore that is used to sign application(s) because when a KeyStore is lost, it is impossible to use the same key to re-sign a signed package.

Creating and exporting Android KeyStore is described in Configure Android KeyStore.

Last updated