Handling Privacy Manifest Requirements with Outdated Firebase and Angular Version

Discussão em 'Angular' iniciado por MadMac, Fevereiro 14, 2025.

  1. MadMac

    MadMac Guest

    I’ve been caught off guard by the new privacy manifest requirements, which are asking for 11 declarations—mostly related to Firebase.

    Obviously missed the memo, I don't remember any communication from Apple. I released updates to existing apps in December with no issues. This is a new app release. Unfortunately, my app is somewhat outdated, as I haven’t had time to update all the dependencies. I’m currently using:

    • Ionic 5
    • Capacitor 5.0.0
    • Angular 12
    • Firebase 8.2.5
    • AngularFire 6.1.5

    I see two possible options:


    1. Upgrade to Firebase 10.22.0, which includes the privacy manifest. However, this would also require upgrading to AngularFire 16.0.0 and Angular 16, introducing a large number of breaking changes that could be difficult to manage in a short time frame. Not to mention having to retest everything as we just completed testing.


    2. Manually create a privacy manifest or use a tool to generate one. Would it be possible to copy the Firebase 10.22.0 manifest contents into my own manually created file? This would be the ideal interim solution due to the time constraint and I could update the packages after the release to the store.

    I’m on a tight deadline and have very limited time to resolve this. Any advice would be greatly appreciated!

    Continue reading...

Compartilhe esta Página