Skip to content

🧹 refactor: remove legacy fallback for device_time - #12

Closed
Dor-bl wants to merge 3 commits into
masterfrom
refactor/remove-device-time-fallback-15249938982603152128
Closed

🧹 refactor: remove legacy fallback for device_time#12
Dor-bl wants to merge 3 commits into
masterfrom
refactor/remove-device-time-fallback-15249938982603152128

Conversation

@Dor-bl

@Dor-bl Dor-bl commented Aug 10, 2026

Copy link
Copy Markdown
Owner

🎯 What: Removed the legacy fallback mechanism (try-except block handling UnknownMethodException) for retrieving device time in appium/webdriver/extensions/device_time.py, and updated associated tests. Cleaned up unused GET_DEVICE_TIME_GET and GET_DEVICE_TIME_POST endpoints.
💡 Why: To improve code maintainability and readability by phasing out outdated appium server fallback logic and consistently using direct mobile: getDeviceTime script executions, aligning with modern Appium standards.
Verification: Verified by running the full test suite (uv run pytest test/unit) and ruff linting checks to ensure code health is improved without behavioral regressions.
Result: A cleaner DeviceTime class and mobile command constant list, directly leveraging mobile: execute script behaviors without legacy overhead.


PR created automatically by Jules for task 15249938982603152128 started by @Dor-bl

Removes the legacy fallback mechanism in the `device_time` extension that relied on `UnknownMethodException` and `GET_DEVICE_TIME_GET` / `GET_DEVICE_TIME_POST` commands. It now directly uses `execute_script('mobile: getDeviceTime')`. Cleans up unneeded imports, constants, and the `CanRememberExtensionPresence` mixin. Updated the associated tests to remove obsolete HTTP mocks.
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Dor-bl added 2 commits August 10, 2026 07:26
Removes the legacy fallback mechanism in the `device_time` extension that relied on `UnknownMethodException` and `GET_DEVICE_TIME_GET` / `GET_DEVICE_TIME_POST` commands. It now directly uses `execute_script('mobile: getDeviceTime')`. Cleans up unneeded imports, constants, and the `CanRememberExtensionPresence` mixin. Updated the associated tests to remove obsolete HTTP mocks.

Additionally fixes CI failures by pinning the flutter test app urls to the 0.0.33 release.
Removes the legacy fallback mechanism in the `device_time` extension that relied on `UnknownMethodException` and `GET_DEVICE_TIME_GET` / `GET_DEVICE_TIME_POST` commands. It now directly uses `execute_script('mobile: getDeviceTime')`. Cleans up unneeded imports, constants, and the `CanRememberExtensionPresence` mixin. Updated the associated tests to remove obsolete HTTP mocks.

Additionally fixes CI failures by pinning the flutter test app urls to the 0.0.33 release and increasing `androidInstallTimeout` for flutter tests.
@Dor-bl Dor-bl closed this Aug 10, 2026

Dor-bl commented Aug 10, 2026

Copy link
Copy Markdown
Owner Author

Closing — no longer relevant against upstream (appium/python-client). Current upstream appium/webdriver/extensions/device_time.py already has zero UnknownMethodException/CanRememberExtensionPresence fallback logic — it already matches this PR's target state exactly. This was covered by upstream's legacy-fallback removal effort (#1267).


Generated by Claude Code

@google-labs-jules

Copy link
Copy Markdown

Closing — no longer relevant against upstream (appium/python-client). Current upstream appium/webdriver/extensions/device_time.py already has zero UnknownMethodException/CanRememberExtensionPresence fallback logic — it already matches this PR's target state exactly. This was covered by upstream's legacy-fallback removal effort (#1267).


Generated by Claude Code

Understood. Acknowledging that this work is now obsolete and stopping work on this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant