4 Replies Latest reply on Apr 26, 2018 8:11 AM by Philip John

    MFi certification update process

    Philip John

      We're in the process of building an iOS app that is used across multiple construction sites. A very small part of the app is to print out a QR code to go on a delivered item. We've built the functionality to do the printing to a Zebra printer, but recognize that we need to be added to a Zebra Whitelist before we can include these changes in a submission to Apple.

       

      What's bothering me is that this does not appear to be a one-time process. According to the MFi FAQ we need to submit an update to Zebra for review every time we do a version update, regardless of how minor, or whether the code changes are in any way related to the print functionality.

       

      Am I correct in my assumption? Having a crucial bug fix held up while waiting for review at Zebra would be a big problem.

        • Re: MFi certification update process
          Steven Si

          Hi Philip,

           

          In theory, your understanding is correct according to the rules specified by Apple in MFi process. In practice, however, the update of an app does not need to be reviewed and registered again for MFi, if the App Name, Bundle ID, External Accessory Protocol(s) and Zebra printers used in the app remain unchanged in the update. If the App Name, Bundle ID or External Accessory Protocol(s) has changes or a new printer is added to the update, then we need to go through the MFi review, test and registration process. Hope this helps.

          • Re: MFi certification update process
            Philip John

            So if we do not change any of those parameters

             

            App Name, Bundle ID, External Accessory Protocol(s) and Zebra printers

             

            we do not need to submit the app to Zebra? Does Apple not check the version number with Zebra's list?

              • Re: MFi certification update process
                Steven Si

                In the MFi registration process, the version number is a required field by Apple. However, after the initial approval of an app, we've found that Apple is less stringent on the version number in the subsequent app updates. You can safely submit your app to Apple's App Store in the subsquent updates, as long as the above mentioned items remain the same in the updates. In case an Apple reviewer was picky on the version number (we've not seen this ever happened though), you can reach out to us for resolution. The turnaround time in this type of cases will be fast and usually in less than a day.