HapTic | : crossed_fingers : Use iOS Hap Tic API easily with Swift | iOS library

I am using Alamofire to make an API request to insert user data to my database, if the user email is exist, the response will return

I've got a Git repo of Markdown articles, where people create pull requests (one per Markdown article) that eventually get merged to master and then, working directly on master, I move that article into a folder called wordpressed and commit and push to master.

And I've got a very old pull request that is still sitting there in a branch called home-base, consisting of a file dan/homebase.md which I'm thinking of editing into shape with some more commits and then merging to master.

This home-base branch is so old that the repo, seen from its point of view, is totally different from how it looks today in master. So I thought it might be good to reverse merge master into home-base just to bring it more up to date and move the merge base up a lot.

But when I try to do that, I get a merge conflict that I can't understand.

To show you the situation, I'm going to show what a ls of files and folders looks like in each branch. I'll start with master:

There is an easy way to present a context menu in iOS 13/14 via UIContextMenuInteraction:

Just got this message from Apple this morning:

I have an app that is using BLE connectivity with my device. Everything works from connecting to the device, discovering the services, writing the characteristic and descriptor. But for some reason, onCharacteristicChanged is not triggering. The goal is to retrieve the data from the characteristic that is in the characteristic. I have tried using a different characteristic from the same service and this works as in retrieving the data. Not sure why this specific characteristic is not working when others are.

Here is my code: //Descriptor public final static UUID UUID_CLIENT_CHARACTERISTIC_CONFIG = UUID.fromString(GattAttributes.CLIENT_CHARACTERISTIC_CONFIG);

I'm creating an app in which I want to utilise Xamarin.Forms' haptic feedback feature. This feature is currently under preview - so I went to the Microsoft documentation and got it setup as expected.

First of all - in my AssemblyInfo.cs in my Android project I added the following code:

[assembly: UsesPermission(Android.Manifest.Permission.Vibrate)]

Then I pasted in the following code from Microsoft into my code-behind:

HapticFeedback.Perform(HapticFeedbackType.Click);

After adding the code I get the following message:

Steps to reproduce

1. Open up a new project and under the Android AssemblyInfo.cs add the following code: [assembly: UsesPermission(Android.Manifest.Permission.Vibrate)]

2. Paste in the following code: HapticFeedback.Perform(HapticFeedbackType.Click);

Now you should notice that intellisense says that HapticFeedback does not exist in the current context.

Things I've tried

1. I tried to update Xamarin.Forms and Xamarin.Essentials - but it still was not recognised for some reason

2. I tried to close and reopen the solution - but it sitll was not recognised.

I am looking for a solution to this so I can use haptic feedback in my application.

Image

Depending on what I do I either get

"No such audio device"

if I leave determining my audio device up to SDL2 or I get

Failed loading libasound.a: /home/aypahyo/.conan/data/libalsa/1.2.4///package/d48130e0dd76369b1338deb3b2372c5a649f9f2d/lib/libasound.a: invalid ELF header

when I set SDL_AUDIODRIVER=alsa. (The error message is actually cut off, I added an r at the end).

Here is an implementation that shows the error:

I was having a problem getting one of my programs that uses SDL to compile so to fix it I reinstalled SDL2 and SDL2Image following this link: https://solarianprogrammer.com/2015/01/22/raspberry-pi-raspbian-getting-started-sdl-2/ I used this link before and have created windows and renderers successfully. Now the program compiles and runs but I get the error

I am experiencing no haptic output while testing the code below on my physical device (iPhone XR). I followed Apple Developer's "Playing a Single-tap Haptic Pattern" article, as well as double-checked with various other articles on the internet, and I am confident I have implemented it correctly. Moreover, there are no errors that are caught when running. What could be the reason why my device is not outputting the haptic pattern?

Side Notes:

1. I can confirm that my phone does produce haptics for other apps, so it does not appear to be an issue with my physical device.
2. I also implement an AVAudioPlayer separately; I doubt that would interfere, but I thought I'd mention it just in case.

Any help would be much appreciated--thanks!