Page 1 of 1

Apple M1 Problem

Posted: Fri Jul 01, 2022 6:48 am
by janherzog
Hey,

I just downloaded Daslight 4 for Mac and tried to open it. At that point where the Startup screen says "done", the application crashes. I thought it might be related to my processor, which is the Apple Silicon M1.

Anyone else having this issue?

Re: Apple M1 Problem

Posted: Mon Jul 04, 2022 7:47 am
by TomHat
Hello,

Please download the latest Beta and let me know if this one works better.

Regards,

Re: Apple M1 Problem

Posted: Tue Jul 12, 2022 10:54 pm
by janherzog
Hey,

I just downloaded the latest Beta from 13. June. But if I download it and open the Image and inspect the .app File I get a File, which was last modified on the 13. June. Seems right. But when I install the App and open Daslight4, I get the following output:
Image

It seems like the Beta version for Apple is the wrong one.

Kind Regards,
Jan

Re: Apple M1 Problem

Posted: Wed Jul 13, 2022 8:38 am
by TomHat
Hello,

I'm glad if it works better.
Yes it turned out the version label is wrong. The version was built in june, but the date information was not updated. This detail was missed, but the build is correct.

Regards,

Re: Apple M1 Problem

Posted: Thu Aug 11, 2022 6:29 pm
by antoinediev
Hi,

I struggle with this problem to.
Daslight is freezing at the "done" phase.
Using the beta from 2022-07-22 and tried 2022-07-13 version. Using M1 silicon to.

Re: Apple M1 Problem

Posted: Fri Aug 12, 2022 8:24 pm
by antoinediev
Hey,

I've done several tests today and I can affirm that the problem occurs when my computer has an internet connection. When he's off line I can use daslightt normaly.

Re: Apple M1 Problem

Posted: Thu Aug 18, 2022 7:57 am
by suzannedalton
Yes, the version number is incorrect. The version was built in June, but the date information was not updated. This detail was overlooked, but the build is correct.drift boss

Re: Apple M1 Problem

Posted: Thu Dec 01, 2022 8:39 am
by antoinediev
In my case the problem was my company proxy & vpn who was blocking the opening request. By disabling it solved the problem