airmessage / airmessage-server-legacy Goto Github PK

Your SSL cert expired!

Below is a screenshot of two links in an AirMessage conversation. The first link was sent directly from my Mac, while the second link was sent from AirMessage. The second link shows a preview in AirMessage, but it does not show a preview on Apple devices, as seen in picture 2.

iMessage allows users to respond to specific messages w/ inner threads going on. It’d be good to duplicate this functionality.

Seems to be a very useful feature that many users would appreciate.

Run the airmessage program on macos vps, the web version can be sent, but the other party cannot receive it, macos does not support imessage, will it affect the software forwarding success? Software Permission has been given, including full access

Hello i installed 3.4 and it keeps complaining about needed full disk access despite have it enabled in the settings. Am i missing something here?

Thank you for working on this. You absolutely rock!

The issue:

I run the server on system boot (added to 'Login Items' with auto-login).

On the latest version, 3.4.1, AirMessage will often start in an error state. Right-clicking on the icon gives the error "Communications error" and there's a Retry button. 100% of the time clicking on Retry will start the server successfully.

So my suggestion is: can/would you add a built-in timer that automatically reattempts to start the server on this error? That'd be extremely helpful and save me from having to remote into the machine only to click Retry.

Thanks! :)

When a mac has text message forwarding airmessage seems to have trouble texting in a conversation when using text message forwarding. This causes it to fail and locks up messaging.

After syncing the Mac the server is running on with iCloud, any messages that were downloaded from iCloud will sync to Airmessage in reverse chronological order, with many duplicated messages and “Read Dec 31, 2000” showing. I saw two reddit threads from 2 years ago where this was acknowledged as an issue, but not fixed, so I’m not entirely sure if this has been fixed by now and it’s something on my end, but this does still seem to be an issue so I figured I’d throw it in here since I can’t find anything about it outside said old reddit threads.

On m1 mac mini, running big sur, sending a message immediately returns "This conversation isn't available"

I am not sure if I did not configure something correctly, but running the server on a Mac (running 10.10 MacOS) whenever there is an update available, there is a pop-up that blocks any further messages being transmitted. I need to go to the desktop and dismiss the update pop-up before traffic resumes. Is there a way around this? Either auto-update or disable update notifications?

On Mac OS X 11.4 (20F71), there is no way to grant automation privileges to AirMessage.

Under System Preferences > Security & Privacy > Privacy > Automation, AirMessage does not show up as one of the apps requesting automation privileges.

When I attempt to send a message from my Android device, I get the error 51:53: syntax error: Expected end of line by found property. (-2741).

Starting AirMessage in the background forces my GPU on, which increases heat and power consumption:

I don't recall this happening before upgrading to 3.2.1.

Automatically convert HEIC image files to a more common format on-the-fly so they can be viewed in Chromium based browsers.