-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission Request Not Dispatching onSuccess()
on first attempt on iOS
#129
Comments
Same thing here. Seems to be an internal crash or stalling of the library - cause the app is not proceeding after |
@angelacassanelli I don't know if it's still relevant to you - but this is how I overcame the bug:
It seems like something is blocking the thread inside the library - so that's why it's not proceeding further. |
I'm facing a similar issue: code after |
Hi,
I'm developing a Kotlin Multiplatform project with native Google Maps integration. The location permission request works perfectly on Android but has issues on iOS.
Devices tested:
Issue:
When the location permission is requested on iOS in
viewDidLoad
ofMapsViewController
, the permission dialog is displayed: even if permission is granted by the user, theonSuccess()
event is not dispatched during the first attempt. If theMapsViewController
is reopened, permission is already granted, andonSuccess()
is correctly triggered.It seems that
permissionsController.providePermission(permission)
is being called in thePermissionViewModel
without any exceptions, buteventsDispatcher.dispatchEvent { onSuccess() }
is not executed.Expected behavior:
onSuccess()
should be dispatched immediately during the first open of theMapsViewController
.Current behavior:
onSuccess()
is only dispatched on subsequent opens of theMapsViewController
, after permissions have already been granted.Logs:
Relevant Code:
PermissionViewModel:
MapsViewController:
PermissionHandler:
Could you please help identify why
onSuccess()
is not dispatched on the first attempt?Thank you!
The text was updated successfully, but these errors were encountered: