Error during iOS build using ionic package Ionic V2


“Cannot parse Null or zero-data
Error reading file: provisioning.plist”

This is the error I was getting when I tried building the app for iOS using ionic package. Can someone tell me what the problem is? I have added all certificates and the right password for the .p12 certificate.


What is your ionic info output?


I have the same issue (since friday I cannot build --prod) my ionic info is

cli packages: (C:\Users\z\AppData\Roaming\npm\node_modules)

    @ionic/cli-utils  : 1.18.0
    ionic (Ionic CLI) : 3.18.0

global packages:

    cordova (Cordova CLI) : not installed

local packages:

    @ionic/app-scripts : 3.0.0
    Cordova Platforms  : android 6.2.3
    Ionic Framework    : ionic-angular 3.7.1


    Node : v6.11.0
    npm  : 3.10.10
    OS   : Windows 10

Environment Variables:

    ANDROID_HOME : not set


    backend : pro


What command are you using to build?
Your backend seems to be “pro”, where ionic package doesn’t even exist. So I don’t think you have the same problem. You should create a new topic and actually include the command that is causing problems and the complete error message you are getting.


nope I was using standard cli ionic cordova android build --prod --release


Screenshot-2017-11-12 My Apps - Ionic build amazing mobile apps faster than ever before

This is my output. I still have a legacy account which I am using for builds.


Trouble is ionic team has quietly released the major update that uses Angular 5.0 and even 2 weeks old projects are no longer legit to be built with the latest CLI. I have just started a new project Ionic start and everything works just fine.
People struggling with the build deserve a simple blogpost !


So do I have to setup my project again in order to properly build it?


What is the exact command you are using to build your app that is giving you this error?
What is your ionic info output?


ionic package build ios --profile PROFILE_TAG --release


So this has nothing to do with Ionic Native at all, I fixed the category of your post.


Is there any fix or solution to this?