search

FruityRazer / FruityUI

An UI for FruityRazer.
GNU General Public License v3.0
121 stars 3 forks source link

app crashes on start #18

Closed ashaik4 closed 4 years ago

ashaik4 commented 4 years ago

hardware configuration: razer core x chroma with macbook pro 15 inch 2019. FruityUI_2020-07-17-020431_ashaik.crash.zip attached the crash report here.

edualm commented 4 years ago

Hey,

It appears that you attempted to run the app without moving it to the Applications folder, am I right?

Could you try the latest build (https://github.com/FruityRazer/FruityUI/releases/tag/v1.2.5), and running it from the /Applications folder? If it still crashes please send me another crash report and I'll be able to look deeper into it. :)

ashaik4 commented 4 years ago

Hi @edualm

I moved the app (build 1.2.5) to the Applications folder. It crashes again. However, it starts fine when I run it without plugging in my eGPU(Razer Core X Chroma).

Also, my razer blackwidow elite keyboard is attached to the USB Port of Razer Core which is connected to my Mac over thunderbolt 3. FruityUI_2020-07-18-145754_ashaik.crash.zip

edualm commented 4 years ago

Erm...

Well, it is probably something related to the hardened runtime, but I'm honestly not able to test that. I don't have an eGPU (or, even, a Thunderbolt 3 dock to check if the same problem is present there).

Does it work if you have the eGPU connected but the keyboard connected directly to your Mac?

ashaik4 commented 4 years ago

nope, it doesn't without eGPU. Everything worked before the latest MacOS update. I think something broke after the MacOS update. I am an experienced python developer but I can take a look at the code with some guidance.

ashaik4 commented 4 years ago

The fruityUI app opens up without any peripherals attached. It doesn't work when any dock, or even when the razer keyboard is attached using a USB to type-c converter.

edualm commented 4 years ago

So, I updated my Mac to 10.15.6, and the app still works flawlessly for me.

I have attached a debug build of FruityUI here. Can you try this one? You may need to cmd-click the app to open it as it's not developer ID signed / notarized.

If it still crashes, can you send me the crash log of this one? It should at least give a much clearer message.

FruityUI.zip

ashaik4 commented 4 years ago

FruityUI_2020-07-19-011221_ashaik_without_egpu.crash.zip FruityUI_2020-07-19-011452_ashaik_eGPU.crash.zip

The app doesn't open with or without eGPU. I have attached the crash reports for both the scenarios.

edualm commented 4 years ago

Exception Type: EXC_CRASH (Code Signature Invalid)

Has to do with codesigning, it was signed with my development certificate so it's complaining on your Mac.

Can you try this one, which I've stripped the code signature of? If it doesn't work, I'm afraid you'd have to try compiling it yourself (which isn't hard at all, just requires you to download the developer tools).

FruityUI No Codesign.zip

ashaik4 commented 4 years ago

This build worked like a charm. Thank you

edualm commented 4 years ago

Only problem with that build is that it's only a workaround, if it worked then it's probably something around sandboxing, but I can't say for sure what.

I guess I can also release debug builds when I release the next versions.

RubiRubsn commented 3 years ago

Hi, is there a debug build for the new version? im on a mac mini m1 and the no signed version workes like a charm. however i want to use a firefly v2 and by the version in this thred its not supported yet. thanks for the nice work ^^

edualm commented 3 years ago

@RubiRubsn opened issue #36 related to your comment.