Hello Valentin,

I am sorry to hear you're experiencing issues with our assemblies.

I would like to ask you for more details on the reasons for App Store rejection - in general, adding the needed permissions to info.plist file of the iOS project should resolve the issue with App Store, here is an example with NSCalendar permission from our Telerik UI for Xamarin Examples application:

<key>NSCalendarsUsageDescription</key>
<string>Progress Telerik UI for Xamarin Examples Would Like to Access Your Calendar</string>

You can check the complete info.plist file on github here: https://github.com/telerik/telerik-xamarin-forms-samples/blob/master/QSF/QSF.iOS/Info.plist

I look forward to your reply.

Regards,
Yana
Progress Telerik

Hello Edward,

This was a change introduced by Apple a year ago - even though your app may not actually use the API, you will still need to add the purpose string because there is a static reference in the Telerik assemblies.  That's why the permission for RadCalendar is required in this case.

Indeed, splitting the common assembly will avoid adding the permission, still, I am afraid this task is not included in our immediate plans for the upcoming release. 

Keep in mind that even after adding the permission to the info.plist file,  if you're not using RadCalendar, you customers shouldn't be prompted to grant the access.

I am sorry for any inconvenience caused.

Regards,
Yana
Progress Telerik

Hello Letticia,

If you are not using the controls that require these descriptions, your customers should not be prompted to grant access to the calendar/photos when they install the actual application.