Looking at 'About' I see this is version 2.11.1.10973 - I don't recall that version, so perhaps it was updated while charging, and I note that I'm now on android 14 - I'm fairly sure it was on 13 before that security update.
I always hate it when something breaks after two or more things have changed - never know who to blame!
The 2.11.1.10973 version is the one I have and seems to be the latest and so looking at play store was presumably changed on 14 Feb 2024.
I have seen this 'tap to open' issue but it is not occurring at the moment. Unfortunately too many things where happening at the same time that I can not be sure of what caused or fixed the issue, but I have my suspicions that it is related to Bluetooth issues.
Briefly what happened is that my old phone broke and I went into my local Tesco and bought the cheapest Moto G that had Bluetooth and NFC (a G14). It lasted a couple of days before I returned it as it giving constant signal loss errors. I think that it was at this time that I was also getting the 'tap to open' notification, but wasn't paying those too much attention as they were merely annoying when compared with the signal loss problems which were causing real problems.
So instead I got a moto G13 (which I knew worked) and I have had that for about 10 days and it is working well. Both phones are Android 13 and both running the same version of librelink and despite being an older phone the G13 seems to have a newer version of Bluetooth than the G14!
Hence the reasons why I suspect bluebooth issues. I have seen a case where I had the librelink app open and updating every minute and then it displayed a signal loss message and then, perhaps a minute later, it updated the display with a new reading. I did not get any notifications at that time, so it would look like the 'signal loss' notification is not sent immediately, but after a period of time (maybe 15 minutes or so). So it is possible that the 'tap to open' message appears after the signal has been lost and then later it has been found again. (Speculation, but I am trying to think of why the programmers would go to the trouble of coding this notification and the only think I can think of is that they are trying to get you to check your blood glucose now that they are able to tell what it is - but don't actually check how long the signal was lost for.)
Not very helpful, but I was wondering if the messages stop if you disable either the 'signal loss alarm' notification or the 'Errors' notification.