errors updating to v1.9.8 arm64 prerelease

[d4tocchini]

Great news on native support for Apple Silicon!

I just updated a server (m1 mac mini ventura13.6.7) from v1.9.7 to the v.1.9.8 prerelease. After opening the app I get series of many repeating error popups of the following saying Messages & Facetime quite unexpectedly.

Both Messages & FaceTime are consequently no longer open, but bluebubbles does boot a lot faster than before ;) I then tried manually opening Messages & FaceTime and testing if any API calls went through only to receive 500 Internal Server Errors.

Should I restart the state of the server? Let me know if there's anything else I can do / provide to help, thanks!

[d4tocchini]

After trying a fresh install, those FaceTime / Message popups showed up only when I tried to turn on the private API features in the onboarding flow. Something w/ papi...

[zlshames]

Yeah I need to debug this some more. The issue is mainly that I don't have an m1 Mac to test against. So I'll need to work closely with one of you to make some test builds to help figure this thing out.

I don't think the issue is how I'm building the private API dylib, but rather, how im calling the app

[HenryTheX]

it's related to Private API send method. If you turn off Private API Attachment send, then it wont crash server imesssage any more.
Waiting for developer to fix

[zlshames]

it's related to Private API send method. If you turn off Private API Attachment send, then it wont crash server imesssage any more. Waiting for developer to fix

it's just related to the private api in general. Not a specific function within it.

[keithah]

Is this fixed? happy to test a build or give access to a test machine if thats helpful.

[zlshames]

Is this fixed? happy to test a build or give access to a test machine if thats helpful.

From our research, it seem this may be a bug in macOS. This other GitHub issue & my comment explains a little bit of it: rofl0r/proxychains-ng#481 (comment)

For some reason your architecture list is "empty", ''. You can fix it by just adding a boot arg, as seen in this StackOverflow comment: https://stackoverflow.com/questions/67695609/building-for-arm64e-on-apple-silicon/70982791#70982791

Then reboot. I'm not sure there is anything I can do to fix it.

We've had other Apple SIlicon users report that it's working for them just fine. So we know it's "environmental". Users on Sonoma don't seem to have the issue, but users on Ventura have (from the feedback I've gotten). I don't necessarily advise upgrading to Sonoma.