PermissionsKit: App crashes in isAllowed method in SPPermission enum

Fatal error: SPPermission - Notification not import. See Readme: https://github.com/ivanvorobei/SPPermission: file /Users/*/<project name>/Carthage/Checkouts/SPPermission/Source/SPPermission/SPPermission.swift, line 89
(lldb) 

Same problem occurs on previous version (4.0), but is gone on version 3.1.1

Screen Shot 2019-06-14 at 13 44 21

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 34 (16 by maintainers)

Most upvoted comments

@ivanvorobei 4.0.5 doesn’t have this issue anymore, many thanks!

@ivanvorobei First off… that’s just an awesome response time!! Can’t tell you how much I appreciate that. Second, I need to do a better job of reading the README file! Sorry about that. I revised my podfile and now all seems to be well. 😃 Thank you!!

Yes, it still does have the same issue. Still has not been fixed. Not sure how good your English is, but you are not understanding what I am saying. It is still regularly crashing on line 131 of the pod file with a fatal error related to the location services request. If you can’t explain why this is happening, I’m just going to go back to using normal permission requests, because that was working just fine. This is still very broken. I am happy to work with you, but claiming it is fixed, when it is clearly crashing in the same place and it is no better than before does not help me. The app I’m building needs to use location always or when in use, and to be able present SPPermissin prompt inside of a UIPageController, to work correctly, and that is where this keeps crashing. Please fix ASAP or at least tell me how to run it without crashing when inside of a UIPageController. I need a working code example at this point using a UIPageController for the root VC, as nothing I have tried is working using the based code. Thank you!

Spencer Koltun

On Jun 17, 2019, at 12:50 AM, Roman Kyslyy notifications@github.com wrote:

@ivanvorobei 4.0.5 doesn’t have this issue anymore, many thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.