Requesting activity recognition permission doesn't prompt for any permission in iOS devices.
Like in Android devices, iOS devices should have asked for activity recognition permission with a dialog. Permission status is always undetermined when requesting.
var status = await Permission.activityRecognition.request();
// check value of status. It's always coming PermissionStatus.undetermined.
// No prompt in iOS device
// Only works with Android device
pubspec.lock
...
permission_handler:
dependency: "direct main"
description:
name: permission_handler
url: "https://pub.dartlang.org"
source: hosted
version: "5.0.1+1"
permission_handler_platform_interface:
dependency: transitive
description:
name: permission_handler_platform_interface
url: "https://pub.dartlang.org"
source: hosted
version: "2.0.1"
...
Platform:
Same error here, under the same conditions.
Same issue here
Hi,
It seems like this has yet to be implemented for iOS.
Since someone has already opened a proposal here I am going to close this issue.
Hi,
It seems like this has yet to be implemented for iOS.
Since someone has already opened a proposal here I am going to close this issue.
You should not have closed this issue as this issue is created earlier than #430. Furthermore, this issue is following proper guidelines for reporting issues such as reproduction steps.
Agreed.
My motivation to close this issue was because of the fact that this issue is not a bug but rather a feature request. Information about this not working on iOS is documented.
/// When running on Android Q and above: Activity Recognition
/// When running on Android < Q: Nothing
/// iOS: Nothing
But I agree with your reasoning to reopen this case!
thanks for clarifying
I am using Permission.sensors instead of Permission.activityRecognition for iOS and it works fine.
Hi @bikcrum, as mentioned before the activityRecognition permission is for Android only, the sensors permission is indeed the iOS equivalent of the activityRecognition. more information about the sensors permission on iOS can be found here. I will close this issue now, if you still have questions please let us know!
Most helpful comment
Agreed.
My motivation to close this issue was because of the fact that this issue is not a bug but rather a feature request. Information about this not working on iOS is documented.
But I agree with your reasoning to reopen this case!
thanks for clarifying