FIX 1 : Generic resolution to repair PrivacyInfo.xcprivacy associated problem.
Replace your APIs based mostly on the supplied official URL:
Let’s take an instance of the API NSPrivacyAccessedAPICategoryActiveKeyboards within the file.
PrivacyInfo.xcprivacy
This API has solely two legitimate NSPrivacyAccessedAPITypeReasons:
3EC4.1 and 54BD.1
Now we have to make sure we use solely these underneath it. If we add another NSPrivacyAccessedAPITypeReasons, it is going to trigger a problem.
FIX 2 : Even when you have eliminated and corrected all NSPrivacyAccessedAPITypeReasons, In case you continue to face the identical points. This might be as a result of, on the time of pod set up, some dependencies add incorrect NSPrivacyAccessedAPITypeReasons. To repair this problem, add privacy_file_aggregation_enabled: false in your Podfile:
use_react_native!(
# Disables the aggregation of privateness info from dependencies to forestall them from including incorrect NSPrivacyAccessedAPITypeReasons
privacy_file_aggregation_enabled: false,
:path => config[:reactNativePath],
# An absolute path to your software root.
:app_path => "#{Pod::Config.occasion.installation_root}/.."
)