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

DevHome SSH widget crashes #3888

Closed
lfiorini opened this issue Sep 20, 2024 · 2 comments · Fixed by #3895
Closed

DevHome SSH widget crashes #3888

lfiorini opened this issue Sep 20, 2024 · 2 comments · Fixed by #3895
Labels
Area-Widgets Related to in-package widgets Issue-Bug Something isn't working or needs investigation Priority-0 Bug that's considered release-blocking Resolution-Fix-Available Available in a release

Comments

@lfiorini
Copy link

Dev Home version

0.1801.625.0

Windows build number

10.0.22631.4169

Other software

No response

Steps to reproduce the bug

Click on an ssh item in the SSH keychain widget

Expected result

Open the window to connect

Actual result

It aits few seconds then the screen flash as if it tries to open the window.
These are the last lines in the log:

[2024/09/20 09:52:09.689 FTL] (DevHome) Unhandled exception: Error reading JObject from JsonReader. Current JsonReader item is not an object: String. Path '', line 1, position 16.
Newtonsoft.Json.JsonReaderException: Error reading JObject from JsonReader. Current JsonReader item is not an object: String. Path '', line 1, position 16.
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
at DevHome.Dashboard.ViewModels.WidgetViewModel.MergeJsonData(String jsonStringA, String jsonStringB)
at DevHome.Dashboard.ViewModels.WidgetViewModel.HandleAdaptiveAction(RenderedAdaptiveCard sender, AdaptiveActionEventArgs args)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at Microsoft.UI.Dispatching.DispatcherQueueSynchronizationContext.<>c__DisplayClass2_0.b__0()

Included System Information

No response

Included Extensions Information

No response

@lfiorini lfiorini added the Issue-Bug Something isn't working or needs investigation label Sep 20, 2024
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label Sep 20, 2024
@krschau krschau added the Area-Widgets Related to in-package widgets label Sep 23, 2024
@krschau krschau added Priority-0 Bug that's considered release-blocking and removed Needs-Triage New issue that the core contributors need to triage labels Sep 24, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Sep 27, 2024
@krschau krschau added Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release and removed In-PR This issue has a related PR labels Sep 27, 2024
@krschau krschau closed this as completed Sep 27, 2024
@lfiorini
Copy link
Author

lfiorini commented Oct 3, 2024

Version 0.1801.640.0 has fixed the issue. Many thanks,

@krschau krschau added this to the Dev Home v0.18 milestone Oct 3, 2024
@krschau krschau added Resolution-Fix-Available Available in a release and removed Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release labels Oct 3, 2024
@github-staff github-staff deleted a comment from SAMBILI Oct 28, 2024
@github-staff github-staff deleted a comment from SAMBILI Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Widgets Related to in-package widgets Issue-Bug Something isn't working or needs investigation Priority-0 Bug that's considered release-blocking Resolution-Fix-Available Available in a release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants