[permission_handler] Remaining issues about plugins

[bbrto21]

on tw3 binary I got a below error, but on R840, it is fine too

W/AUL     ( 4667): launch.c: app_request_to_launchpad_for_uid(266) > request cmd(0) result : -13
E/CAPI_APPFW_APP_CONTROL( 4667): app_control.c: app_control_error(438) > [__launch_request_send] APP_NOT_FOUND(0xfef00021)

[bbrto21]

@bbrto21 I'm still getting an error when running the integration test on wearable 5.5 emulator.

Failure Details:
Failure in method: open app settings
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
The following TestFailure object was thrown running a test:
  Expected: <true>
  Actual: <false>

When the exception was thrown, this was the stack:
#4      main.<anonymous closure> (file:///home/swift/Git/plugins/packages/permission_handler/example/integration_test/permission_handler_test.dart:22:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

This was caught by the test expectation on the following line:
  file:///home/swift/Git/plugins/packages/permission_handler/example/integration_test/permission_handler_test.dart line 22
The test description was:
  open app settings
═════════════════════════════════════════════════════════════════

end of failure 1

According to my investigation, the setting app on tw3 and on wearable emulator are not ready for a launch operation of app control. Therefore, at least in Tizen 6.0 or in lower, this function cannot be used.(I've asked to review this issue.)
But on the other hand, I found that instead of showing the system settings, the app can show the own permissions view on Galaxy watch. please see this PR.

[bbrto21]

openAppSettings() always returns false (APP_NOT_FOUND)

It seems to work fine on mobile. could you tell me details?

[swift-kim]

@bbrto21 Does it? I had only tested on watch devices.

[bbrto21]

W/AUL ( 4667): launch.c: app_request_to_launchpad_for_uid(266) > request cmd(0) result : -13

I guess it means permission denied, but I still confused

[swift-kim]

Yeah I also found it strange when I was testing the plugin before publishing.

[swift-kim]

@bbrto21 I'm still getting an error when running the integration test on wearable 5.5 emulator.

Failure Details:
Failure in method: open app settings
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
The following TestFailure object was thrown running a test:
  Expected: <true>
  Actual: <false>

When the exception was thrown, this was the stack:
#4      main.<anonymous closure> (file:///home/swift/Git/plugins/packages/permission_handler/example/integration_test/permission_handler_test.dart:22:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

This was caught by the test expectation on the following line:
  file:///home/swift/Git/plugins/packages/permission_handler/example/integration_test/permission_handler_test.dart line 22
The test description was:
  open app settings
═════════════════════════════════════════════════════════════════

end of failure 1