IOS fails to start after upgrade to capacitor 5

Capacitor
1

After upgrading our project to Capacitor 5, our IOS app will not run on the simulator or on a device. It just gives a blank screen and WebProcessProxy errors in the output. It works fine on Android with no issues. Tested in IOS 16 and 13.

Any ideas or help on how to fix? Running out of ideas.

Using: Ionic 6, Angular 15, Capacitor 5, xCode 14.3.1
plugins for biometrics, push notifications, network, keyboard, camera and a few others.

Do not really have any code to show as this seems to happen at start up before it the code runs, does not even show the splashscreen. This is the output of the console from xCode IOS 16:

DiskCookieStorage changing policy from 2 to 0, cookie file: file:///Users/Library/Developer/CoreSimulator/Devices/9BE0203A-CCA7-4DE6-A729-F1BD298DFC50/data/Containers/Data/Application/92DA6A78-7339-4A0A-AB5E-D63E50485372/Library/Cookies/com.0000.0000.binarycookies
[Process] 0x118000400 - [PID=0] WebProcessProxy::requestTermination: reason=6
[Process] 0x118000400 - [PID=0] WebProcessProxy::processDidTerminateOrFailedToLaunch: reason=ExceededProcessCountLimit
[Process] 0x7fe007825020 - [pageProxyID=8, webPageID=9, PID=0] WebPageProxy::processDidTerminate: (pid 0), reason=ExceededProcessCountLimit
[Loading] 0x7fe007825020 - [pageProxyID=8, webPageID=9, PID=0] WebPageProxy::dispatchProcessDidTerminate: reason=ExceededProcessCountLimit
[Process] 0x118000000 - [PID=0] WebProcessProxy::requestTermination: reason=6
[Process] 0x118000000 - [PID=0] WebProcessProxy::processDidTerminateOrFailedToLaunch: reason=ExceededProcessCountLimit
…(keeps repeating)

2

In your Pods-App-Frameworks file (In xcode):

replace

  if [ -L "${source}" ]; then
    echo "Symlinked..."
    source="$(readlink "${source}")"
  fi

with:

  if [ -L "${source}" ]; then
    echo "Symlinked..."
    source="$(readlink -f "${source}")"
  fi

this is found in the following path:
…/ios/App/Pods/Target Support Files/Pods-App

3

Also add this to the end of your pod file and run pod install:

post_install do |installer|
  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
         end
    end
  end
end
4

Thanks for the info, we already had the first one on this branch, added this code and still got the error. Could it be something with FirebaseMessaging?

2023-09-10 20:47:29.547691-0400 App[91830:8969418] DiskCookieStorage changing policy from 2 to 0, cookie file: file:///Users/appledevices/Library/Developer/CoreSimulator/Devices/9BE0203A-CCA7-4DE6-A729-F1BD298DFC50/data/Containers/Data/Application/F1071C50-2084-428B-8E44-5AD3AE2F9F2D/Library/Cookies/com.0000.0000.binarycookies
2023-09-10 20:47:29.698502-0400 App[91830:8969699] 10.14.0 - [FirebaseMessaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you’d prefer to manually integrate Firebase Messaging, add “FirebaseAppDelegateProxyEnabled” to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
2023-09-10 20:47:50.891035-0400 App[91830:8969418] [Process] 0x114000400 - [PID=0] WebProcessProxy::requestTermination: reason=6
2023-09-10 20:47:50.898293-0400 App[91830:8969418] [Process] 0x114000400 - [PID=0] WebProcessProxy::processDidTerminateOrFailedToLaunch: reason=ExceededProcessCountLimit
2023-09-10 20:47:50.903853-0400 App[91830:8969418] [Process] 0x7fa4ea024c20 - [pageProxyID=8, webPageID=9, PID=0] WebPageProxy::processDidTerminate: (pid 0), reason=ExceededProcessCountLimit
2023-09-10 20:47:50.930640-0400 App[91830:8969418] [Loading] 0x7fa4ea024c20 - [pageProxyID=8, webPageID=9, PID=0] WebPageProxy::dispatchProcessDidTerminate: reason=ExceededProcessCountLimit

5

Figured out the issue., seems when we upgraded XCode changed the Launch screen settings in the general tab of the app to be the main storyboard. We updated to be the Launch screen storyboard, and everything worked as expected. Knew it had to be a s setting somewhere.

Thanks for your help.