π’ #FOSSWarn 1.0.1 is now on F-Droid.
-
π’ #FOSSWarn 1.0.1 is now on F-Droid. This release addresses some issues with the push-notification setup and fixes some bugs.
One crucial bug fix was related to the coordinates of the subscription bounding box. The coordinates (after a subscription has expired and the resubscribe feature was used) might be swapped (so lat is long instead). Please check your subscription and remove it if it is incorrect, and re-add the place. You can check the bounding box by pressing the icon to the left of the place name.
Other improvements are:
- a notification self-check feature
- an easy check to switch between distributors
- bug fix with a parser error with biwapp alertsRead the the full release note here:
https://github.com/nucleus-ffm/foss_warn/wiki/Release-notes-for-FOSSWarn-1.0.1 -
π’ #FOSSWarn 1.0.1 is now on F-Droid. This release addresses some issues with the push-notification setup and fixes some bugs.
One crucial bug fix was related to the coordinates of the subscription bounding box. The coordinates (after a subscription has expired and the resubscribe feature was used) might be swapped (so lat is long instead). Please check your subscription and remove it if it is incorrect, and re-add the place. You can check the bounding box by pressing the icon to the left of the place name.
Other improvements are:
- a notification self-check feature
- an easy check to switch between distributors
- bug fix with a parser error with biwapp alertsRead the the full release note here:
https://github.com/nucleus-ffm/foss_warn/wiki/Release-notes-for-FOSSWarn-1.0.1@foss_warn Seems like this release broke compatibility with #Conversations_im again?
Previously this was due to the relatively long URLs that Conversations uses but I was under the impression that this had been fixed.
-
@foss_warn Seems like this release broke compatibility with #Conversations_im again?
Previously this was due to the relatively long URLs that Conversations uses but I was under the impression that this had been fixed.
@daniel @foss_warn I can confirm, that there are problems with conversations. Selftest keeps failing π
-
@daniel @foss_warn I can confirm, that there are problems with conversations. Selftest keeps failing π
-
@foss_warn @schlumpf timeouts? Not sure what that could be. I donβt have a rate limiting mechanism that would lead to timeouts.
Can you reach the redirect when you GET / on up.conversations.im? Generally GETs to the endpoint URL should get you a version number.
What about other hosts on that machine like https://gultsch.de
-
@foss_warn @schlumpf timeouts? Not sure what that could be. I donβt have a rate limiting mechanism that would lead to timeouts.
Can you reach the redirect when you GET / on up.conversations.im? Generally GETs to the endpoint URL should get you a version number.
What about other hosts on that machine like https://gultsch.de
@daniel @schlumpf Mh ok, I checked the server logs, and it seems like we are getting 404 responses here. Can this be related to deleted registrations for push notification on your server? So, if a user registers and later removes their registration, and we attempt to send a notification to that user, do we receive 404 responses in that case?
-
@daniel @schlumpf Mh ok, I checked the server logs, and it seems like we are getting 404 responses here. Can this be related to deleted registrations for push notification on your server? So, if a user registers and later removes their registration, and we attempt to send a notification to that user, do we receive 404 responses in that case?
@foss_warn endpoints expire on Conversations so a certain number of 404s is probably expected. However if you try with a new region in FOSS warn expiry can be ruled out as a reason.