starred/ntfy
1
0
Fork 0
mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00
Code Issues 368 Projects Packages Wiki Activity

[GH-ISSUE #230] Android: UnifiedPush registration with Schildichat broken since v1.11.0 #185

New issue
Closed
opened 2026-05-07 00:21:10 +02:00 by BreizhHardware · 12 comments
BreizhHardware commented 2026-05-07 00:21:10 +02:00
Owner
Copy link

Originally created by @binwiederhier on GitHub (Apr 30, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/230

As reported by Jakob on Discord:

This is a log of the ntfy Android app. The log shows up to 1,000 entries.
Server URLs (aside from ntfy.sh) and topics have been replaced with fruits 🍌🥝🍋🥥🥑🍊🍎🍑.

Device info:
--
ntfy: 1.11.0 (fdroid)
OS: 4.14.116
Android: 10 (SDK 29)
Model: HWVOG
Product: VOG-L29EEA

--
Settings:                    
{
  "autoDeleteSeconds": 2592000,
  "autoDownloadMaxSize": 1048576,
  "broadcastEnabled": true,
  "connectionProtocol": "ws",
  "darkMode": -1,
  "defaultBaseUrl": "",
  "lastSharedTopics": [],
  "minPriority": 1,
  "mutedUntil": 0,
  "recordLogs": true
}

Logs
--

1651348085689 2022-04-30 21:48:05.689 D NtfyLog Log was truncated
1651348090103 2022-04-30 21:48:10.103 D NtfyUpBroadcastRecv UNREGISTER received (connectorToken=)
1651348090105 2022-04-30 21:48:10.105 D NtfyUpBroadcastRecv UNREGISTER received (connectorToken=)
1651348090112 2022-04-30 21:48:10.112 D NtfyUpBroadcastRecv Subscription with connectorToken  does not exist. Ignoring.
1651348090112 2022-04-30 21:48:10.112 D NtfyUpBroadcastRecv Subscription with connectorToken  does not exist. Ignoring.
1651348090120 2022-04-30 21:48:10.120 D NtfyUpBroadcastRecv Adding subscription with for app de.spiritcroc.riotx (connectorToken raspberry): Subscription(id=-6776334696088911957, baseUrl=https://ntfy.sh, topic=strawberry, instant=true, mutedUntil=0, upAppId=de.spiritcroc.riotx, upConnectorToken=raspberry, totalCount=0, newCount=0, lastActive=1651348090, state=NOT_APPLICABLE)
1651348090120 2022-04-30 21:48:10.120 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry)
1651348090125 2022-04-30 21:48:10.125 D NtfyUpBroadcastRecv Adding subscription with for app de.spiritcroc.riotx (connectorToken raspberry): Subscription(id=-8361902847137317442, baseUrl=https://ntfy.sh, topic=upA7g3BlRWqyIS, instant=true, mutedUntil=0, upAppId=de.spiritcroc.riotx, upConnectorToken=raspberry, totalCount=0, newCount=0, lastActive=1651348090, state=NOT_APPLICABLE)
1651348090125 2022-04-30 21:48:10.125 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry)
1651348090146 2022-04-30 21:48:10.146 D NtfyUpDistributor Sending NEW_ENDPOINT to de.spiritcroc.riotx (token=raspberry): https://ntfy.sh/strawberry?up=1
1651348090149 2022-04-30 21:48:10.149 D NtfyUpDistributor Sending REGISTRATION_FAILED to de.spiritcroc.riotx (token=raspberry)
1651348090150 2022-04-30 21:48:10.150 D NtfySubscriberMgr Enqueuing work to refresh subscriber service
1651348090152 2022-04-30 21:48:10.152 W NtfyUpBroadcastRecv Failed to add subscription
Exception:
android.database.sqlite.SQLiteConstraintException: UNIQUE constraint failed: Subscription.upConnectorToken (Sqlite code 2067 SQLITE_CONSTRAINT_UNIQUE), (OS error - 110:Connection timed out)
	at android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method)
	at android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId(SQLiteConnection.java:923)
	at android.database.sqlite.SQLiteSession.executeForLastInsertedRowId(SQLiteSession.java:810)
	at android.database.sqlite.SQLiteStatement.executeInsert(SQLiteStatement.java:88)
	at androidx.sqlite.db.framework.FrameworkSQLiteStatement.executeInsert(FrameworkSQLiteStatement.java:51)
	at androidx.room.EntityInsertionAdapter.insert(EntityInsertionAdapter.java:64)
	at io.heckel.ntfy.db.SubscriptionDao_Impl.add(SubscriptionDao_Impl.java:121)
	at io.heckel.ntfy.db.Repository.addSubscription(Repository.kt:72)
	at io.heckel.ntfy.up.BroadcastReceiver$register$1.invokeSuspend(BroadcastReceiver.kt:79)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

1651348090197 2022-04-30 21:48:10.197 D NtfySubscriberMgr ServiceStartWorker: Starting foreground service with action START (work ID: f9011e93-05b9-4914-a418-801d0a681def)
1651348090199 2022-04-30 21:48:10.199 D NtfySubscriberService onStartCommand executed with startId: 12
1651348090199 2022-04-30 21:48:10.199 D NtfySubscriberService using an intent with action START
1651348090202 2022-04-30 21:48:10.202 D NtfySubscriberService Refreshing subscriptions
1651348090203 2022-04-30 21:48:10.203 D NtfySubscriberService - Desired connections: [ConnectionId(baseUrl=https://banana.example.com, topicsToSubscriptionIds={kiwi=-2754791496466822081}), ConnectionId(baseUrl=https://ntfy.sh, topicsToSubscriptionIds={strawberry=-6776334696088911957})]
1651348090203 2022-04-30 21:48:10.203 D NtfySubscriberService - Active connections: [ConnectionId(baseUrl=https://banana.example.com, topicsToSubscriptionIds={kiwi=-2754791496466822081})]
1651348090203 2022-04-30 21:48:10.203 D NtfySubscriberService - New connections: [ConnectionId(baseUrl=https://ntfy.sh, topicsToSubscriptionIds={strawberry=-6776334696088911957})]
1651348090204 2022-04-30 21:48:10.204 D NtfySubscriberService - Obsolete connections: []
1651348090204 2022-04-30 21:48:10.204 D NtfySubscriberService - Match? --> false
1651348090208 2022-04-30 21:48:10.208 D NtfyWsConnection ntfy.sh/strawberry (gid=7): New connection with global ID 7
1651348090210 2022-04-30 21:48:10.210 D NtfyWsConnection ntfy.sh/strawberry (gid=7): Opening https://ntfy.sh/strawberry/ws?since=1651348090 with listener ID 1 ...
1651348090648 2022-04-30 21:48:10.648 D NtfyWsConnection ntfy.sh/strawberry (gid=7, lid=1): Opened connection
1651348090650 2022-04-30 21:48:10.650 D NtfyWsConnection ntfy.sh/strawberry (gid=7, lid=1): Received message: {"id":"y3pWDiMMzjuy","time":1651348090,"event":"open","topic":"strawberry"}
Originally created by @binwiederhier on GitHub (Apr 30, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/230 As reported by Jakob on Discord: ``` This is a log of the ntfy Android app. The log shows up to 1,000 entries. Server URLs (aside from ntfy.sh) and topics have been replaced with fruits 🍌🥝🍋🥥🥑🍊🍎🍑. Device info: -- ntfy: 1.11.0 (fdroid) OS: 4.14.116 Android: 10 (SDK 29) Model: HWVOG Product: VOG-L29EEA -- Settings: { "autoDeleteSeconds": 2592000, "autoDownloadMaxSize": 1048576, "broadcastEnabled": true, "connectionProtocol": "ws", "darkMode": -1, "defaultBaseUrl": "", "lastSharedTopics": [], "minPriority": 1, "mutedUntil": 0, "recordLogs": true } Logs -- 1651348085689 2022-04-30 21:48:05.689 D NtfyLog Log was truncated 1651348090103 2022-04-30 21:48:10.103 D NtfyUpBroadcastRecv UNREGISTER received (connectorToken=) 1651348090105 2022-04-30 21:48:10.105 D NtfyUpBroadcastRecv UNREGISTER received (connectorToken=) 1651348090112 2022-04-30 21:48:10.112 D NtfyUpBroadcastRecv Subscription with connectorToken does not exist. Ignoring. 1651348090112 2022-04-30 21:48:10.112 D NtfyUpBroadcastRecv Subscription with connectorToken does not exist. Ignoring. 1651348090120 2022-04-30 21:48:10.120 D NtfyUpBroadcastRecv Adding subscription with for app de.spiritcroc.riotx (connectorToken raspberry): Subscription(id=-6776334696088911957, baseUrl=https://ntfy.sh, topic=strawberry, instant=true, mutedUntil=0, upAppId=de.spiritcroc.riotx, upConnectorToken=raspberry, totalCount=0, newCount=0, lastActive=1651348090, state=NOT_APPLICABLE) 1651348090120 2022-04-30 21:48:10.120 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry) 1651348090125 2022-04-30 21:48:10.125 D NtfyUpBroadcastRecv Adding subscription with for app de.spiritcroc.riotx (connectorToken raspberry): Subscription(id=-8361902847137317442, baseUrl=https://ntfy.sh, topic=upA7g3BlRWqyIS, instant=true, mutedUntil=0, upAppId=de.spiritcroc.riotx, upConnectorToken=raspberry, totalCount=0, newCount=0, lastActive=1651348090, state=NOT_APPLICABLE) 1651348090125 2022-04-30 21:48:10.125 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry) 1651348090146 2022-04-30 21:48:10.146 D NtfyUpDistributor Sending NEW_ENDPOINT to de.spiritcroc.riotx (token=raspberry): https://ntfy.sh/strawberry?up=1 1651348090149 2022-04-30 21:48:10.149 D NtfyUpDistributor Sending REGISTRATION_FAILED to de.spiritcroc.riotx (token=raspberry) 1651348090150 2022-04-30 21:48:10.150 D NtfySubscriberMgr Enqueuing work to refresh subscriber service 1651348090152 2022-04-30 21:48:10.152 W NtfyUpBroadcastRecv Failed to add subscription Exception: android.database.sqlite.SQLiteConstraintException: UNIQUE constraint failed: Subscription.upConnectorToken (Sqlite code 2067 SQLITE_CONSTRAINT_UNIQUE), (OS error - 110:Connection timed out) at android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method) at android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId(SQLiteConnection.java:923) at android.database.sqlite.SQLiteSession.executeForLastInsertedRowId(SQLiteSession.java:810) at android.database.sqlite.SQLiteStatement.executeInsert(SQLiteStatement.java:88) at androidx.sqlite.db.framework.FrameworkSQLiteStatement.executeInsert(FrameworkSQLiteStatement.java:51) at androidx.room.EntityInsertionAdapter.insert(EntityInsertionAdapter.java:64) at io.heckel.ntfy.db.SubscriptionDao_Impl.add(SubscriptionDao_Impl.java:121) at io.heckel.ntfy.db.Repository.addSubscription(Repository.kt:72) at io.heckel.ntfy.up.BroadcastReceiver$register$1.invokeSuspend(BroadcastReceiver.kt:79) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665) 1651348090197 2022-04-30 21:48:10.197 D NtfySubscriberMgr ServiceStartWorker: Starting foreground service with action START (work ID: f9011e93-05b9-4914-a418-801d0a681def) 1651348090199 2022-04-30 21:48:10.199 D NtfySubscriberService onStartCommand executed with startId: 12 1651348090199 2022-04-30 21:48:10.199 D NtfySubscriberService using an intent with action START 1651348090202 2022-04-30 21:48:10.202 D NtfySubscriberService Refreshing subscriptions 1651348090203 2022-04-30 21:48:10.203 D NtfySubscriberService - Desired connections: [ConnectionId(baseUrl=https://banana.example.com, topicsToSubscriptionIds={kiwi=-2754791496466822081}), ConnectionId(baseUrl=https://ntfy.sh, topicsToSubscriptionIds={strawberry=-6776334696088911957})] 1651348090203 2022-04-30 21:48:10.203 D NtfySubscriberService - Active connections: [ConnectionId(baseUrl=https://banana.example.com, topicsToSubscriptionIds={kiwi=-2754791496466822081})] 1651348090203 2022-04-30 21:48:10.203 D NtfySubscriberService - New connections: [ConnectionId(baseUrl=https://ntfy.sh, topicsToSubscriptionIds={strawberry=-6776334696088911957})] 1651348090204 2022-04-30 21:48:10.204 D NtfySubscriberService - Obsolete connections: [] 1651348090204 2022-04-30 21:48:10.204 D NtfySubscriberService - Match? --> false 1651348090208 2022-04-30 21:48:10.208 D NtfyWsConnection ntfy.sh/strawberry (gid=7): New connection with global ID 7 1651348090210 2022-04-30 21:48:10.210 D NtfyWsConnection ntfy.sh/strawberry (gid=7): Opening https://ntfy.sh/strawberry/ws?since=1651348090 with listener ID 1 ... 1651348090648 2022-04-30 21:48:10.648 D NtfyWsConnection ntfy.sh/strawberry (gid=7, lid=1): Opened connection 1651348090650 2022-04-30 21:48:10.650 D NtfyWsConnection ntfy.sh/strawberry (gid=7, lid=1): Received message: {"id":"y3pWDiMMzjuy","time":1651348090,"event":"open","topic":"strawberry"} ```
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Apr 30, 2022):

As said on Discord, to me it looks like Schildi is sending the same registration twice within 5ms:

1651348090120 2022-04-30 21:48:10.120 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry)
1651348090125 2022-04-30 21:48:10.125 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry)

Looking at https://github.com/binwiederhier/ntfy-android/compare/v1.10.0...v1.11.0 (only BroadcastReceiver and Distributor), it looks like I

(i) got rid of REGISTRATION_REFUSED and replaced it with REGISTRATION_FAILED
(ii) am now catching a SQLConstraintException and sending REGISTRATION_FAILED back. This was to address #185.

My question to the UP guys (@karmanyaahm, @p1gp1g, @sparchatus)

(a) is the way that ntfy behaves (in the latest version, see log) now correct?
(b) are you in touch with the schildi devs to maybe let them know not to send the registration twice?

<!-- gh-comment-id:1114068808 --> @binwiederhier commented on GitHub (Apr 30, 2022): As said on Discord, to me it looks like Schildi is sending the same registration twice within 5ms: ``` 1651348090120 2022-04-30 21:48:10.120 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry) 1651348090125 2022-04-30 21:48:10.125 D NtfyUpBroadcastRecv REGISTER received for app de.spiritcroc.riotx (connectorToken=raspberry) ``` Looking at https://github.com/binwiederhier/ntfy-android/compare/v1.10.0...v1.11.0 (only `BroadcastReceiver` and `Distributor`), it looks like I (i) got rid of `REGISTRATION_REFUSED` and replaced it with `REGISTRATION_FAILED` (ii) am now catching a `SQLConstraintException` and sending `REGISTRATION_FAILED` back. This was to address #185. My question to the UP guys (@karmanyaahm, @p1gp1g, @sparchatus) (a) is the way that ntfy behaves (in the latest version, see log) now correct? (b) are you in touch with the schildi devs to maybe let them know not to send the registration twice?
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Apr 30, 2022):

My guess is that (i) is incorrect, because: same app + same token -> return NEW_ENDPOINT, right?

<!-- gh-comment-id:1114069149 --> @binwiederhier commented on GitHub (Apr 30, 2022): My guess is that (i) is incorrect, because: same app + same token -> return NEW_ENDPOINT, right?
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@karmanyaahm commented on GitHub (May 2, 2022):

My guess is that (i) is incorrect, because: same app + same token -> return NEW_ENDPOINT, right?

Yes, as Sparchatus said in the chat, it should return the same endpoint again if there's another call with same params.

(b) are you in touch with the schildi devs to maybe let them know not to send the registration twice?

@SpiritCroc

<!-- gh-comment-id:1115287924 --> @karmanyaahm commented on GitHub (May 2, 2022): > My guess is that (i) is incorrect, because: same app + same token -> return NEW_ENDPOINT, right? Yes, as Sparchatus said in the chat, it should return the same endpoint again if there's another call with same params. > (b) are you in touch with the schildi devs to maybe let them know not to send the registration twice? @SpiritCroc
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@SpiritCroc commented on GitHub (May 2, 2022):

Hm, if I remember correctly, from @p1gp1g's implementation, it re-registered on every app start. Will have a look when I find time.

<!-- gh-comment-id:1115331032 --> @SpiritCroc commented on GitHub (May 2, 2022): Hm, if I remember correctly, from @p1gp1g's implementation, it re-registered on every app start. Will have a look when I find time.
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (May 2, 2022):

Hi @SpiritCroc nice to meet you :-D

I was going totally insane for a while, because GitHub search doesn't show any results for unifiedpush in the SchildiChat Android repo. Turns out the search is just broken. Good old grep on your repo saved the day.

I briefly looked at the code, but not in an IDE, but it is entirely possible that registerApp is called more than once under certain circumstances. I think I just have to make sure that the BroadcastReceiver on my end is race-safe.

<!-- gh-comment-id:1115461490 --> @binwiederhier commented on GitHub (May 2, 2022): Hi @SpiritCroc nice to meet you :-D I was going totally insane for a while, because GitHub search doesn't show any results for `unifiedpush` in the SchildiChat Android repo. Turns out the search is just broken. Good old `grep` on your repo saved the day. I briefly looked at the code, but not in an IDE, but it is entirely possible that `registerApp` is called more than once under certain circumstances. I think I just have to make sure that the `BroadcastReceiver` on my end is race-safe.
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@SpiritCroc commented on GitHub (May 3, 2022):

Hi @SpiritCroc nice to meet you :-D

Hi :)

I was going totally insane for a while, because GitHub search doesn't show any results for unifiedpush in the SchildiChat Android repo. Turns out the search is just broken. Good old grep on your repo saved the day.

Github search doesn't search code for projects with "fork" status unfortunately.

I briefly looked at the code, but not in an IDE, but it is entirely possible that registerApp is called more than once under certain circumstances. I think I just have to make sure that the BroadcastReceiver on my end is race-safe.

So will SchildiChat need changes, or is it fine as is?

<!-- gh-comment-id:1115844023 --> @SpiritCroc commented on GitHub (May 3, 2022): > Hi @SpiritCroc nice to meet you :-D Hi :) > I was going totally insane for a while, because GitHub search doesn't show any results for `unifiedpush` in the SchildiChat Android repo. Turns out the search is just broken. Good old `grep` on your repo saved the day. Github search doesn't search code for projects with "fork" status unfortunately. > I briefly looked at the code, but not in an IDE, but it is entirely possible that `registerApp` is called more than once under certain circumstances. I think I just have to make sure that the `BroadcastReceiver` on my end is race-safe. So will SchildiChat need changes, or is it fine as is?
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@p1gp1g commented on GitHub (May 3, 2022):

Hi !

Ntfy should resend the new endpoint when it receives a new registration :)

https://unifiedpush.org/spec/android/#orgunifiedpushandroidconnectornew_endpoint

The distributor MUST send this action to the registered application in the following cases:
[...]

  • a registered application sends an action with the intent org.unifiedpush.android.distributor.REGISTER and a token for an existing registration. The distributor MUST also update the features associated with the registration.
<!-- gh-comment-id:1116026373 --> @p1gp1g commented on GitHub (May 3, 2022): Hi ! Ntfy should resend the new endpoint when it receives a new registration :) https://unifiedpush.org/spec/android/#orgunifiedpushandroidconnectornew_endpoint > The distributor MUST send this action to the registered application in the following cases: > [...] > * a registered application sends an action with the intent org.unifiedpush.android.distributor.REGISTER and a token for an existing registration. The distributor MUST also update the features associated with the registration.
BreizhHardware commented 2026-05-07 00:21:11 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (May 3, 2022):

So will SchildiChat need changes, or is it fine as is?
Ntfy should resend the new endpoint when it receives a new registration :)

I mean while I of course agree, I think that the connector should maybe not send the same registration twice within 5ms (see above: 21:48:10.120 and 21:48:10.125). That makes it unnecessarily difficult, since now I have to lock/synchronize around something that happens once every full moon, but then happens twice at the exact same moment :-D

I'll fix it on my end, np.

<!-- gh-comment-id:1116050278 --> @binwiederhier commented on GitHub (May 3, 2022): > So will SchildiChat need changes, or is it fine as is? > Ntfy should resend the new endpoint when it receives a new registration :) I mean while I of course agree, I think that the connector should maybe not send the same registration twice within 5ms (see above: `21:48:10.120` and `21:48:10.125`). That makes it unnecessarily difficult, since now I have to lock/synchronize around something that happens once every full moon, but then happens twice at the exact same moment :-D I'll fix it on my end, np.
BreizhHardware commented 2026-05-07 00:21:12 +02:00
Author
Owner
Copy link

@SpiritCroc commented on GitHub (May 3, 2022):

send the same registration twice within 5ms (see above: 21:48:10.120 and 21:48:10.125)

I see, that indeed sounds unnecessary 🤔

<!-- gh-comment-id:1116065843 --> @SpiritCroc commented on GitHub (May 3, 2022): > send the same registration twice within 5ms (see above: `21:48:10.120` and `21:48:10.125`) I see, that indeed sounds unnecessary :thinking:
BreizhHardware commented 2026-05-07 00:21:12 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (May 3, 2022):

Fixed in github.com/binwiederhier/ntfy-android@821a1ac222 -- this looks like a lot, but it's just a Mutex around the entire register/unregister call. Will be in the next release.

I tested with MacroDroid tapping a floating action button many times. Since that didn't work I added an artificial delay(200) after the exists check and that reproduced the error above.

220503 18-03-19 Selection 001

220503 18-03-37 Selection 001

<!-- gh-comment-id:1116706878 --> @binwiederhier commented on GitHub (May 3, 2022): Fixed in https://github.com/binwiederhier/ntfy-android/commit/821a1ac222ca566b4de68297cafab8aa3bc12748 -- this looks like a lot, but it's just a `Mutex` around the entire register/unregister call. Will be in the next release. I tested with MacroDroid tapping a floating action button many times. Since that didn't work I added an artificial `delay(200)` after the `exists` check and that reproduced the error above. ![220503 18-03-19 Selection 001](https://user-images.githubusercontent.com/664597/166573920-dbafcb15-ea5e-4fd1-b2a1-cb78cd12cc04.png) ![220503 18-03-37 Selection 001](https://user-images.githubusercontent.com/664597/166573934-448090ec-d2b4-4e87-8d59-71182d429524.png)
BreizhHardware commented 2026-05-07 00:21:12 +02:00
Author
Owner
Copy link

@SpiritCroc commented on GitHub (May 22, 2022):

Fixed in SchildiChat now as well, it was indeed trying to register twice when clicking "re-register push distributor" - my fault, sorry.

<!-- gh-comment-id:1133876031 --> @SpiritCroc commented on GitHub (May 22, 2022): Fixed in SchildiChat now as well, it was indeed trying to register twice when clicking "re-register push distributor" - my fault, sorry.
BreizhHardware commented 2026-05-07 00:21:13 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (May 22, 2022):

Nice. Thanks!

<!-- gh-comment-id:1133876479 --> @binwiederhier commented on GitHub (May 22, 2022): Nice. Thanks!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dependabot/npm_and_yarn/web/fast-uri-3.1.2
email-verification
attachment-no-http2
attachment-fixes
attachment-s3
config-generator
postgres-replica
dockers-v2
postgres-support
postgres-webpush+user+message
postgres-webpush+user
postgres-webpush
1364-copy-action
crashfix
user-header
scalar-api-docs
cancel-scheduled
update-available
windows-server
303-update-notifications
postgres
admin-ui
require-login
http-clipboard
message-cache-lock
debian-stripe
predefined-users
busy-timeout
template-dir
ipv6
client-ip-header
apns-fix
feat_optional_require_login
security-updates
pg-message-cache
templating-disallow
templating-3
templating-2
message-size-limit+delay-limit
remove-rate-topics
html-emails
cf-priority
acl-underscores
auth-user-header
markdown
img-attach
web-improvements
utf8-headers
matrix-507-reject
http-response-writer
new-homepage-design
e2e
canary
windows
electron
update-messages
webhook-templating
v2.22.0
v2.21.0
v2.20.1
v2.20.0
v2.19.2
v2.19.1
v2.19.0
v2.18.0
v2.17.0
v2.16.0
v2.15.0
v2.14.0
v2.13.0
v2.12.0
v2.11.0
v2.10.0
v2.9.0
v2.8.0
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.0
v2.1.2
v2.1.1
v2.1.0
v2.0.1
v2.0.0
v1.31.0
v1.30.1
v1.29.1
v1.29.0
v1.28.0
v1.27.2
v1.27.1
v1.26.0
v1.25.2
v1.25.1
v1.25.0
v1.24.0
v1.23.0
v1.22.0
v1.21.2
v1.21.1
v1.21.0
v1.20.0
v1.19.0
v1.18.1
v1.18.0
v1.17.1
v1.17.0
v1.16.0
v1.15.0
v1.14.1
v1.14.0
v1.13.0
v1.12.1
v1.12.0
v1.11.1
v1.11.2
v1.11.0
v1.10.0
v1.9.0
v1.8.0
v1.7.0
v1.6.1
v1.6.0
v1.5.3
v1.5.2
v1.5.1
v1.5.0
v1.4.8
v1.4.7
v1.4.6
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.3.2
v1.3.3
v1.3.1
v1.3.0
v1.2.5
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.0
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
ai-generated

   
android-app

   
android-app

   
android-app

   
🪲 bug

   
build

   
build

   
dependencies

   
docs

   
enhancement

   
enhancement

   
🔥 HOT

   
in-progress 🏃

   
ios

   
prio:low

   
prio:low

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
🔒 security

   
server

   
server

   
unified-push

   
web-app

   
website
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
starred/ntfy#185
No description provided.