[Feature request / Error] Support for Apple Silicon / M1 Binaries

[Pa1nstar]

Hi,

first of all thanks for your work! :-)

I have been using MacPass (version 0.7.12) and MacPassHttp for that. Because of the problems with MacPass under BigSur, I switched to the continuous build (version 0.8 beta). Since I use a Macbook Air with M1 chip, this version now also supports the new Apple Silicion processor (yeah, great work! :-) ).

Unfortunately, however, MacPassHttp is now listed as incompatible (see screenshot) with a note that it is not compatible with the architecture.

Since I would hate to go back to the old version of MacPass, but equally hate to do without MacPassHttp, my question would be if you could update MacPassHttp to the M1 binaries as well? :-)

That would be really great...

[ssdowd]

@Pa1nstar you should check out KeepassXC. Works fine on my m1 mac, plus supports auditing and nicer autotype options. It appears to be updated regularly.

[justr1]

Thanks for this great project.

But due to incompatibility between MacPassHTTP 0.3.2 and MacPass 0.8.x at Apple M1, I had to downgrade to 0.7.12. Mac Pass without MacPassHTTP is useless for me. Are there any plans to make a MacPassHTTP-M1 compatible version or do I have to look for alternatives?

[mstarke]

Sure. I’m going to provide apple silicon binaries soon! Can you tell me what the problem was when running 0.8.1 under Rosetta?

[justr1]

Don't know, if it's possible to force MacPass to use Intel-Code with Rosetta instead of M1-Code. By default M1-Code is used and therefore MacPassHTTP is marked as incompatible.

[mstarke]

If you open the Info panel for MacPass you can check the box "Open using Rosetta" and macOS will launch the Intel binary.

[luk355]

@mstarke, thanks a lot for your work on this project. I can confirm "Open using Rosertta" works with this plugin, however, it would be really great to utilize the M1-Code on the M1 powered macbooks. Can you please add the support?

[ramujin]

@mstarke I'm just curious if there's any update on support for M1/M2 chips or are you just referring people to use Rosetta (or walk away from MacPass) since your comment from last year made it seem like you were going to add this capability? Thanks in advance!

[mstarke]

I did try to update the project but ran into a lot of issues re-building the extensions. I need to sort this out. Sorry for the big delay. Have you considered relying on Autotype and AutotypeURL for a replacement? It's not the same but "works for me" :)

[ramujin]

Thanks for the update! Yep, that's what I've been using. It's not the same, but it "works for me" for now as well. I wish global autotype just worked out of the box!

[mspbonn]

MacPassHTTP could not be build from the sources due to an error on silicon-architecture:

me@Mac-mini MacPassHTTP % carthage bootstrap --platform macOS
*** Checking out KeePassHTTPKit at "1.3.1"
*** Checking out jsonmodel at "cd940e7ae0e74c927cd4293931f5d7e6465c343d"
*** Checking out GCDWebServer at "3.4.1"
*** Cloning jsonmodel
*** Cloning GCDWebServer
*** Cloning KeePassHTTPKit
*** xcodebuild output can be found in /var/folders/h7/px3jjdl11b11rx5_6pnjznkr0000gn/T/carthage-xcodebuild.TidBS8.log
*** Skipped building GCDWebServer due to the error:
Dependency "GCDWebServer" has no shared framework schemes for any of the platforms: Mac

If you believe this to be an error, please file an issue with the maintainers at https://github.com/swisspol/GCDWebServer/issues/new
*** Skipped building jsonmodel due to the error:
Dependency "jsonmodel" has no shared framework schemes for any of the platforms: Mac

If you believe this to be an error, please file an issue with the maintainers at https://github.com/jsonmodel/jsonmodel/issues/new
*** Skipped building KeePassHTTPKit due to the error:
Dependency "KeePassHTTPKit" has no shared framework schemes for any of the platforms: Mac

If you believe this to be an error, please file an issue with the maintainers at https://github.com/MacPass/KeePassHTTPKit/issues/new```

[viktorb1]

I compiled it for the M2 chip, but it does not work smoothly. Lots of syncing issues when I try to use it with a chrome extension. I keep getting "The document “Database.kdbx” could not be autosaved. The file has been changed by another application." Any idea on how to fix this?

MacPassHTTP.mpplugin.zip

[mstarke]

@viktorb1 this is an issue with the current sync implementation and NSDocuments architecture I’m having problems with for a while. I did consider this behavior to be as designed by Apple since it‘s technically correct. However the user experience is bad and I need to get this done differently (by not showing this info in most cases)