hasCustomVibrationsSupport missing

[ItzBubschki]

Version: 3.1.1
Plattform: iOS
iOS Version: 18
flutter version: 3.27.3

Why does the latest version just return a hardcoded false for hasCustomVibrationsSupport instead of calling VibrationPlatform.instance.hasCustomVibrationsSupport() like it used to?

Also it seems like starting a vibration with a custom pattern and intensity does not work anymore and it instead just plays the default vibration with 500ms duration and default intensity.

[benjamindean]

Can you give any code examples? You can always refer to the example app, since most of the cases are there.

[ItzBubschki]

The missing implementation of the function is here

Code example:

final vibrationSupport = await Vibration.hasCustomVibrationsSupport();
print("vibrationSupport: $vibrationSupport");

used to print true now prints false.

Code example for custom vibration pattern:

await Vibration.vibrate(pattern: [150, 150, 150], intensities: [75, 0, 75]);

used to work now just vibrates once (probably 500ms long since that is the default value)

[benjamindean]

That's a mistake on my side - will fix soon. But what about the second case with intensities that you've mentioned?

[benjamindean]

The patterns do work fine for me - just tested it out.

[benjamindean]

In your example, you wait for 150ms, then vibrate for 150ms and then wait for 150ms again. The first argument is always wait.

[ItzBubschki]

Hey thanks for fixing the missing hasCustomVibrationsSupport so quickly.
Regarding the vibration pattern i have found some strange code in the iOS handler.
Up until now I am using version 2.0.1 of this package and there the code i supplied works fine on iOS.
However in the latest version in the getIntensities method the supplied intensities are completely disregarded and replaced with a new value.
This is because of this line of code at

flutter_vibration/vibration/ios/Classes/VibrationPluginSwift.swift

Line 90 in ec05ec0

return pattern.enumerated().map { $0.offset % 2 == 0 ? 0 : amplitude }

So no matter what you supply as intensities e.g. [100, 0, 100] it will be transformed to [0, 255, 0](considering that no amplitude was supplied and it uses the default value of255`).
I think this line of code was meant to look like this:

return intensities.enumerated().map { $0.offset % 2 == 0 ? 0 : $0.element }

This would keep the supplied intensities and still turn every even indexed element into a pause.

[benjamindean]

Yes, you're absolutely right about intensities. I probably forgot to revert it after the testing (the only available type of testing for this plugin is manual, unfortunately).

About the order in pattern: In iOS’s Core Haptics framework, when creating a custom haptic pattern using CHHapticPattern, the sequence starts with a “pause” value. Same goes for Android. Hence the change.

[benjamindean]

I made these changes because there were too many bug reports about pattern or duration not working at all. That's why I decided to implement as many fallbacks as possible.

Anyways, will fix it ASAP.

[ItzBubschki]

Alright thank you very much :)