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

install_release.sh from release 2.1 installs wrong scrcpy-server version (2.0) #4121

Closed
2 tasks done
weisswieschwarz opened this issue Jun 27, 2023 · 2 comments
Closed
2 tasks done

Comments

@weisswieschwarz
Copy link

weisswieschwarz commented Jun 27, 2023

  • I have read the FAQ.
  • I have searched in existing issues.

Environment

  • OS: Debian 12
  • scrcpy version: 2.1
  • installation method: manual build from release 2.1
  • device model: irrelevant
  • Android version: irrelevant

Describe the bug
Installation prodecure with install_release.sh (release 2.1) downloads scrcpy-server 2.0. Resulting installation will not work due to mismatch between scrcpy (2.1) and scrcpy-server (2.0)

grep ^PREBUILT_SERVER_URL scrcpy-2.1/install_release.sh
PREBUILT_SERVER_URL=https://github.com/Genymobile/scrcpy/releases/download/v2.0/scrcpy-server-v2.0
scrcpy 2.1 <https://github.com/Genymobile/scrcpy>
scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 7.6 MB/s (52867 bytes in 0.007s)
[server] ERROR: Exception on thread Thread[main,5,main]
java.lang.IllegalArgumentException: The server version (2.0) does not match the client (2.1)
        at com.genymobile.scrcpy.Server.createOptions(Server.java:172)
        at com.genymobile.scrcpy.Server.main(Server.java:360)
        at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
        at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:355)
ERROR: Server connection failed

One workaround is to manually download scrcpy-server 2.1 from the release page but perhaps this could be fixed.

@rom1v
Copy link
Collaborator

rom1v commented Jun 27, 2023

Please read explanation in #4098.

You should not execute ./install_release.sh from tag v2.0, but one commit after (in practice, it is intended to be called from current master only).

@weisswieschwarz
Copy link
Author

Thanks for the explanation. Sorry I did not find that issue, I searched for issues including "2.1".

Will close this issue then.

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

No branches or pull requests

2 participants