Common: Split Telerik.Xamarin.iOS.dll into separate binary files
We should consider splitting the Telerik.Xamarin.iOS.dll into separate DLLs so that the customers can reference only the controls they need.
Posted on:16 Dec 2019 09:34
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.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items
Posted on:14 Dec 2019 05:23
After two years I'm trying to deploy an app that uses Telerik Xamarin framework, and I'm not using the calendar actually I'm using the RadListView and Apple rejected my app for the Calendar permissions. I added the correspond string to fix this.
Posted on:28 Nov 2017 08:08
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.
Posted on:27 Nov 2017 15:37
NSCalendarsUsageDescription and NSPhotoLibraryUsageDescription required when deploying to TestFlight even without using the resource.