Skip to content

ARM version is not working on a a1 max  #1

Description

@avi-stx

ARM version is not working on a a1 max

Activity

  1. VasylBaran commented on Jan 30, 2022

    @VasylBaran
    Owner

    ARM version is not working on a a1 max

    Could you explain in more detail? Are you getting some error message? And could also mention your MacOS version? Thanks

  2. unickq commented on Feb 4, 2022

    @unickq

    m1 pro

    image

    image

  3. VasylBaran commented on Feb 5, 2022

    @VasylBaran
    Owner

    m1 pro

    image image

    Ah, that's probably because I used Big Sur to compile the app. I'll get a copy of Monterey and re-compile CommandShift in the coming days. Thanks for reporting the issue, btw! ;-)

  4. VasylBaran commented on Feb 6, 2022

    @VasylBaran
    Owner

    UPDATE: I've just upgraded to Monterey and the current version of CommandShift still runs fine. After googling the issue I've reasized that it's most likely due to Security settings. The following solution should help:

    Navigate to System Preferences, select Security and Privacy, and go to General. Go to Allow apps downloaded from and select Anywhere. In other words, you’re allowing non-App Store apps to run on your machine.

    Please let me know if it helped. Cheers! ;-)

  5. unickq commented on Feb 6, 2022

    @unickq

    @VasylBaran

    image

    sudo spctl --master-disable allows it, but doesn't help much

    image

  6. VasylBaran commented on Feb 6, 2022

    @VasylBaran
    Owner

    UPDATE: sorry, my bad. You're absolutely right, ARM64 app was damaged and now I've uploded a new version - please give it a try and let me know if everything is ok. Thank you! ;-)

  7. BEGEMOT9I commented on Feb 9, 2022

    @BEGEMOT9I

    @VasylBaran Hi! I've tried current version on M1 Pro and it still not working by the same reason (warning about damaged app) :(

  8. anorudes commented on Feb 19, 2022

    @anorudes

    Yep, it's not working on m1 :'(

  9. VasylBaran commented on Feb 19, 2022

    @VasylBaran
    Owner

    @BEGEMOT9I @anorudes @avirosenberg @unickq ok, so this is very weird... When I use CommandShift.app from dmg-image that I just created locally - it works fine. But after uploading it to Bitbucket/SourceForge/GitHub and downloading it again - the CommandShift.app becomes "damaged" o_O

    This is strange, some permissions issue perhaps?

    UPDATE: ok, the problem is that MacOS marks my app as damaged even though it isn't. I'll figure out how to solve it properly so that people won't have to hassle with this in the future but in the mean time if you want CommandShift to work right now - here's a temporary solution:

    Please run this command in Terminal (it recursively removes all attributes from app-file)
    xattr -cr /Applications/CommandShift.app

    P.S. just wanted to say 'thank you!' for trying out CommandShift so early on, it's my first release of a desktop app on GitHub and your feedback is very important because without it I wouldn't even know about this issue since it worked fine on my side. So thanks again! I'll keep you updated... ;-)

  10. BEGEMOT9I commented on Feb 20, 2022

    @BEGEMOT9I

    @VasylBaran Hi again! I tried your solution, it works, the application starts normally, but changing the language by pressing any of the combinations, that are in the list, still does not work. If you want, you can write to me in TG (@BEGEMOT9I) and try to debug together)

  11. VasylBaran commented on Feb 20, 2022

    @VasylBaran
    Owner

    @VasylBaran Hi again! I tried your solution, it works, the application starts normally, but changing the language by pressing any of the combinations, that are in the list, still does not work. If you want, you can write to me in TG (@BEGEMOT9I) and try to debug together)

    ok, and did you add CommandShift to "Security & Privacy -> Privacy -> Accessibility" ?

  12. BEGEMOT9I commented on Feb 20, 2022

    @BEGEMOT9I

    Yeah)

  13. VasylBaran commented on Feb 20, 2022

    @VasylBaran
    Owner

    @BEGEMOT9I ok, and the last question: do you have system level shortcuts to change language set to default like on this screenshot?

    Screenshot 2022-02-20 at 14 06 36

  14. BEGEMOT9I commented on Feb 20, 2022

    @BEGEMOT9I

    Not exactly, for "previous input source" i have cmd + space

  15. BEGEMOT9I commented on Feb 20, 2022

    @BEGEMOT9I

    Ooo, i've got it) Yeah, with default ctrl+space this app is working well 👍
    I think it must be described in README in order to avoid misunderstanding

  16. VasylBaran commented on Feb 20, 2022

    @VasylBaran
    Owner

    Ooo, i've got it) Yeah, with default ctrl+space this app is working well 👍 I think it must be described in README in order to avoid misunderstanding

    I'm glad it worked for you. Yes, you're right - I'll update the README. Thanks again! ;-)

  17. BEGEMOT9I commented on Feb 20, 2022

    @BEGEMOT9I

    Ooo, i've got it) Yeah, with default ctrl+space this app is working well 👍 I think it must be described in README in order to avoid misunderstanding

    I'm glad it worked for you. Yes, you're right - I'll update the README. Thanks again! ;-)

    I think info about changing app attributes would also be useful to describe)

  18. Ramlevy commented on Jun 2, 2022

    @Ramlevy

    xattr -cr /Applications/CommandShift.app
    @VasylBaran
    Had the exact same problem and this solved it! Thanks a bunch.

  19. VasylBaran commented on Jun 2, 2022

    @VasylBaran
    Owner

    xattr -cr /Applications/CommandShift.app
    @VasylBaran
    Had the exact same problem and this solved it! Thanks a bunch.

    I'm glad it worked for you. I plan to find a better solution (so that people wouldn't be getting this error message at all).
    But I'm not sure when this will happen since I'm from Ukraine and currently it's a warzone here. Can't believe I'm writing this, 4 months in and it's still feels surreal...

  20. VasylBaran commented on Jun 2, 2022

    @VasylBaran
    Owner

    Ok, the problem is that MacOS marks my app as damaged even though it isn't. I'll figure out how to solve it properly so that people won't have to hassle with this in the future, but I'm not sure when this will happen since I'm from Ukraine and currently it's a warzone here. Can't believe I'm writing this, 4 months in and it's still feels surreal...

    Anyhow, in the mean time if you want CommandShift to work right now - here's a temporary solution:

    Please run this command in Terminal (it recursively removes all attributes from app-file)
    xattr -cr /Applications/CommandShift.app

    P.S. I would also like to say 'thank you!' for trying out CommandShift so early on, it's my first release of a desktop app on GitHub and your feedback priceless. So thanks again, you're awesome! Peace! ;-)

  21. pinned this issue on Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions