Problem

After upgrading to Capacitor 4 everything worked fine when buidling using ionic cap sync (I am using Ionic Framework) and worked fine in Xcode and iOS. However, when building in Android Studio I got this error:

:capacitor-cordova-android-plugins:processDebugManifest
Manifest merger failed with multiple errors, see logs

Solution

The error message does not give much of a hint but after lots of trials, I found out that one of my Cordova plugins was the cause. In my case it was onesignal-cordova-plugin that was on version 2.11.4 and needed to be upgraded to version 3. So a simple npm i onesignal-cordova-plugin@3 solved this problem for me.

Did this solution help you?

I hope this helped! Please comment if it did, or if you had any problem with it. Also let me know if you got it working (or not) using other versions or if you found a better solution – it will help me and others!

Problem with Capacitor logging

Capacitor only logs to the Xcode console (or Safari console) but not to the iOS device console (aka the native log), for example from your Capacitor plugins or Cordova plugins, or console.log and console.debug statements in your code.

Having the debug log in Xcode or Safari only is fine when debugging during development or in Testflight. But once your app is published to the AppStore and has some specific error that does not show in dev or Testflight, you need to have log write to the iOS device log, which can be read by console.app on your Mac.

Solution

There is a Capacitor feature request regarding this but if you don’t want to wait for that, this is how to quickly fix it in your project:

1. Open the file capacitor/ios/Capacitor/Capacitor/CAPLog.swift either from your favourite editor or directly in Xcode.
2. Comment out the line starting with Swift.print
3. Instead add the line: NSLog(String(describing: item))

public class CAPLog {
    public static var enableLogging: Bool = true

    public static func print(_ items: Any..., separator: String = " ", terminator: String = "\n") {
        if enableLogging {
            for (itemIndex, item) in items.enumerated() {
                //Swift.print("\(item)".prefix(4068), terminator: itemIndex == items.count - 1 ? terminator : separator)
                NSLog(String(describing: item))
            }
        }
    }
}

Now you are ready to build and upload to Apple App Store. Once approved by Apple, start debugging your production build in console.app.

This was tested using Capacitor 3.6.0 / @capacitor/ios 3.6.0 (on an Ionic Framework 6 project)

Note on performance

Swift.print is a more resource effective, but also more limited, way of logging. I doubt that this has much practical impact, but this is something to consider, you may want to revert back to Swift.print after you’re done debugging.

Note on logging

I used NSLog but there are also other ways to use logging that you may want to look into. For example Logger and Apple’s concept of Universal logging / Unified logging system.

Did this solution help you?

I hope this helped! Please comment if it did, or if you had any problem with it. Also let me know if you got it working (or not) using other versions or if you found a better solution – it will help me and others!

Background – pre Xcode 11 / Xcode 12

Before Xcode 11 the “normal” way to auto increment build number was to read current build number from Info.plist using the MacOS PlistBuddy tool and then increment that number and write the updated build number back to Info.plist, again using PlistBuddy. Or you could use avgtool or some 3rd party solution.

However, with Xcode11 (and currently Xcode12) version number and buildnumber are set in the pbxproj file, and Info.plist only reference what is set in pbxproj.

This change got my old script to generate an error on build: Command PhaseScriptExecution failed with a nonzero exit code

$(CURRENT_PROJECT_VERSION) + 1: syntax error: operand expected (error token is "$(CURRENT_PROJECT_VERSION) + 1")
Command PhaseScriptExecution failed with a nonzero exit code

This is what Info.plist now looks like in Xcode11 / Xcode12, i.e. there is no longer an actual build number to read from Info.plist, only a reference to what is set in the pbxproj file.

<key>CFBundleShortVersionString</key> 
<string>$(MARKETING_VERSION)</string> 

<key>CFBundleVersion</key>
<string>$(CURRENT_PROJECT_VERSION)</string>

Solution for Xcode 11 / Xcode 12

So, in Xcode 11/12 we now need to update the pbxproj file instead of Info.plist.

Use this script to auto increment build number:

buildNumber=$(xcodebuild -showBuildSettings | grep CURRENT_PROJECT_VERSION | tr -d 'CURRENT_PROJECT_VERSION =')
buildNumber=`echo $buildNumber +1|bc`
xcrun agvtool new-version $buildNumber

To add the script in Xcode 12, follow these steps:

1. Select your Project Target (Target, not Project)
2. Select Build Phases
3. Add a new Build Phase by clicking the plus (+) icon on top left
4. If you wish you can rename the new Build phase, e.g. Set Build Number
5. Copy the script above and paste it
6. You can leave all other Build Phase settings as default
7. Done – Build your project and watch build number increment with 1 for each build

This was latest tested on Xcode 12.5 and macOS Big Sur 11.5.2 on a MacBook Air M1

Did this solution help you?

I hope this helped! Please comment if it did, or if you had any problem with it. Also let me know if you got it working (or not) using other versions or if you found a better solution – it will help me and others!

The answer is CFBundleDevelopmentRegion set in info.plist

It seems CFBundleDevelopmentRegion is always set to en_US by default (or maybe this is because I build on a laptop that has these settings) thus showing context menus, file upload dialog etc in English.

I found that setting CFBundleDevelopmentRegion to empty uses device settings for language.

It seems making the change directly in Xcode does not work for some reason.

Put this in your config.xml ios section.

<platform name="ios">
   <config-file parent="CFBundleDevelopmentRegion" target="*-Info.plist">
        <array>
            <string />
        </array>
    </config-file>
</platform>

Note that some plugins seem to set language, so if you cannot get this to work, check your plugins. This was tested in Ionic 5 / Angular / Cordova.

Thanks to Maximillion Bartango on SO for putting me on the right track.

Please comment if this worked for you or if you have problems or other solutions.

It is aimed for our customers, who are mainly non-developers, on the steps for first time setup Apple Developer and App Store Connect for us to be able to sign and upload apps that we have developed for them. But it should be usable for any non-developer or developer in that same situation.

https://www.mobilapp.nu/2020/02/12/tutorial-add-your-app-to-apple-app-store-preparations-for-non-developers/

All this is probably too new for it to be any good tutorials or examples available, at least I could not find any and I spent quite some time looking. I also spent quite a few hours getting it to work, but here it is:

Solution

I used the plugin cordova-plugin-apple-login (version 1.0.0) so go ahead and install it using:

npm i cordova-plugin-apple-login
ionic cordova plugin add cordova-plugin-apple-login

Note that there is no Ionic Native wrapper for the plugin, so you have to declare it instead of importing it on your page:

declare var SignInWithApple: any;

This is the login function:

 loginWithApple() {

    SignInWithApple.request({requestedScopes: [ SignInWithApple.Scope.Email, SignInWithApple.Scope.FullName ]})
    .then((appleCredential) => {
      const credential =  new firebase.auth.OAuthProvider('apple.com').credential(appleCredential.identityToken);
      this.afAuth.auth.signInWithCredential(credential)
      .then((response) => {
        console.log('Login successful');
      })
      .catch((error) => {
        console.log(error);
        alert('error:' + JSON.stringify(error));
      });
    });

  }

This was done using Ionic 4 / Angular, AngularFire2 5.30 and the cordova-plugin-apple-login 1.0.0

Configuration

You also have to do some configurations…

-> Xcode: Add capability for Sign in with Apple
-> Apple Developer: Add Services id
-> Firebase console: Add Sign-in method for Apple, leave all fields blank if you only use on iOS

If you want to support Android and or Web / PWA, you will need to do some more configuring.

Did this solution help you?

Please comment if it did, or if you had a problem with it. Also if you got it working (or not) using other versions of plugins, frameworks etc or if you found a better solution – it will help others!

P.s. I also posted this solution to Stack Overflow (my first anwer there, yay!)

When trying to build (“ionic cordova build ios”) my Ionic Cordova project, I got this error: “Error: ENOENT: no such file or directory“.

Took me awhile to figure out since I had just copied the project from an older project, made a few changes etc. Turns out the cause was that I had used a slash (“/”) in the app name in config.xml, changing the name fixed the issue.

[code]Copying iOS template project to /xxx/platforms/ios
shell.js: internal error
Error: ENOENT: no such file or directory, rename ‘/xxx/platforms/ios/__TEMP__.xcodeproj’ -> ‘/xxx/platforms/ios/project/name.xcodeproj’
at Object.renameSync (fs.js:594:3)
at /xxx/node_modules/cordova-ios/node_modules/shelljs/src/mv.js:77:8
at Array.forEach (<anonymous>)
at Object._mv (/xxx/node_modules/cordova-ios/node_modules/shelljs/src/mv.js:53:11)
at Object.mv (/xxx/node_modules/cordova-ios/node_modules/shelljs/src/common.js:186:23)
at copyTemplateFiles (/xxx/node_modules/cordova-ios/bin/lib/create.js:124:11)
at Object.exports.createProject (/xxx/node_modules/cordova-ios/bin/lib/create.js:228:5)
at Api.createPlatform (/xxx/node_modules/cordova-ios/bin/templates/scripts/cordova/Api.js:122:14)
at /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/platform/addHelper.js:188:28
at _fulfilled (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:854:54
[ERROR] An error occurred while running subprocess cordova.
cordova platform add ios –verbose –save exited with exit code 1.
Re-running this command with the –verbose flag may provide more information. [/code]