I think its to do with the component I forgot to specify as a pre-req:
https://github.com/opensource-socialnetwork/UnreadMessagesCountAPI

Came from this discussion:
https://www.opensource-socialnetwork.org/discussion/view/4639/message-notifications
Could you try installing this and testing again?

I will incorporate this API extension into Web Chat so that it's not needed in future.

A bit of background - this provides the number of notifications from each user. It compares that number against the previous number - if the number goes up, it checks whether there is an unread message icon. If there's not, it'll add the icon AND play a sound and then refresh #contacts (this puts most recent contacts at the top).

Also, when checking for new notifications, if the message is from somebody you are currently chatting with - it only updates the main message thread #messages. If there is a new message from somebody else, it just refreshes #contacts.

All the verifications are done using the above component, so that would explain the unwanted behaviour (UnreadMessagesCountAPI).

Have to revert "flawlessly"
messages are indeed saved correctly now, but window of chat partner isn't updated (message not shown)
(running Edge <-> Chrome on Windows 10)

Thanks Arsalan, i'll look at changing that.

Its possible i've missed a pre-requisite... one of you guys kindly gave me a component that extends the API:
Custom API method for total unread messages count 1.0

This allows me to check unread message counts, and handles the notifications properly - so you dont get that beeping every time it polls. I'll resolve that by incorporating that component into my own chat_api.php.

I also have an issue where the ossn* functions don't seem to work in my second page? I have added the following lines to both the webchatpage.php and chat_api.php files:

$apiKey = ossn_services_apikey();
$siteURL = ossn_site_url();

file_put_contents ("api_log.txt","chat_api.php : API KEY : " . $apiKey . PHP_EOL,FILE_APPEND);  
file_put_contents ("api_log.txt","chat_api.php : SITE URL : " . $siteURL . PHP_EOL,FILE_APPEND);    

and the output I get is:

chatapi.php : API KEY :
chatapi.php : API KEY :
webchatpage.php : API KEY : d30de045bb6d5ff11cdec4e68d... (correct key)
webchatpage.php : SITE URL : http://10.48.1.28/
chatapi.php : API KEY :
chatapi.php : SITE URL :

Any troubleshooting suggestions?

Sorry, my fault: I missed setting the site in 1.1
Running 1.2 now, it's working flawlessly with

$apiKey = ossn_services_apikey();
$siteURL = ossn_site_url() . 'api/v1.0/';
error_log('key: ' . $apiKey . ' site: ' . $siteURL);
$recentURL = $siteURL . 'message_recent?';
$listURL = $siteURL . 'message_list?';
$userURL = $siteURL . 'user_details?';
$notifcountURL = $siteURL . 'unread_mesages_count_custom?';

without any hardcoded vars.

BTW, you may use ossn_dump instead of print_r or var_dump
like error_log('blabla ' . ossn_dump(array_of_interest));

I found one issue; when i receive message it keeps playing ping sound i and it never going off.
Besides that if you planning to use it as OSSN component then I suggest you to use input() function instead of $__POST

Sorry, updated OssnServices on community :)

I appreciate the feedback thanks :)

I'll look into better integration, I needed to not have any of the OSSN menus/displays etc - and just wanted a screen on the mobile that was purely for one function. I tried using css to hide things, but it was getting messy. Felt like a cleaner way would be to have its own page entirely.

Another issue was that without a clean page, it was appending the CSS to the site wide CSS, which prevented me from doing two things:

1. Resetting CSS so that there was nothing quirky to troubleshoot on different devices
2. Applying styles without being very granular - without the granularity, the main OSSN site was being restyled. :-(

The issue you are getting I was able to reproduce when I used the ossnservicesapikey() and ossnsiteurl() functions in the chat_api.php.

What you are seeing on screen when you hit the SEND button, the javascript is just placing the message on screen so that it appears quickly, and the page doesn't need to re-load. At the same time it POSTs the same data to the ChatAPI.php - which in turn uses the OSSN API to submit the new message. If the message appears on screen, but disappears when you refresh, it means the chatapi failed to submit the new message to the OSSN API - which I think (though i'm not entirely sure?) is because the chatapi.php file doesn't seem to be getting anything from ossnservicesapikey() or ossnsite_url(). I can tell that file to write out the results of those functions to a log file to check if thats the case.

If you manually enter your API key and site_url, does it post the messages properly? I've been able to use three browsers (chrome / chrome incognito / edge) and have two distinct conversations going with notifications sounds and new message icons :)

Ok, got it running meanwhile.
1. No problem here retrieving the key like $apiKey = ossn_services_apikey(); in both files.
2. new messages don't seem to be saved
I can see the lines I entered with OssnMessages


but the new line I entered via webchat disappears after refreshing the webchat page

Anyway, I think that any further development based on polling once per second can't be a solution, it should use a service worker indeed, as you mentioned already.
Next - instead of setting up a completely new page (that takes about 3s to load here) - you should try to use as much of the already loaded Ossn framework as possible, instead of fetching jquery, fonts and stuff again.
Finally ... all this wasn't meant to sound discouraging. Right the opposite, I'm excited we have a new developer who's willing and able to really dig into things and I'm looking forward for the next release.

Ok great thank you. I missed those when I was adapting the HelloWorld plugin. I've now removed all custom function names and references to drop "OSSN" and moved the menu registration into the init function.