Not working with xcode 12.

3. While evaluating request SILGenWholeModuleRequest(SIL Generation for module AES__El__Salvador)
4. While emitting SIL for 'setupUI()' (at /Users/willygonzalez/Documents/iOS Projects/AESApp/AESApp/Helpers/PAPermissions/Classes/PAPermissionsTableViewCell.swift:63:5)
5. While silgen emitFunction SIL function "@$s17AES__El__Salvador26PAPermissionsTableViewCellC7setupUIyyF". for 'setupUI()' (at /Users/willygonzalez/Documents/iOS Projects/AESApp/AESApp/Helpers/PAPermissions/Classes/PAPermissionsTableViewCell.swift:63:5)

error: Segmentation fault: 11

So, my app uses PAPermissions to get all the approvals. If I use PAPermission's notifications settings, the didRegisterForRemoteNotificationsWithDeviceToken in AppDelegate is not called. It is getting called with regular Push notification setup.

Is there any other way to call the didRegisterForRemoteNotificationsWithDeviceToken from PAPermissions after the user allow? Or am I missing something that need to be implemented?

Thanks for any help.

When you have declined one of the permission Calendar, Motion, Photo or Notifications then you can't enable them anymore from the app. The other permissions will go to the settings screen like it should.

App will sometimes get rejected when using the PAPermissions library because of the use of prefs:root=

Your app uses the "prefs:root=" non-public URL scheme, which is a private entity. The use of non-public APIs is not permitted on the App Store because it can lead to a poor user experience should these APIs change.

In PAPermissionsTableViewCell, you have the following properties declared as weak:

weak var iconImageView: UIImageView!
weak var titleLabel: UILabel!
weak var detailsLabel: UILabel!
	
weak var permission: PAPermissionsItem!
	
fileprivate weak var rightDetailsContainer: UIView!
fileprivate weak var enableButton: UIButton!
fileprivate weak var checkingIndicator: UIActivityIndicatorView!

There is no circular reference from any of those properties back to PAPermissionsTableViewCell, so those should be regular / strong references. Otherwise, you run the risk of your instance of PAPermissionsTableViewCell outliving one of those items and since they are all declared as being implicitly-unwrapped optionals, you'll crash in that scenario.

For adding CloudKit discoverability permissions you could use this code. You do have to be aware that this is an async call.

        let container = CKContainer.default()
        container.status(forApplicationPermission: CKApplicationPermissions.userDiscoverability, completionHandler: { applicationPermissionStatus, error in
                 // handle applicationPermissionStatus for statuses like
                 // CKApplicationPermissionStatus.Granted, .Denied, .CouldNotComplete, .InitialState
        })


        let container = CKContainer.default()
        container.accountStatus(completionHandler: {status, error in
            switch status {
            case .available, .restricted:
                container.requestApplicationPermission(CKApplicationPermissions.userDiscoverability,  completionHandler: { applicationPermissionStatus, error in
                          // handle applicationPermissionStatus for statuses like CKApplicationPermissionStatus.Granted, .Denied, .CouldNotComplete, .InitialState
                })
            case .couldNotDetermine, .noAccount: break
                // Ask user to login to iCloud
            }
        })

This project does a lot of implicit and forced unwrapping of vars. That's generally discouraged in Swift since you lose the protection of explicitly handling optionality.

Also - several vars were declared as weak and were also being force-unwrapped. This semantically doesn't make sense because weak vars, by definition, aren't retained and therefore must be optional. Swift should have probably always thrown an error on this - but as of Swift 5.3 in Xcode 12 Beta, force-unwrapping a weak var will no longer compile (it crashes the compiler). This PR fixes that.

Hello Pasquale,

thanks for your fine library. I have added support for Media Library permission (done already last year) and want to suggest to add this to your repo, so that we are in sync for the future. The code is tested and running fine. Thanks,

I want to check a permission status before presenting the CustomPermissionsViewController, in case the permission is already ok. How would I do that? In Example Project/ViewController.swift, I tried let calendarCheck = PACalendarPermissionsCheck() print("\(calendarCheck.status)") but it always returns "checking".

Also I want to add MediaLibrary support. Which check class would you recommend to use as an template for that?

If I delete the unused check classes in my project, will this prevent the issue "Too many permissions for AppStore", please see https://github.com/nickoneill/PermissionScope/issues/194 I used PermissionScope in the past, but looking for a new solution as PermissionScope is not maintained anymore.

Thank you very much.

Anyone have any idea on why I would get these errors?

'shared' is unavailable: Use view controller based solutions where appropriate instead.

'openURL' is unavailable

Hi,

A little bug with Blur...

Replace this 'return self._blurEffectView as! UIVisualEffectView' by 'return self._blurEffectView as? UIVisualEffectView' line 144 in PaPermissionsView.swift

Hi,

I've found a little bug when user accept camera permission, the status button was not refreshing because the updateStatus method isn't called in authorization block. Do you agree ?