No longer working with Macos 15

[HiimHyy]

I have recently updated my mac to sequoia, the app stopped working and no longer pause at 80%, It asked me to perform Onboarding every time i reopen it.

[plyght]

same issue here; also stuck on initializing mode on sequoia.

[Eirperuier]

same here

[plyght]

@rurza any updates?

[rurza]

Thanks for reporting the problem. I won’t bother spending time testing it on macOS 15.0 until beta 3.

[rurza]

I've double checked – there is no changes in APIs I'm using, which means it's a bug on macOS. I'll schedule a call with Apple to discuss it.

[Xytronix]

[rurza]

@Xytronix @plyght Can you send me a screenshot from the System Settings -> Login Items?

[plyght]

@Xytronix @plyght Can you send me a screenshot from the System Settings -> Login Items?

@rurza I think part of the issue is that Sequoia keeps removing the "allow in background" thing you have to enable during the setup of BatFi. Screenshot BatFi "allow in background" should be here

[plyght]

I've double checked – there is no changes in APIs I'm using, which means it's a bug on macOS. I'll schedule a call with Apple to discuss it.

@rurza Any updates on the call w/ Apple?

[mcernohorsky]

thanks for looking into this

[rurza]

Hey!

We should wait for the next macOS beta. The engineer I spoke with was well-prepared and aware of some issues in the current seed.

But...

Did you install the macOS beta on a separate volume? I did, and I experienced the same issues you mentioned. However, the app suddenly started working. To be honest, I don't know how I resolved it. Initially, I thought it was due to some changes I made in the XPC connection, but that wasn’t the case because the existing version of the app works as well. My guess is that it started working because I deleted the other copy of the app that was on the separate volume. Maybe this will work for you?

[plyght]

Hey!

We should wait for the next beta. The engineer I spoke with was well-prepared and aware of some issues in the current seed.

But...

Did you install the macOS beta on a separate volume? I did, and I experienced the same issues you mentioned. However, the app suddenly started working. To be honest, I don't know how I resolved it. Initially, I thought it was due to some changes I made in the XPC connection, but that wasn’t the case because the existing version of the app works as well. My guess is that it started working because I deleted the other copy of the app that was on the separate volume. Maybe this will work for you?

@rurza That seems odd to me as the External volume shouldn't have access to the other, and shouldn't change anything (as far as I know). I did not install Sequoia onto a separate volume, so I cannot attempt the fix you described.

[rurza]

Actually, it's completely normal and expected behavior that an OS has access to other mounted volumes (for example, to index them). It's definitely not a trivial topic to determine what the system should do in some edge cases. Unfortunately, apps like BatFi are at a disadvantage. From Apple's perspective (and the best proof is the direction they chose for their newer platforms), the user shouldn't have to give admin permission to some third-party app in the first place. But here we are :)

Anyway, I've released a new beta. I highly recommend it. It should fix all the issues I know of from the release 2.0.0, and it works on my machine :D

[plyght]

Actually, it's completely normal and expected behavior that an OS has access to other mounted volumes (for example, to index them). It's definitely not a trivial topic to determine what the system should do in some edge cases. Unfortunately, apps like BatFi are at a disadvantage. From Apple's perspective (and the best proof is the direction they chose for their newer platforms), the user shouldn't have to give admin permission to some third-party app in the first place. But here we are :)

Anyway, I've released a new beta. I highly recommend it. It should fix all the issues I know of from the release 2.0.0, and it works on my machine :D

@rurza Weird! you learn something new everyday. I'll try out that new beta when I get home. Thanks for being responsive and helpful.

[plyght]

Actually, it's completely normal and expected behavior that an OS has access to other mounted volumes (for example, to index them). It's definitely not a trivial topic to determine what the system should do in some edge cases. Unfortunately, apps like BatFi are at a disadvantage. From Apple's perspective (and the best proof is the direction they chose for their newer platforms), the user shouldn't have to give admin permission to some third-party app in the first place. But here we are :)

Anyway, I've released a new beta. I highly recommend it. It should fix all the issues I know of from the release 2.0.0, and it works on my machine :D

@rurza BatFi 2.0.1 Beta did not fix the issue on my machine.

[plyght]

Actually, it's completely normal and expected behavior that an OS has access to other mounted volumes (for example, to index them). It's definitely not a trivial topic to determine what the system should do in some edge cases. Unfortunately, apps like BatFi are at a disadvantage. From Apple's perspective (and the best proof is the direction they chose for their newer platforms), the user shouldn't have to give admin permission to some third-party app in the first place. But here we are :)

Anyway, I've released a new beta. I highly recommend it. It should fix all the issues I know of from the release 2.0.0, and it works on my machine :D

@rurza BatFi 2.0.1 Beta did not fix the issue on my machine.

@rurza just following up on this to check for any updates.

[rurza]

@plyght

We should wait for the next beta.

[plyght]

@plyght

We should wait for the next beta.

I see. wait for the next MacOS beta. Makes sense! Thanks for reminding me.

[cinestl]

Hi guys! By any chance did you find a way to fix it on Sequoia Version 15.0 Beta (24A5264n)?

upd: I have beta 2.0.1 of BatFi upd: IC that we need to wait till new beta comes out, just was curious maybe there is a workaround)

[plyght]

Hi guys! By any chance did you find a way to fix it on Sequoia Version 15.0 Beta (24A5264n)?

upd: I have beta 2.0.1 of BatFi

upd: IC that we need to wait till new beta comes out, just was curious maybe there is a workaround)

@cinestl as of now, no one (to my knowledge) has a workaround.

[cinestl]

I got it to work - I am using the 1st DB and I clicked DENY on the prompt (Bat-fi added items that can run in the bg) , and then allowed inside of system settings separately , it works like a charm for me now. @plyght @rurza

Did you uninstall the app or just closed and launched?

Cuz I just have this thing that does nothing for me =(

[rurza]

Exactly, that’s the core of the issue: the daemon responsible for matching the app with the helper has a bug. I am experiencing the same issue that @cinestl described. The helper is displayed instead of the app and is marked as “from an unidentified developer.” If @cinestl quits System Settings and then opens Login Items again, the “garbage collection” mechanism deletes this entry.

The app worked for me for a while, but then it stopped. I have restarted the OS and used sfltool resetbtm numerous times, to the point where I’m unsure what, if anything, actually helped. As of now, I still have no solution.

[cinestl]

I got it to work - I am using the 1st DB and I clicked DENY on the prompt (Bat-fi added items that can run in the bg) , and then allowed inside of system settings separately , it works like a charm for me now. @plyght @rurza

Did you uninstall the app or just closed and launched? Cuz I just have this thing that does nothing for me =(

Can't you just turn it on?

Yeah, I've enabled it, and after I close Settings, it disappears as @rurza mentioned before, so no luck here

[GavinMcNabb]

I can confim that this has been resolved in Beta 2. You do have to go through the onboarding one time but it'll stick on reboot.

[cinestl]

Yeah MacOS Beta 2 rules! You just need to manually enable thing in Login items and reboot your mac, tho I'm using beta update of BatFi)

[Xytronix]

indeed fixed it #close