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

MacOS: "Check with the developer to make sure Signal works..." #3261

Closed
1 task done
salinggergo opened this issue Mar 25, 2019 · 9 comments
Closed
1 task done

MacOS: "Check with the developer to make sure Signal works..." #3261

salinggergo opened this issue Mar 25, 2019 · 9 comments

Comments

@salinggergo
Copy link

salinggergo commented Mar 25, 2019

  • I have searched open and closed issues for duplicates

Bug Description

In February I had the exact same issue as described in #3054 , contacted Signal support and following their advice I deleted the app, deleted all app folders from /Library/AppSupport/, re-installed, re-launched my computer and worked properly for some weeks.

With version 1.23.1 I have the same issue but the previous workaround doesn't fix the bug anymore. After I deleted the app, etc, I get only the attached Mac OS X error message.

Steps to Reproduce

  1. step one
  2. step two
  3. step three

Actual Result:

First: Unhandled Promise Rejection; Then: Mac OS X launch error message

Expected Result:

App launches

Screenshots

Screen Shot 2019-02-06 at 08 25 43

Screen Shot 2019-03-25 at 22 43 37

Platform Info

Signal Version:

1.23.1

Operating System:

OS X 10.11.6

Linked Device Version:

iOS 12.1

Link to Debug Log

@scottnonnenberg-signal scottnonnenberg-signal changed the title Signal-Desktop launch and re-install error MacOS: "Check with the developer to make sure Signal works..." Mar 26, 2019
@smoser11
Copy link

ditto. same problem here on OSX 10.11.6 (15G22010)

Unhandled Promise Rejection
Error: The resource could not be loaded because the App Transport Security policy requires the use of a secure connection.
at MacUpdater.doDownloadUpdate ([REDACTED]/app.asar/node_modules/electron-updater/out/MacUpdater.js:167:7)

....

@marieae
Copy link

marieae commented Mar 27, 2019

Ditto for me on my mac. Hope there is a fix soon.

@scottnonnenberg-signal
Copy link
Contributor

If you're running into this, the workaround is to go to https://signal.org/download and install the latest version of Signal Desktop. Then it won't have trouble downloading new updates, because it is the latest update.

@salinggergo
Copy link
Author

If you're running into this, the workaround is to go to https://signal.org/download and install the latest version of Signal Desktop. Then it won't have trouble downloading new updates, because it is the latest update.

Hi Scott, sorry if I was not clear but I did exactly that and I still run into the osx error message. I retried it now, downloaded the latest version, the same happens, Signal does not launch.

@scottnonnenberg-signal
Copy link
Contributor

@salinggergo I meant this error: "Error: The resource could not be loaded because the App Transport Security policy requires the use of a secure connection."

@salinggergo
Copy link
Author

Yes, first of all I tried that but did not work for me. That's why I contacted your help, tried the other workaround they suggested which worked for some time indeed but now I'm having the same issue

@scottnonnenberg-signal
Copy link
Contributor

Okay, this is a duplicate of #3161

@salinggergo
Copy link
Author

I tried the Beta you suggest there and doesn't work either.

@salinggergo
Copy link
Author

Here's a workaround for this issue, not the perfect but maybe others have the same problem waiting in vain for a solution:

  1. i downloaded the latest version that worked for me v18.1
  2. installed, opened it
  3. signal won't let messaging because the version is expired, it ask for an update
  4. i downloaded the latest version too, copied it to the app folder but kept also the latest functioning version there (signal and signal copy)
  5. that way i was able to launch the new version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants