-
Notifications
You must be signed in to change notification settings - Fork 6
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
Tried compiling app using script and manual process. Getting this error when trying to build (M1 Pro MacBook Pro) #2
Comments
Also tried what you mentioned in #1 with no success unfortunately :( |
Do you have the full log available from using the script approach? |
Potentially related: yue/yackage#19 |
Had to delete all the node lib refs in the middle to fit in a comment.
|
Same error as #1 in this case. When you say you had no success with #1 (comment), can you explain what happened in more detail? Was there an error message? What commands did you use? :) |
Commented out line 70 and it built this time... I swear before this exact thing didn't work...
I'm not entirely sure how to interpret that result. I ran the next command you suggested both with and without sudo but ended up with an error:
|
Very interesting! Thanks for the extra info! Although I'm not sure where this takes us. The first command you have that says that
Try see if you can sign a
|
Signed them all successfully. When I try to sign again it says they're all signed. After doing these 3 the app still won't launch. Here's the other outputs:
|
Amazing! This is really narrowing it down now. :) What happens with these:
I assume the first signing command says it's already signed, and the second one will throw an error with the vague internal error? |
Not exactly but kind of. |
Excellent! Thanks again for your help on this! I think this all just comes down to how Yode is bundled. One last thing to try if you don't mind:
|
Tried it - gave the same error of "internal error in Code Signing subsystem". App still won't open but hopefully I've give you some more clues as to why :) What's meant to happen if the app launches? Is there a menubar icon or dock icon? On mine it looks like the dock icon is about to appear - a small gap starts to open but then it disappears. To me that's always happened on macOS if something is just crashing on launch. |
Will have to research more, and open a ticket on Final thing to try for now I promise: So on first launch, you will see it open in the dock and then close, but then it's supposed to show a modal asking for permissions. Once granted, it appears as a menubar icon. If you're not seeing the permissions modal, it's likely that it did crash somewhere, likely on signature verification. :( What I think is happening is that Yode is downloaded pre-signed, but on build, it modifies Yode and combines it together with the compiled app code, which makes the signature invalid. And I think it's failing to re-sign the code because it's not liking the fact there's "hidden data" attached to the binary, which M1 is probably very strict about. It seems like it should be a very common problem for multiple apps but I'm not finding much in terms in solutions. Hypothetically I think I can create a custom build script that avoids combining the files together and signs the If you're comfortable with it, you could try using |
That command shows "invalid signature (code or signature have been modified) Ran it as npm start with those signed - showed up with permissions window that I couldn't sign, even when I manually added the app in System Preferences. Would refuse to open the app even after allowing the permissions. |
Unfortunately I’m a structural engineer not a software engineer so I’m not much help in terms of knowing where to look next! But if you point me in a direction to read up more I’d be keen to keep trying to fix it in my spare time 😄 I do some basic coding in the background when I bored from designing buildings anyway.. |
You could have fooled me, would have assumed you were a software engineer! 😂 That confirms it so, it's not liking the fact that Not much else I can think of that could be looked into at the moment. I'll research later this evening. Might just have to bit the bullet and write that custom build script from scratch. At least I have a lot more information now that really helps to narrow it down! Your help has been very much appreciated, learned so much! 😁 |
Me too mate. I just got it running by giving Terminal the permissions temporarily. Finally saw the little DWP appear up in the menu bar. But alas... no previews are appearing in the dock 😄. The debugger is running in the terminal and showed this:
What does Visual Studio Code have to do with the app running? |
Oh, one piece of information that I probably should've mentioned way earlier. I'm on the macOS 13.0 Ventura beta 1, so there could be heaps of bugs inherent in my OS that wouldn't affect others. |
It's possible Aliases are an important feature. Sometimes what an app is called in the dock, is not the same as the name of the app according to the system processes. For example, Visual Studio Code is called "Visual Studio Code" on the dock, but when you get a list of running processes, it's called "Code". This occurs fairly rarely though, most apps are usually the same name, but the config is available should it happen for another app. 🙂 |
Updated the code to include some additional useful debug messages. :) |
Another test to try. I noticed that sometimes Mac doesn't let you sign over binaries if they have an issue with their existing signature. Try to remove the signature first, then see if you can sign it.
|
Gave it a go - no luck. App won't open yet without using |
Did the additional debug messages show additional information when using |
Custom build script that in theory, should allow signing.
If this works, I'll update the normal build script to use this approach instead. 🤞
|
Hi, finally got to try this out now. Yes that script worked to create an app that could launch. It launches with the permissions dialog - but even once I give it Accessibility and Screen Recording permission it doesn't let me go beyond that screen. |
Brilliant! I'll update the installation script, thanks for confirming! :) As for it not showing anything beyond that, when you try running through the terminal, what do the logs say when you try to hover over the dock items? The latest version should show more debug logs. :) |
Just gave it a go. Seeing nothing unfortunately. I don't see any previews. I ran it and clicked around a little. Could be an issue with Ventura that I'm seeing nothing?
|
I would have expected to see something like this here:
The only way you can't see the logs there, is either something going wrong with listening to mouse moves, or potentially the mouse position is being calculated incorrectly. Is your dock located on the bottom of the screen? Is there something unusual about your monitor setup or anything? |
Dock is on the bottom and there's nothing unusual going on with monitors or anything, except that I'm on Ventura beta 1 😄 |
The only other thing you can do is try is added in additional The only other explanation is that Apple changed how accessibility works, but that would be a massive breaking change for them to make... 🤔 |
I had a bit of a play by adding some more debug messages in but nothing I did made debug show more information than the following:
As I said though, I'm not much of a programmer, so I was kind of just playing around in the dark with it 😄 |
BTW an alternate app to this that works decently but has also been kind of abandoned is DockMate. It's more modern than HyperDock. I have emailed the developers asking if they'd be willing to open source it too as it seems to not be maintained anymore, so if that ever happened there'd be a much larger foundation to build upon for this project. |
I just find it really weird you're not seeing anything additional in the logs. What changes did you try to make exactly? Can you outline the steps? Try throw in something near the very beginning of the I'm aware of the alternatives, but like you said, they're often abandoned, closed source, and charge a fee, and for a work laptop, that's just a no go. 🙂 |
Not much I can do from here unfortunately. 🙁 Only thing I can suggest is to keep throwing in debug calls throughout the code (add them everywhere), and printing out the variables, until you spot something unusual. As you suggested, it sounds like it's not picking up on the fact it's hovering over the dock. Did the DEBUG_LOG you add show anything odd about the co-ordinates? Try maybe adding |
Ok, I'll give it a go when I have more time on my hands 😄 As I said my day job is structural engineering 🏗️ |
Hi - I'm back on Monterey now, was having too many issues and bugs with Ventura. The app is still having the same issues as when I was on Ventura - App is not detecting anything I mouse over. This all makes me think the problem may be with Apple Silicone compatibility as I'm on an M1 Pro. |
It does sound like it, but none of the code to my knowledge is Intel specific... 🙁 And if part of the native modules is working which appears to be the case, would be odd for another part to not work... |
Mmm yeah I'm unsure unfortunately 😞 likely have to wait until you buy an Apple Silicon Mac 😆 do itttt |
I'm curious I've got this error after I ran ´npm audit fix´ due to some vulnerabilities. If I did not run the npm fix command I've get the error from issue #1 (also M1). Was this the same with you @apotenza92 |
@DavidKaub Have you tried the script I've posted in #2 (comment) ? |
I just ran the script you suggested. It definitely fixes the signing errors. But I also don't get any preview when hovering over the dock. Running
I will tinker the debug output to narrow it down but, since I'm very new to Mac, I don't expect too much.... |
@apotenza92 Any updates from here? |
That's perfect, means the situation is reproducible consistently on M1. :) If you can debug it further, would be much appreciated. I have no access to an M1 so I'm completely locked out of helping on this issue, but happy to answer questions where I can. I'm very new to Macs as well, so it wouldn't be surprising if I done something silly somewhere. 🙂 It sounds like |
While I wish I would be able to help you with this issue and really appreciate the effort, I have to admit that I have given up on this app since I found another open source alternative that works good for me (AltTab + DockAltTab). Maybe this can help somebody, or taking a look into the code might also help with development here. Regards |
I've been able to reproduce this behavior on an M2 as well. I'm a developer but have no experience with Objective C or developing MacOS apps 😅 I'm happy to help with debugging wherever I can. So far I've observed that I've also tried to inspect the dock as an AXUIElementRef appElement = AXUIElementCreateApplication([[[NSRunningApplication runningApplicationsWithBundleIdentifier:@"com.apple.dock"] lastObject] processIdentifier]); This returns an element with Any ideas what might be going wrong? I'm kind of stumped ATM. It seems like |
Still no M1-type device to test with unfortunately, so I can still only speculate. I wonder if it's some sort of security permission that's required, that has a different default between Intel and M1 chips... Like you said, it would be baffling if they just removed the functionality entirely, but it would make sense to me if they changed a default permission somewhere like how code signing became mandatory... |
So I got it working...noticed that After changing all the instances of |
Nice job!! Very interesting discovery. I noticed I'm using a combination of Do open a PR, I'll give a try on my Intel Mac over the weekend and merge if all is good! Thanks for looking into this! |
Can confirm this worked for me too, did a simple find and replace as per @t1m0thyj comment. Thanks! |
Hi, tried compiling app using script and manual process. Getting this error when trying to build (M1 Pro MacBook Pro)
The text was updated successfully, but these errors were encountered: