6
61
Fork
You've already forked android
5

Some app registrations no longer possible with 1.2.0 #69

Closed
opened 2025年10月07日 18:00:35 +02:00 by felschr · 3 comments

Since my registrations were all gone after the update (#68), I attempted to re-register my apps.

I do see Sunup's registration toast for new registrations, but when I open the Sunup app afterwards these apps do not show up in the list of registrations.

Not all apps seem to be affected, so far I tested these apps:

  • Failing: Element X, IronFox, FOSS Warn, Moshidon
  • Working: Molly

For Element X specifically, I tried re-registering the app by force-stopping the app and starting it again. This approach worked successfully with 1.1.0. With 1.2.0, I only see Sunup's registration toast on the new start, but Element X does not show up in the list of registrations in the Sunup app afterwards.
Additionally, when using "Troubleshoot notifications" in Element X, the "Test Push loop back" step is now failing (see screenshot).

Since my registrations were all gone after the update (#68), I attempted to re-register my apps. I do see Sunup's registration toast for new registrations, but when I open the Sunup app afterwards these apps do not show up in the list of registrations. Not all apps seem to be affected, so far I tested these apps: - **Failing:** Element X, IronFox, FOSS Warn, Moshidon - **Working:** Molly For Element X specifically, I tried re-registering the app by force-stopping the app and starting it again. This approach worked successfully with 1.1.0. With 1.2.0, I only see Sunup's registration toast on the new start, but Element X does not show up in the list of registrations in the Sunup app afterwards. Additionally, when using "Troubleshoot notifications" in Element X, the "Test Push loop back" step is now failing (see screenshot).
Author
Copy link

I think whether the new registrations fail depends on the way I registered them.

In case of the failing apps, I just started the app (with a force stop beforehand in some cases) and that triggered the registration toast.

For Molly, I went into the settings and switched from UnifiedPush to WebSockets and then back.
My guess is that that properly removed the previous registration and thus the new registration worked.
Perhaps the old registrations might still exist in some broken state due to #68?

I think whether the new registrations fail depends on the way I registered them. In case of the failing apps, I just started the app (with a force stop beforehand in some cases) and that triggered the registration toast. For Molly, I went into the settings and switched from UnifiedPush to WebSockets and then back. My guess is that that properly removed the previous registration and thus the new registration worked. Perhaps the old registrations might still exist in some broken state due to #68?
Owner
Copy link

Fixed with 1.2.1

Fixed with 1.2.1
Owner
Copy link

Thanks for the report

Thanks for the report
Sign in to join this conversation.
No Branch/Tag specified
main
1.2.3-rc1
1.2.2
1.2.1
1.2.0
1.1.0
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
0.2.2
0.2.1
0.2.0
0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Sunup/android#69
Reference in a new issue
Sunup/android
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?