Open halmueller opened 2 years ago
How did you end up solving this?
The last time I looked at the project, it was still unsolved. It’s a mildly scary warning for whoever uploads the build, but nothing more than that. It might at some point in the future become an actual blocking error, though. A careful audit of the JS framework files and defaults would probably catch it.
Uploading a new iOS build generates this warning email from App Store Connect:
We aren't using push notifications. But something in the app is registering for them, and the Apple automatic validator is (correctly) flagging it as nonsensical behavior. You can't use push notifications if you haven't requested the entitlement.
The fix is to remove the registration, not to claim a pointless entitlement. From preliminary research, it might be coming from Firebase, or some other Cocoapod.
Relevant discussion threads: