mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1079] Poblem with updating notifications in the iOS app ntfy 1.3 #758
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#758
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @viniciussgoncalves on GitHub (Mar 31, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1079
🐞 Describe the bug
I'm having trouble receiving notification updates in my app. I'm able to send and receive messages from my ntfy app on my iphone, but I have to keep refreshing the topic for the messages to be updated. I've cleared all the permissions for the app on iOS and I still can't receive the messages.
💻 Components impacted
Own ntfy server, Iphone 15 iOS 17.3.1, app version 1.3 (4)
🔮 Additional context
The problem does not occur when I use my second Android smartphone. I don't have to keep refreshing the topic to receive or send messages and I don't have a problem receiving messages on the smartphone's notification screen.
@wunter8 commented on GitHub (Mar 31, 2024):
To get notifications working on iOS, you need to:
upstream-base-urlis set to "https://ntfy.sh"base-urlis set to your full domain, including "https://" and without a trailing slash (e.g.,https://ntfy.domain.com)base-url)@viniciussgoncalves commented on GitHub (Mar 31, 2024):
Thank you very much! I ended up getting excited when installing and didn't even see this part of the docs. It worked now wunter8.
@adebisi-fa commented on GitHub (Nov 15, 2024):
Will things still work if a device subscribes to a topic on a custom domain while the default server URL is still set to https://ntfy.sh?
@wunter8 commented on GitHub (Nov 15, 2024):
@adebisi-fa I think that will work fine as long as you set the server for that topic to "your full domain, including "https://" and without a trailing slash (it has to exactly match the
base-url)"