currently if the user sends an heic image, the web still shows the download sign, but it doesn't either display or download the image, currently, no browser can actually support heic image yet, so we need a mechanism to automatically convert the heic to JPG

My internet service has occasional short outages. Of course when that happens, AirMessage notices it can't reach the internet. This makes it so sad it gives up.

At that point my Android AirMessage App notices that it can't reach the server. This makes it sad. So it throws up it's hands and gives up.

Then my loving correspondents send me some messages. I don't get these. They think I'm a jerk. This makes me sad.

The server's menu-ui shows a "Retry" choice. That has never worked for me. But killing and restarting the server makes things better... kind of.

I think, both the server and client should be more persistent. Giving up makes me look bad. We are all sad about that, I'm sure.

When I tried to build server and (I believe) followed the requisite setup instructions, the build fails due to the fact that it can't locate the zlib dependency. I was able to workaround this by:

• going to File>Add Packages>Add Local and selecting the Zlib folder in the base of this repo
• I then went to the AirMessage target, General>Frameworks, Libraries, and Embedded Content, clicked '+'
• Locate Zlib library and click Add

I'm very new at Xcode/MacOS development, so I'm unsure how/if this is fixable from a project configuration standpoint, but I just wanted to document the steps in case anybody else ran into this as well.

Im trying to add my own reverse proxy on it and the server refuses to work the same way as when i connect to directly to ip address. Example 192.168.1.90:1359 works fine but airmessage.example.com does not and airmessage.example.com points to http://192.168.1.90:1359. So im a little confused why?

@tagavari Hey, I replied to you on Discord -- these are the fixes that have eliminated those AppleScript Invalid Index errors for me. Basically makes use of some repeat loops to detect the presence of the buttons we're looking for, and uses try catch exceptions to prevent stopping on irrelevant errors.

In the future, I might try speeding up the execution of these scripts by replacing some of the arbitrary delays with similar loops.

v3 works great and can send texts etc, 3.4.1

but when downloading v4, fixing the privacy accessibility settings, running it, the client connects, the client can see the facetime experiemntal toggle being turned on, but it fails on liteconversationretrieval / of length 0 so the client just never loads messages :(

what coudl this issue be? i cleared cache on client and everything to confirm. is there cache in server i need to clear?

I've had a repeating issue that occurs more frequently than I'd like. Often I will open the app, and it will say "Personal server not available". The server, in the menu bar, will say "An external error occurs." The server does not, from appearance, try to restart.

Might I suggest a retry-loop with a configurable threshold (maybe with a default of 5 retries before failing), and use/show a log window instead? I would strongly prefer this over having to connect to the Mac over VNC and click a button to restart the server: a process that should realistically be automated.

When the server loses connection to AirMessage Connect, it may take a while for it to pick up on the fact that the connection has been severed and re-establish it. The server should check the health of the connection more frequently.

This can easily be recreated on laptops by running the server, then closing the lid for a few minutes. When the laptop is reopened, the server will still think it is connected, but no clients will be able to connect to it.

Reported by Avibee and others on Discord: https://discord.com/channels/992925221256450068/992929582439202908/1004535441212571769

This may be a duplicate of #13.

Hi,

Is there any way that you could submit AirMessage Server to be included as a Homebrew Cask for users who'd prefer to use brew as their package manager?

Thanks in advance!

Showing All Messages No account for team "T86T6AP696". Add a new account in the Accounts preference pane or verify that your accounts have valid credentials.

No signing certificate "Mac Development" found: No "Mac Development" signing certificate matching team ID "T86T6AP696" with a private key was found.

Not sure if this is the android app or the server but anywho, submitting it here.

When the android app loses connection which happens several hundred times per day while connected to my local wifi (that's because the fallback is the intranet address?), it sometimes decides to just send me the same notification over and over again. When I open the android up, I get 2 copies of the same messages - send and received. Then on the next notification I get 3 copies, and then 4. Haven't seen 5 yet, fingers crossed! 🤞

Right now, you can't sign into a Google account that uses security keys because the in-app browser on Mac doesn't support them in AirMessage. Additionally, with Advanced Protection enabled there is no bypass other than removing and re-enrolling all your keys.

Rather than using the alternative iMessage setup method, it would be nice if the app could either: show the URL (so the user can copy it into their own browser that does support security keys) or be given the option to complete the sign-in directly in their browser.

I have my iMac set up to automatically turn on when power is restored. However, we had a couple power outages here since I set it up, and neither time did the AirMessage server start automatically. (It does auto-start after a full reboot) Is this an AirMessage issue? Is this a macOS issue? Has anybody else had this issue? Is there a fix?

P.S. My iMac is running Big Sur.

After upgrading to version 4.1.1 this msg showing up

“AirMessage” is damaged and can’t be opened. You should move it to the Bin. This file was downloaded on an unknown date.

Like the title says. Attempting to FaceTime while screen is off (but system is still on) will do nothing, giving "Unable to complete FaceTime" error. Going back to the Mac, turning the display on (even hours later!) will cause the call to start right there and then, even though the client is no longer "there". Obviously on my machine there is no screen, it is a Mac mini, but still.

This becomes an even bigger issue considering the fact that, by default, disconnecting from a screen share will put the display to sleep.

Workaround I found (only applies to headless machines):

• Set all the options to perma keep display on, sleep never
• sudo defaults write /Library/Preferences/com.apple.RemoteManagement RestoreMachineState -bool NO to keep display on when disconnecting

When a message fails to send, hitting Retry can cause the server to send the message multiple times. This is more likely to happen with larger attachment files.

I'm not sure if this is a bug in the client, server, or both, so until this is looked into further it will be filed here.

Originally reported by rx on Discord