New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screensaver and M1 #86
Comments
Hi, i have same issue, this beautiful screensaver it's not works on my laptop Macbook Air M1 |
You can have a try for this: |
I don't have an M1 to test this out, so I'm afraid someone else will need to look into it |
Great report @TechVader! - would you mind submitting a PR to update the |
@pedrommcarrasco Just an update... I've never done a pull request, so I've been looking into how to do it. But while doing that, I thought I'd post a bug report on Keka's github, but apparently, the maintainer of Keka isn't able to reproduce my issue. So it might actually only be my computer. If we can agree that Keka is the issue, then I'll put in a Pull Request. Otherwise, it might be my computer. |
Unsure of what to think here, but in any cases, I feel like using Apple's tool should be the way to go here given how "sensitive" screensavers can be @TechVader |
@pedrommcarrasco I'm still checking this extraction issue, since I was unable to reproduce. Give me a few days 🙏🏻 By the way my display always turns off before any screensaver appears, but checking the effects of this one makes me wanna revert that. |
@pedrommcarrasco No need for a PR. The issue is resolved and it was my computer. Apparently, even though I had tried reinstalling the app through both the MAS and it's own website, I never cleared out the preferences/other files that come with it. I cleared it all out using an Application Uninstaller, and then did a fresh install, and the Keka app worked just fine to install your screensaver. Thank YOU for this awesome screensaver and to both you and and @aonez for taking the time to help remedy this. |
Hey guys and thank you for all this help |
@JalevYT Are you on 11.3.1? Mine will install but it never gives me the option to 'open anyway' under security & privacy and the preview says the current OS does not support the screensaver. |
@rpath16 i have the newest so 11.3 I think. But I downloaded it on a big Sur version earlier. I really don't now why slthos worked cause some of you have their issues |
Anyone has the screensaver on the latest Monterrey and MBP 14"? It's not working with the latest macOS. |
@HDtx94 install it, restart your system and then it should work |
I get a security warning from Apple when enabling this on my M1. |
Not working on MacBookPro M1 Max Error - You cannot use the Brooklyn screen saver with this version of MacOS. Contact vender for update |
I don’t understand? So it’s not going to be fixed?
Sent From Cyber Space With Typos
…On May 8, 2022, 1:12 PM -0400, ncls-fcs ***@***.***>, wrote:
I only let the localization issue get fixed by Xcode as @darrelldudics mentioned earlier:
> So I did some testing and here's what I found:
> I opened up the project in XCode and I only had one warning about localization.
Building and then installing it worked perfectly fine on M1 with macOS Monterey 12.2.1 . I never worked with screensavers and/or Xcode before but my uneducated guess would be that maybe the current macOS version needs to have the ressources in that specific spot, but I could be (and probably am) wrong on this. However what counts is that it worked for me after building it on a device with M1 chip.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Only thing I can say is that it worked for me after building it again on my Mac, however I don't know why. Maybe try doing that too and please tell us if it worked, maybe someone with more experience than I knows whats going on. |
I sure hope someone come up with an easy fix soon for M1. |
I have never used Xcode. However I have the project open in Xcode and have migrated localizations as you have done above. How do I now export as a .saver? |
@ncls-fcs - |
@Undivided-1 |
I confirm building the app via Xcode on a Mac M1 is working well. thx @ncls-fcs |
I'm on Monterey 12.2 and I install it using |
@truongnmt thanks, it works. |
This is still not working on macOS 12.6, M1 MacBook Air. Gives error "You cannot use the Brooklyn screen saver with this version of macOS." Installed via Homebrew. |
Can someone just make it for any M1/M2 please.
…________________________________
From: Jeff Pistone ***@***.***>
Sent: Thursday, October 13, 2022 3:01 PM
To: pedrommcarrasco/Brooklyn ***@***.***>
Cc: Hide My Email ***@***.***>
Subject: Re: [pedrommcarrasco/Brooklyn] Screensaver and M1 (#86)
This is still not working on macOS 12.6, M1 MacBook Air. Gives error "You cannot use the Brooklyn screen saver with this version of macOS." Installed via Homebrew.
—
Reply to this email directly, view it on GitHub<#86 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWI47B5HWZTTZGTF4LVILVLWDBTAFANCNFSM4WX23BPA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I got that too (I have a MacBook pro M1). But I got it working by going to the screensaver options and selecting the Brooklyn screen saver while holding down the option button. I assume it overrides the error, cause it immediately started working for me. Hope it helps! |
M2 Build success |
Is there any chance there will be an Apple Silicon native version released in the near future? |
Looks like there's a PR for this... #116 Think we could get that merged, @pedrommcarrasco? |
Just installed my new M2Pro Mac mini and the screensaver does not work. "The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 13.3.99." UPDATE |
In order to help us sort your issue, we ask that you provide the following information:
Description of issue
{{ What's happening? }}
The screensaver won't work for the new M1 Macs. Can someone please fix it?
The text was updated successfully, but these errors were encountered: