appium ios Recording the screen, the saved mp4 file cannot be opened
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- mobile-dev
Research direction
Start with the Python client entry points start_recording_screen and stop_recording_screen, then reproduce the iOS recording flow through tidevice on Windows using the provided options and save path. Check the Appium logs and recording_data handling; done means the saved recorded_video.mp4 can be opened successfully.
Written by the indexing model from the issue text.
Description
The problem
appium ios Recording the screen, the saved mp4 file cannot be opened
Environment
- Appium version (or git revision) that exhibits the issue:2.0.1
- Last Appium version that did not exhibit the issue (if applicable):
- Desktop OS/version used to run Appium: windows
- Node.js version (unless using Appium.app|exe):
- Mobile platform/version under test:ios
- Real device or emulator/simulator:device
- Appium CLI or Appium.app|exe:
Details
Use appium to connect tidevice to run in windows environment
The mp4 file saved by using the start_recording_screen method to record the screen cannot be opened
Link to Appium Logs
Create a GIST which is a paste of your full Appium logs, and link them here.
Code To reproduce issue
options = {
'videoQuality': 'low',
'timeLimit': 600,
}
self.driver.start_recording_screen(**options)
sleep(3)
recording_data = self.driver.stop_recording_screen()
with open(r'F:\recorded_video.mp4', 'wb') as file:
file.write(base64.b64decode(recording_data))
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 570
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 25
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from appium/python-client
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
appium/python-client#1230 · 1 comment ·
Maintainers usually reply within 1 day
-
question
Difficulty 4/5 3-5 days Newbie friendliness 25/100
appium/python-client#1168 · 9 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
appium/python-client#1147 · 7 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
appium/python-client#1091 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
appium/python-client#1076 · 2 comments ·
Maintainers usually reply within 1 day
All issues in appium/python-client
Similar issues
-
docs pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pydantic/pydantic-ai#8863 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
run-llama/llama_index#23278 ·
Maintainers usually reply within 2 days
-
documentation from-review-extraction github-actions priority: low severity:nit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
LearningCircuit/local-deep-research#6946 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
oracle/langchain-oracle#323 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
tenstorrent/tt-metal#58057 · 1 comment ·
Maintainers usually reply within 1 day