Skip to main content
← Blog

I Thought Our Notifications Didn't Vibrate — A Hunt That Never Found Its Cause

VauDium·

Mail notifications vibrated and fecit's didn't, or so it felt. I chased the cause with Claude: went through settings, dropped three hypotheses, and ran into an unrelated crash while putting a fresh build on the phone. The cause of the missing vibration was never found.

Today I chased one cause and did not find it. The problem went away anyway. This is the record.

The start

I asked Claude this:

“It’s the same notification, but Mail vibrates and ours doesn’t?”

A little later I added one more line:

“I don’t think I’ve ever seen ours vibrate, in general.”

The code was fine

Claude looked at the server first. Every notification fecit sends from the server goes through one function, and that function attaches the default sound to all of them. On an iPhone, a notification with a sound comes with a vibration. The code that asks for permission and the Android notification channel were fine too.

With nothing wrong on the sending side, we turned to the receiving side: the settings on my phone.

One setting at a time

Claude asked, I looked at the phone and answered, and this went on for a while.

  • Is Sounds turned off for fecit in the notification settings? It was on.
  • What is the Default Alerts sound? Rebound.
  • Is the haptic inside it set to None? It was “Synchronized (Default)”.
  • Is a Focus turned on? No.
  • Do KakaoTalk and Slack vibrate? They did.

Every answer came back normal. Other apps vibrated, fecit did not, and every fecit setting was in order.

Three hypotheses

Along the way three hypotheses came up and were dropped.

First: the default vibration is too weak to notice. The idea was that the vibration paired with the default alert sound is faint. It sounded plausible. So we decided to test whether giving fecit its own notification sound would change the vibration.

Second: the notification arrives silently. This came up when I answered, during a test, that I didn’t think there was any sound either. We put the permission values the app had actually been granted on the screen. Everything was allowed.

Third: a Focus is blocking only fecit. No Focus was on.

A detour — the app won’t open

Testing a custom sound meant putting a new build on the phone. That is where the detour began.

  1. The build failed at signing. The development profile was missing two capabilities the app uses.
  2. Fetching a new profile failed because the account registered in Xcode had been logged out.
  3. After signing in again, the build went through and onto the phone. fecit would not open.

The crash log from the phone showed a reason that had nothing to do with vibration. iOS 27 terminates an app built with the new Xcode right at launch unless it creates its window through the scene life cycle. fecit’s iOS project was still on the old way.

The version that is out now opens without this problem. But had the next build been made with the new Xcode as it was, it would have been an app that closes the moment it opens. Chasing a vibration, we found this first.

The test was wrong

With the app fixed and reinstalled, the testing went on. The test was this: start a task with a planned time of one minute, lock the screen, and watch for vibration when the notification comes a minute later.

After a few rounds I said:

“But I started a one-minute task and locked the screen, and no notification came after that.”

That notification only comes when conditions are met. The task has to be the focused one, and showing elapsed time has to be turned on. If not, there is no notification at all.

So the answers I had given until then, “no vibration”, “I think there was a sound”, “I don’t think there was a sound either”, may have been answers about a notification that never arrived. The three hypotheses were standing on those answers.

And then it vibrated

We changed the test. Opening the app now sent one notification twenty seconds later, no matter what.

It vibrated. Quite strongly.

We tested a notification sent from the server. Sound and vibration came together. I switched to silent and tried again. It vibrated. I put the phone back on the TestFlight version and tried once more. The vibration came through a Focus.

In every case the vibration arrives as it should.

What we didn’t find

We did not find the cause.

The one thing that changed is that the app was installed again. It may have been something that only happened on the install that was on the phone before, but that install is gone and there is no way to check. Not a single line of code related to vibration or notification sound was changed.

The first hypothesis, that the default vibration is weak, collapsed on its own at the end. The vibration that did arrive was not weak.

What’s left

Here is what remains.

  1. It vibrates. I don’t know why it didn’t.
  2. A crash at launch on iOS 27 was found and fixed before the next build.
  3. With a test whose notification only comes under certain conditions, we could not tell “no vibration” from “no notification”. Once the test was changed to one where the notification always comes, the answer showed up on the first try.

If fecit’s notifications arrive without vibration for you, try installing it again from the store without deleting the app. That is the only fix I know of right now.

It was a fun dig in the wrong place.