Boostnote.next: Support for Mac 10.15

Created on 13 May 2020  ·  14Comments  ·  Source: BoostIO/BoostNote.next

OS version: Mac OSX 10.15 can`t run the lastest version of team or legacy.

bug

Most helpful comment

@ohhheyyyy I had the same issue. You can override this here https://support.apple.com/en-us/HT202491

All 14 comments

I have same issue.
Opening Boost Note.app display the dialogue.
macOS 10.15.4

スクリーンショット 2020-05-14 11 18 48

For me it's working on macOS 10.15.4, downloaded from boostnote.next website

Working on 10.15.4 for me too but there is no way of moving (dragging) the window.... No title bar

@kfcobrien Could you provide some screenshots? And maybe what version you have installed?

Screenshot 2020-05-25 at 13 33 25
Screenshot 2020-05-25 at 13 33 45

I can resize fine but no way of dragging the window to reposition it

I'm having exactly the same problem as @kfcobrien , although it only started happening after the third or fourth time of opening the app, I think.

I can resize fine but no way of dragging the window to reposition it

+1. The app window can't be moved on MacOS 10.15.5.

The app does not open in Mac OS 10.15.5. It throws a security error.

“Boost Note” can’t be opened because Apple cannot check it for malicious software. I downloaded it from the main website today.

See attached screenshot.

@hitenv79 Could you try posting the screenshot again? It's not linked in your previous message.

@Flexo013 I trigger the same error when I attempt to open Boost Note on macOS Catalina Version 10.15.5. Screen shot below 👇

boostNoteCantBeOpened

@ohhheyyyy I had the same issue. You can override this here https://support.apple.com/en-us/HT202491

Similar to @k3ntar0 on macOS Catalina 10.15.6 with the ZIP distributable:

image

Pressing the help button oddly produces nothing - macOS issue, but I don't recall seeing that before.

With the DMG, granting via "open anyways" didn't run the app.

Checked out master branch, and was able to build and run via npm. Wish the setup / launch of that was a little easier (inclusion of .env and single npm command to launch would be cool).

This issue will be fixed as of 0.12.0. If it does pop-up again, leave a comment here and we'll re-investigate.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

marilari88 picture marilari88  ·  3Comments

jcarr98 picture jcarr98  ·  5Comments

Flexo013 picture Flexo013  ·  4Comments

derekantrican picture derekantrican  ·  4Comments

themattgabriel picture themattgabriel  ·  4Comments