You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/known-issues.md
+48-23Lines changed: 48 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
# Table of contents
2
2
3
3
-[macOS](#macos)
4
+
-['Apple could not verify this app is free of malware' error when launching the app](#apple-could-not-verify-this-app-is-free-of-malware-error-when-launching-the-app)
4
5
-['The username or passphrase you entered is not correct' error after signing into account](#the-username-or-passphrase-you-entered-is-not-correct-error-after-signing-into-account)
5
6
-[Checking for updates triggers a 'Could not create temporary directory: Permission denied' message](#checking-for-updates-triggers-a-could-not-create-temporary-directory-permission-denied-message)
6
7
-[Windows](#windows)
@@ -12,8 +13,10 @@
12
13
-[Failed to open CA file after an update](#failed-to-open-ca-file-after-an-update)
13
14
-[Authentication errors due to modified registry entries](#authentication-errors-due-to-modified-registry-entries)
14
15
-[Linux](#linux)
15
-
-[I get a white screen when launching Desktop](#i-get-a-white-screen-when-launching-desktop)
16
+
-[I cannot sign in using "Continue with browser"](#i-cannot-sign-in-using-continue-with-browser)
17
+
-[Error "cannot read property 'path' of undefined"](#my-shellterminal-is-not-detected-and-is-stuck-on-gnome-terminal)
16
18
-[I cannot access repositories under my organization](#i-cannot-access-repositories-under-my-organization)
19
+
-[I get a white screen when launching Desktop](#i-get-a-white-screen-when-launching-desktop)
17
20
-[My shell/terminal is not detected and is stuck on "GNOME Terminal"](#my-shellterminal-is-not-detected-and-is-stuck-on-gnome-terminal)
18
21
19
22
# Known Issues
@@ -32,10 +35,18 @@ Each known issue links off to an existing GitHub issue. If you have additional q
32
35
33
36
### My issue is not listed here?
34
37
35
-
Please check the [open](https://github.com/desktop/desktop/labels/bug) and [closed](https://github.com/desktop/desktop/issues?q=is%3Aclosed+label%3Abug) bugs in the issue tracker for the details of your bug. If you can't find it, or if you're not sure, open a [new issue](https://github.com/desktop/desktop/issues/new?template=bug_report.md).
38
+
Please check the [open](https://github.com/pol-rivero/github-desktop-plus/issues) and [closed](https://github.com/pol-rivero/github-desktop-plus/issues?q=is%3Aissue%20state%3Aclosed) bugs in the issue tracker for the details of your bug. If you can't find it, or if you're not sure, open a [new issue](https://github.com/pol-rivero/github-desktop-plus/issues/new?template=bug_report.yaml).
36
39
37
40
## macOS
38
41
42
+
### 'Apple could not verify this app is free of malware' error when launching the app
43
+
44
+
Related issue: [#33](https://github.com/pol-rivero/github-desktop-plus/issues/33)
45
+
46
+
This error is caused by the app not being notarized by Apple, as notarization requires a paid Apple Developer account.
47
+
48
+
Simply go to "System Settings" > "Privacy & Security", scroll down to "Security" and click "Open Anyway" on "GitHub Desktop Plus".
49
+
39
50
### 'The username or passphrase you entered is not correct' error after signing into account
40
51
41
52
Related issue: [#3263](https://github.com/desktop/desktop/issues/3263)
@@ -232,29 +243,30 @@ If you see an error that says "Not enough resources are available to process thi
232
243
233
244
## Linux
234
245
235
-
### The PackageCloud package feed is no longer working
246
+
### I cannot sign in using "Continue with browser"
236
247
237
-
The PackageCloud feed has been closed down. If you are seeing errors about this you should remove the configuration for this feed and refer to the [README](https://github.com/shiftkey/desktop#repositories)
238
-
for the new settings.
248
+
Related issue: [#54](https://github.com/pol-rivero/github-desktop-plus/issues/54)
239
249
240
-
#### APT configuration
250
+
After following the instructions in your web browser to authorize GitHub Desktop, the callback is not sent to the app and it remains stuck on the "Continue with browser" screen.
The most likely cause is that the URI scheme used by GitHub Desktop Plus for authorization (`x-github-desktop-auth://`) is not linked to the correct program. You can verify if this is the case by fully closing GitHub Desktop Plus (`Ctrl+Q`) and running the following command in your terminal:
This should open the GitHub Desktop Plus app. If it doesn't, it means the URI scheme is not linked to the app, and you can fix it by running the following command:
254
259
255
-
Electron enables hardware accelerated graphics by default, but some graphics cards have issues with hardware acceleration which means the application will launch successfully but it will be a white screen. If you are running GitHub Desktop within virtualization software like Parallels Desktop, hardware accelerated graphics may not be available.
260
+
```bash
261
+
# Prints the current default app for the URI scheme
**Workaround:** if you set the `GITHUB_DESKTOP_DISABLE_HARDWARE_ACCELERATION` environment variable to any value and launch Desktop again it will disable hardware acceleration on launch, so the application is usable.
264
+
# Set GitHub Desktop Plus as the default app for the URI scheme
### I cannot access repositories under my organization
260
272
@@ -267,13 +279,23 @@ in a couple of different ways:
267
279
generic error message
268
280
269
281
The root cause of this is organizations by default will have "OAuth App access
270
-
restrictions" enabled, which blocks the GitHub Desktop development app that is
282
+
restrictions" enabled, which blocks the GitHub Desktop Plus app that is
271
283
used by this fork.
272
284
285
+
You can verify if this is the case by going to https://github.com/settings/applications, clicking on "Desktop Plus (GitHub Desktop Plus)", and checking if your organization is enabled in the "Organization access" section.
286
+
273
287
**Workaround:** ask your organization admin to [approve access](https://docs.github.com/en/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization)
274
-
to the GitHub Desktop development app.
288
+
to the GitHub Desktop Plus app.
289
+
290
+
If you have not requested the GitHub Desktop Plus app for this organization, [follow these instructions first](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps).
291
+
292
+
293
+
### I get a white screen when launching Desktop
294
+
295
+
Electron enables hardware accelerated graphics by default, but some graphics cards have issues with hardware acceleration which means the application will launch successfully but it will be a white screen. If you are running GitHub Desktop within virtualization software like Parallels Desktop, hardware accelerated graphics may not be available.
296
+
297
+
**Workaround:** if you set the `GITHUB_DESKTOP_DISABLE_HARDWARE_ACCELERATION` environment variable to any value and launch Desktop again it will disable hardware acceleration on launch, so the application is usable.
275
298
276
-
If you have not requested the GitHub Desktop development app for this organization, [follow these instructions first](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps).
277
299
278
300
### My shell/terminal is not detected and is stuck on GNOME Terminal
279
301
@@ -283,7 +305,10 @@ environment's shell, despite the shell being selected in the application setting
283
305
Attempting to launch the shell from the application will show the error
284
306
"cannot read property 'path' of undefined".
285
307
286
-
**Workarounds:**
308
+
**Workaround:**
287
309
288
-
- Option 1: install a second different terminal, switch to it, then switch to the terminal you want to use, and then uninstall the second terminal.
289
-
- Option 2: open the application's developer tools and step through the JS calls to correctly set the shell. Further details at https://github.com/shiftkey/desktop/issues/344#issuecomment-1001287110
310
+
1. Install any other terminal emulator (it doesn't matter which one).
311
+
1. In GitHub Desktop Plus, go to "File" > "Options" > "Integrations".
312
+
1. Change the "Shell" option to the other terminal emulator you have installed. Click "Save".
313
+
1. Change the "Shell" option back to your preferred terminal emulator. Click "Save" again.
314
+
1. Uninstall the other terminal emulator you installed in step 1, you no longer need it.
0 commit comments