Status Update
Comments
sa...@dinoz.mobi <sa...@dinoz.mobi> #2
you want Secure Shell to actually do the reconnect, or you want it to display a dialog for you to press "R"(reconnect) ?
yo...@uber.com <yo...@uber.com> #3
My personal preference would be autossh
behavior - just immediately reconnect. Alternatively, a hot-key to reconnect instantly would work. Currently, I have to refresh the page, and then navigate to the remote I want to connect to and hit enter. Would love for this to be quicker, since basically every time I have to reconnect, its because my laptop went to sleep or something.
bl...@grubhub.com <bl...@grubhub.com> #4
it sounds like the dialog isn't being shown which is an existing KI. you can press Enter ~ . to break the connection and force the reconnect dialog, then press R. no need to refresh the page.
pa...@gmail.com <pa...@gmail.com> #5
I used to receive the option to press "R" to refresh the page but this stopped working this morning. Refreshing manually has also stopped working, forcing me to close the Secure Shell window and open a new one.
[Deleted User] <[Deleted User]> #6
Raising this to P2 to try and get a response here. This is quite annoying having to close and reopen the Secure Shell window every time I close my laptop or lock my screen.
Edit: I don't have permission to raise this to a P2. I will ask the reporter to do so if they can...
ba...@careem.com <ba...@careem.com> #7
ad...@move.com <ad...@move.com> #9
[Deleted User] <[Deleted User]> #10
Is there any update on this? I have been facing the same issue
ly...@twitter.com <ly...@twitter.com> #11
Menu -> View -> "Reload This Page" works for me -
[Deleted User] <[Deleted User]> #12
[Deleted User] <[Deleted User]> #13
Still not reconnecting
[Deleted User] <[Deleted User]> #14
sorry, but that isn't a useful report. you need to describe your setup (OS & client version) and what you're actually doing.
de...@gmail.com <de...@gmail.com> #15
I've been experiencing this for the past-few weeks with the built-in Terminal app on ChromeOS, which I know is distinct from (but shares a lot of code with) the Secure Shell extension (problem is not present in the latter). Let me know if I should file a different bug for this (can't find a relevant tracker and this issue seems the most relevant...), but otherwise here's the report:
Platform: ChromeOS, Version 132.0.6834.154 (Official Build) (64-bit).
Application version: impossible to say -- the built-in Terminal app doesn't show up in the list of ChromeOS apps, and it's obviously not an extension. The "about" page doesn't give a version string.
Behavior: when my Chromebook goes idle (~10m), or after I close the lid or otherwise lost my SSH connection to the remote host, the window "freezes" (not responding to mouse/keyboard input), and there's no re-connection dialog. Normally there is a dialog with (R)econnect, (C)hoose another connection, and (E)xit options, but in the past few weeks this dialog no longer appears.
Expected behavior: the dialog should simply appear when it detects the SSH session has ended, as it did for years up until recently.
Workaround: pressing the obscure keycombo in this bug (Enter
, ~
, .
) causes the dialog to appear. Otherwise I need to close the window and start my session from scratch.
Other notes: I don't have this problem when using the Secure Shell extension (ID: iodihamcpbpeioajjeobimgagajmlibd, version: 0.68), but it's more cumbersome than the built-in Terminal (doesn't support tabs, much slower to redraw the screen and reflow text).
[Deleted User] <[Deleted User]> #16
as noted above, the change is not in R132, and we aren't backporting it. please retest with R133.
ap...@strava.com <ap...@strava.com> #17
Amendment to
ri...@gmail.com <ri...@gmail.com> #18
pi...@gmail.com <pi...@gmail.com> #19
I am facing the same issue. The "obscure keycombo" workaround from
ju...@upkeep.com <ju...@upkeep.com> #20
please review
ch...@priceline.com <ch...@priceline.com> #21
[Deleted User] <[Deleted User]> #22
ju...@gmail.com <ju...@gmail.com> #23
[Deleted User] <[Deleted User]> #24
co...@zen.ly <co...@zen.ly> #25
[Deleted User] <[Deleted User]> #26
ah...@google.com <ah...@google.com> #27
ry...@spothero.com <ry...@spothero.com> #28
[Deleted User] <[Deleted User]> #29
se...@gmail.com <se...@gmail.com> #30
[Deleted User] <[Deleted User]> #31
da...@gmail.com <da...@gmail.com> #32
[Deleted User] <[Deleted User]> #33
[Deleted User] <[Deleted User]> #34
vj...@gmail.com <vj...@gmail.com> #35
da...@gmail.com <da...@gmail.com> #36
ry...@gmail.com <ry...@gmail.com> #38
ra...@gmail.com <ra...@gmail.com> #39
Porque no funcionan las apps de conductor de beat y bolt????
[Deleted User] <[Deleted User]> #40
th...@gmail.com <th...@gmail.com> #41
at com.google.maps.api.android.lib6.gmm6.vector.ct.<init>(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):9)
at com.google.maps.api.android.lib6.gmm6.vector.cv.a(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):23)
at com.google.maps.api.android.lib6.gmm6.util.m.run(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):14)
at java.lang.Thread.run(Thread.java:764)
Description
# It is OK to share your API Project ID, but _not_ API keys.
The Google Maps SDK is currently crash with the following stack trace:
Fatal Exception: java.lang.ArrayIndexOutOfBoundsException: length=1; index=12
at com.google.maps.api.android.lib6.gmm6.vector.ct.<init>(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):9)
at com.google.maps.api.android.lib6.gmm6.vector.cv.a(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):23)
at com.google.maps.api.android.lib6.gmm6.util.m.run(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):14)
at java.lang.Thread.run(Thread.java:764)
What steps will reproduce the problem?
1. Appears to be related to the size of the map view. Small map views render fine, however opening a large map view freezes then crashes the app.
Issue started appearing at ~11:30AM PST April 23rd, 2020.
Also add the following details:
- Device (and version of Android) you have verified this issue on:
- Google Play Services client library version:
- Google Play Services version on the device:
- Android SDK Version:
- Was this working correctly on a previous version of Google Play Services?
(If yes, which client library and SDK version?)
Also attach screenshots, sample code and optionally an APK if possible.
If the problem exhibits itself in a released version of your app on the
Play Store, optionally provide a link to the app, and explain how to
reproduce the issue in the app.