- name: scrcpy-buddy
- description: A simple, clean, minimalist GUI for scrcpy ( GitHub - Genymobile/scrcpy: Display and control your Android device · GitHub )
- snapcraft: scrcpy_buddy/snap/snapcraft.yaml at main · Codertainment/scrcpy_buddy · GitHub
- upstream: https://gitlab.com/brlin/scrcpy-runtime-snaps
- upstream-relation: None. Related to thread here: Classic confinement request: scrcpy-buddy
- interfaces:
- content[scrcpy-runtime-2404]:
- request-type: auto-connection
- reasoning: As scrcpy-buddy is a GUI wrapper for scrcpy, the auto-connection is needed so that the GUI can use scrcpy CLI.
- content[scrcpy-runtime-2404]:
This request has been added to the queue for review by the @reviewers team.
Hello @shripal17!
Given the snap functionality, the request makes sense to me, so +1 (#voteFor) for granting the scrcpy-runtime-2404 interface to scrcpy-buddy!
Thanks for your vote @yomonokio!
How long do we wait for the voting to complete?
Also, do I need to separately request human review of my snap app (version 1.0.6)?
Hello @shripal17!
Given the granting of the very similar request: Content[scrcpy-runtime-2404] auto-connection request for the scrcpy snap, this is also a +1 (#voteFor) from me for granting auto-connect of the content interface scrcpy-runtime-2404 for the scrcpy-buddy snap.
Apologies for the extended wait on this request!
I have approved the latest revision to grant usage of the specified dbus name(this was the human review needed failure you were seeing). Please let me know if you experience any more issues with new revisions.
In addition, +2 votes for, 0 votes against, granting auto-connect of content interface scrcpy-runtime-2404 to snap scrcpy-buddy. This is now live!
It is important for you to note that in these cases, the addition of a content plug auto-connect overrides the default behaviour of all other content plugs in use for this snap (ex: ffmpeg-2404, gtk-3-themes).
What this means for you:
- I have granted individual auto-connect for each of the
content plugsalready in yoursnapcraft.yamlto retain current functionality - Going forward, if you add any new
content plugsto this snap they will not auto-connect by default, you will need to create a new post in this forum requesting auto-connection. If you link this post for context there should be no issues.
These types of content interface grants can be a bit complex, so please reach out if you experience any issues.
Mega thanks!
Minor follow-up question:
If I update the snap with some new features (keeping current snapcraft the same), will it again require human review? ![]()
It shouldn’t require human review again, the dbus grant should persist through new revisions. If you do get blocked, let me know and I will investigate.