The application can't be opened. (Startup error)

[wayneashleyberry]

Describe the bug

I have installed Meeting Bar using homebrew, and it runs just fine. However, if I restart my machine or log out and back in I get a cryptic error message "The application can't be opened. -50".

I then have to open Meeting Bar manually, which works fine.

To Reproduce

Install Meeting Bar, enable "Launch at Login" and then log out and back in again.

Expected behavior

This error should not appear and Meeting Bar should open on startup.

Screenshots

Desktop (please complete the following information):

                 -/+:.          wayne@Waynes-iMac
                :++++.          OS: 64bit Mac OS X 10.15.7 19H2
               /+++/.           Kernel: x86_64 Darwin 19.6.0
       .:-::- .+/:-``.::-       Uptime: 44m
    .:/++++++/::::/++++++/:`    Packages: 107
  .:///////////////////////:`   Shell: fish 3.1.2
  ////////////////////////`     Resolution: 6400x3600
 -+++++++++++++++++++++++`      DE: Aqua
 /++++++++++++++++++++++/       WM: Quartz Compositor
 /sssssssssssssssssssssss.      WM Theme: Blue
 :ssssssssssssssssssssssss-     Disk: 11G / 1.0T (2%)
  osssssssssssssssssssssssso/`  CPU: Intel Core i7-10700K @ 3.80GHz
  `syyyyyyyyyyyyyyyyyyyyyyyy+`  GPU: AMD Radeon Pro 5500 XT
   `ossssssssssssssssssssss/    RAM: 10084MiB / 32768MiB
     :ooooooooooooooooooo+.
      `:+oo+/:-..-:/+o+/-

Additional context

I tried removing everything from launch agents, and all other startup items to eventually get to this. I can safely reproduce the error message on startup by uninstalling and reinstalling Meeting Bar.

[leits]

Thanks, @wayneashleyberry!

@jogendra , @Itaybre can you take a look at this issue?

[jogendra]

Hey @leits! Let me take a look.

Are you also facing the same issue? (and updated to latest version?) @leits @Itaybre

[Itaybre]

Saw this today (I don't restart my machine frequently) but MeetingBar did open automatically

[jogendra]

Most probably the reason would be the Development Team for the AutoLauncher is not set when you released (the bundle homebrew fomaula using). As I was not able to set (do not have paid membership). That would probably fix. If not, I will do my part.

[leits]

@jogendra, Now the target has been signed with DevTeam and it happened earlier than the previous release.
v1.6.1...master

[jogendra]

@wayneashleyberry please update to latest version, 1.6.1. It should fix your issue.

To update, run:

brew upgrade meetingbar

Still not get fixed, try running brew reinstall meetingbar after upgrading.

[jogendra]

@leits we should also put/ask meetingbar version in issue templete. It will help us getting better idea, which version having the issue.

[wayneashleyberry]

@jogendra tried both of those and still get the same issue. Removed it completely, did a cleanup, installed afresh and still the same. Pretty sure I was already running on v1.6.1 as well 🤷

[jogendra]

@wayneashleyberry oh so sorry to know that it didn't work. Let me look into this earliest.

[jogendra]

Hey @leits @wayneashleyberry
I just figured out what causing the issue and fix to it. Problem was with previous implementation. Opening a PR for the fix, today only.

[marcusziade]

I'm still getting this crash after updating to 1.6.1 😢

Is the latest Master (with the merge above) updating through Homebrew? I did brew upgrade meetingbar

[jogendra]

@marcusziade new release has not been made after the merging of PR above. Hopefully, it will be released soon. I am sure this will fix your issue.

[marcusziade]

Any update on this?

[leits]

Sorry for the delay, guys!
The fixed version here and on homebrew available here and on homebrew:
https://github.com/leits/MeetingBar/releases/tag/v1.6.2
The AppStore version is on review.
@marcusziade, @jogendra

[tonglil]

Mm, as a new MeetingBar user, I am encountering this when I click on an event that doesn't have a meeting link (aka a regular calendar event).

FWIW, the event is on an iCloud calendar I own.

The application can’t be opened. -50

[jogendra]

@tonglil Seems like a similar issue. I think most probably the API for Launch at Login changed so it is giving an error. Have to wait for few more reports to know the cause.