Replies: 1 comment 2 replies
-
Reposting this without mentioning the Ionic team, since I believe that is why my previous comment was marked as disruptive Since the Ionic team often struggles with communication (no shame, I'm sure there is a lot going on), I'll try to give a quick summary of where I believe things are at. I'm not on the Ionic team, so take all of this with a grain of salt, but this is what I've observed so far. In the past few days, three PRs have been merged to add the XCPrivacy manifest into #7330, #7322, and #7321. Last November, the Ionic team announced a new Capacitor Release Cadence, which boils down to: August-December: Prerelease of the next major update (6.x) Thankfully the changes were also merged into 4.x (maintenance?) and 5.x (current stable/latest), so we'll hopefully see a new 5.x version released within a week or two. Sadly this is cutting it close for a lot of teams, as Apple's latest announcement from February 29th said that warnings will start appearing on March 13th (yesterday) and it will be enforced on May 1st (6 weeks from now). I'd greatly appreciate some additional context from the Ionic team on when a new 5.x version will be released, as I have quite a few people breathing down my neck for when we'll have these issues resolved in our apps. |
Beta Was this translation helpful? Give feedback.
-
Apple has listed Capacitor on its list of 3rd party SDKs that will need to provide privacy info in order to be included in iOS apps:
https://developer.apple.com/support/third-party-SDK-requirements/
This is also the case for Cordova (see apache/cordova-ios#1391), so I just wanted to start a discussion about how this might be handled and whether Capacitor will require a similar or different approach than Cordova to handling this.
Beta Was this translation helpful? Give feedback.
All reactions