Closed jakerockland closed 8 years ago
What issue do you have?
The pre-permission seems to always fire, even if the permission has already been authorized previously, is this correct behaviour? Perhaps I'm just a bit confused about the expected behaviour.
It definitely shouldn't fire indeed. I'm gonna look into it
That would be awesome, thanks so much for looking into it. If you have any issue re-creating the error I can try to send you some sample code of exactly how I am implementing the framework, but my implementation was pretty much just based on the sample documentation you gave but using the .Bluetooth permission.
@delba: Im seeing this too.
@AndrewSB I believe I found a fix to this if you check out #70. 😄
@AndrewSB did you had a change to try #70 ? I'm going to test it as well on my side :)
I'll test #70 later today! On Thu, Oct 20, 2016 at 8:18 AM Damien notifications@github.com wrote:
@AndrewSB https://github.com/AndrewSB did you had a change to try #70 https://github.com/delba/Permission/pull/70 ? I'm going to test it as well on my side :)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/delba/Permission/issues/36#issuecomment-255136942, or mute the thread https://github.com/notifications/unsubscribe-auth/ADo1dMvUB5BJSyVFakok2JKDHFlrSIVaks5q14YxgaJpZM4JDkMH .
This is now replaced with #74 for isolation from #69 @delba @AndrewSB
I'm having an issue using the pre-permission with the .Bluetooth Permission type. Does this have something to do with this line in Permission.swift
case .Bluetooth: requestBluetooth(self.callback)
?Still a bit new to Swift so not 100% sure what is wrong here.