Not receiving push notifications (3a)
-
@azraelpwnz Well you can clearly see that the push client has some issues there, unfortunately idk which. I will ask a bit around whats going on here, maybe we find a clue. Please open a ticket in https://github.com/ubports/ubuntu-push with the last log detail that you uploaded.
-
@flohack will do, thanks Florian!
-
@azraelpwnz @Flohack That should be https://gitlab.com/ubports/core/lomiri-push-service now instead, BTW.
-
@dobey @Flohack issue created:
https://gitlab.com/ubports/core/lomiri-push-service/-/issues/33Let me know if I can be of any help. Trying to get started with contributions, but am just starting out and have only just begun looking through repos.
-
I have the same issue sometimes. I have noticed a pattern that it happens when I am on 4G ... and NOT when I am on 3G ...** even if I have good working connectivity via WIFI and/or 4g cell data **. Very strange. Additionally, (but perhaps unrelated) my SMS only comes in on 3G. I am pretty sure there were some changes in OTA17 related to this ... because my 4G was hard to connect in the past and now it connects regularly. (In the past, it would connect, but then some workaround script would tear everything down to try to start over ... the cycle repeating until eventually it settled showing a good connection, but in reality, it was still missing the proper default route entry in the route table to have anything work. Hope this helps!
-
@standupmobile interesting that you point all of that out.
On OTA16, I forced 3G because I was having issues with 4G...and at that time I had no major issues with consistent SMS. Now I am on solid 4G running OTA17...and can only send....not receive SMS.
As for push notifications...it is odd that you found you had better luck with push notifications on 3G, but not on 4G or even wifi. If I wasnt using my pixel 3a as my DD, and didnt want to risk mucking up my APN and losing 4G...I would totally force 3G to see if push notifications work.
I have been looking through the repos as of late...but have had no major findings that could cause the connectivity check to fail on 4G & wifi, but not 3G.
I did notice the move from TLSv1 to TLS1_2 in this commit, but the connectivity check endpoint is http, not https...so wouldnt think it would matter.
https://gitlab.com/ubports/core/lomiri-push-service/-/commit/7d7f8c2ef4283526587eb496c9964185f46e2f7c -
@azraelpwnz said in Not receiving push notifications (3a):
I did notice the move from TLSv1 to TLS1_2 in this commit, but the connectivity check endpoint is http, not https...so wouldnt think it would matter.
This is in the
mainbranch, which is not what is currently shipped on devices. Theubports/xenialbranch is what is currently being used. And no, the changes inmainwouldn't affect the connectivity check.I wonder if other Halium 9 based devices are also having this issue when on 4G. Perhaps changes to get data working better there, are causing some memory corruption which is causing this failure. @fredldotme might have some insight here?
-
@dobey I figured it wouldn't have a negative effect, but thanks for the clarification on which branch is currently being used!
-
Just to be 100% clear:
3G - Good SMS, good notifications
3G Wifi - Good SMS, good notifications
4G - Inbound SMS not working1, sketchy notifications
4G Wifi - Inbound SMS not working1, sketchy notifications**1 Didn't thoroughly test outbound SMS ...
I am on RC (should be close to OTA17).
I am using as a daily as well (with a few inconveniences)... have flipped back and forth quite a bit recently between 3G and 4G - pretty consistent: you should have no issues getting back to 4G ... would be interesting to confirm my observation...
-
@standupmobile Thank you!!
Set to 3G with wifi on, rebooted...and I now receive notifications!
I then asked someone to send me an SMS...AND YES! I can now send and receive SMS!
Would like to have LTE...but I am fine with 3G and wifi 100%. Love it! Thanks for finding that. Now I can stick with UT for good! You will see me on the OpenStore soon
-
Glad I could help! ... Very weird bug. Now if only we could find a workaround for MMS!
