-
Notifications
You must be signed in to change notification settings - Fork 5
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
🐞 Bug - crew-launcher borked ("Add to launcher" button returns JS error in console on click) #15
Comments
@supechicken this is your wheelhouse... |
Updated crew to the latest update d4ed8038 and upgraded my chromebook to v116. Nothing has changed, although this may not be relevant. |
@supechicken, any potential solution to this issue? |
The command also dosent work for me |
This issue should also probably be transferred to the crew-launcher repo, right? |
The "Help needed?" section in the crew-launcher repo gives a link to the issues page on this repository. If we are supposed to report issues there, then the link must be updated to that repo. |
@supechicken, crew-launcher is largely your project, what do you think? |
I am okay with this... |
Describe the bug
When chrome-launcher add (package) is run, a chrome window pops up connecting to localhost. When the "Add to launcher" button is clicked, nothing happens.
To Reproduce
Steps to reproduce the behavior:
I executed this command:
Output (shell):
Output (console):
Expected behavior
A popup should've appeared prompting me to install the website/
Environment: Paste the output of
crew sysinfo -v
between the two***
belowExpand
Architecture:
x86_64
(x86_64
)Processor vendor:
GenuineIntel
User space:
64-bit
Chromebrew Kernel version:
5.4
Chromebrew Running in Container:
false
Chromebrew version:
1.35.6
Chromebrew prefix:
/usr/local
Chromebrew libdir:
/usr/local/lib64
Last update in local repository: f9a4fccf
Telegram 4.9.4 => 4.9.5 (#8616) (20 hours ago)
OS variant:
Chrome OS
OS version:
dedede-release/R116-15509.72.0
OS channel:
stable-channel
The text was updated successfully, but these errors were encountered: