appium / appium/appium-flutter-driver
Unable to see some Android Native permission popups while running automation.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 539
- Forks
- 195
- Avg merge
- 1h 11m
- Merged PRs (30d)
- 4
Description
Prerequisite: External USB drive is connected to the mobile device and the automation scripts are running wireless.
Description: I'm running an flutter debug android mobile application which needs some native OS permissions to perform some operations to the connected USB drive.
Test Environment:
- Java 11 (temurin)
- Appium: 2.1.3
- java-client: 8.4.0
- flutter@2.1.0 [installed (npm)]
- uiautomator2@2.29.11 [installed (npm)]
- Google Pixel 7 Pro (14.0)
Prerequisite: User is connected an external USB drive to the Mobile.
Steps followed:
- Initially user will be in FLUTTER context.
- Perform some click operation on flutter elements in the FTUE screens.
- After FTUE screens, user will redirect to android settings permission screen.
- Switch to NATIVE_APP context and click on android native switch_widget button.
- Click OK button(
android:id/button2) element Xpath as per the logs.
Issue: The moment user click on the above button, a pop up(Usb Access) should display. Only while running the test scripts through appium the pop is not displayed.
Note: The same flow if you perform manually then the pop up is displayed without any issues.
Attached logs for both:
Please take a look on both logs and let me know if anything is needed.
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the attached Appium.log and Manual_ADB.log, then reproduce the flow on the listed Pixel 7 Pro and software versions. Trace the Flutter-to-NATIVE_APP transition and the click on android:id/button2; done means the USB Access popup appears during automation, or the driver limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, flutter, java, typescript
- Domain
- mobile, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100