Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

addMedia causes crash on Android API 28 #1821

Open
1 task done
bartekpacia opened this issue Jul 23, 2024 · 1 comment
Open
1 task done

addMedia causes crash on Android API 28 #1821

bartekpacia opened this issue Jul 23, 2024 · 1 comment
Labels
bug Something isn't working maestro cli Related to the command-line Maestro tool P2 Important and valid issues not at the top of the work list platform: android Testing Android apps is affected

Comments

@bartekpacia
Copy link
Contributor

bartekpacia commented Jul 23, 2024

Is there an existing issue for this?

  • I have searched the existing issues and didn't find mine.

Steps to reproduce

  1. Clone example app

  2. Run Android emulator with API 28 (I used image system-images;android-28;google_apis;arm64-v8a)

  3. Run flow issue1821.yaml

    maestro test .maestro/issue1821.yaml
Flow file
appId: com.example.example
name: Issue 1821
---
- launchApp:
    clearState: true
- addMedia:
  - assets/image.png
- launchApp: com.android.documentsui

# Files app ID is:
# "com.android.documentsui" for API 29 and below
# "com.google.android.documentsui" for API 30 and above

Actual results

addMedia causes a crash and the flow fails.

Expected results

addMedia works and doesn't crash.

About app

n/a (does not matter in this context)

About environment

M1 MacBook Air, macOS 14.5 Sonoma

Logs

Logs
$ maestro test .maestro/issue1821.yaml
Running on emulator-5554
io.grpc.StatusRuntimeException: UNKNOWN
    at io.grpc.Status.asRuntimeException(Status.java:539)
    at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:487)
    at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:563)
    at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70)
    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:744)
    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:723)
    at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
    at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)


==== Debug output (logs & screenshots) ====

/Users/bartek/.maestro/tests/2024-07-23_123749

Maestro version

1.36.0

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

No response

@bartekpacia bartekpacia added maestro cli Related to the command-line Maestro tool platform: android Testing Android apps is affected bug Something isn't working labels Jul 23, 2024
@bartekpacia bartekpacia added the P2 Important and valid issues not at the top of the work list label Aug 15, 2024
@Aleksandriukas
Copy link

The same issue occurs with Android API levels below 29.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working maestro cli Related to the command-line Maestro tool P2 Important and valid issues not at the top of the work list platform: android Testing Android apps is affected
Projects
None yet
Development

No branches or pull requests

2 participants