Skip to content
Sunset Beach, NC
Get Support

Troubleshooting

Almost everything that looks broken in Sunset Beach, NC is one of two things: your phone could not reach the backend, or the backend could not reach one of its upstream sources and is telling you so. The app never passes old data off as current — it labels it — so the fix is usually to read the label, check your connection, and pull to refresh. Nothing below needs an account, a login or a reinstall; the app has none of those.

If a symptom is not here, reach the support team with what screen you were on, what it said, what you expected and roughly when, and the app version from More › This app › Version. If a number looked wrong, the Sources screen (More › Sources) and the ⓘ note beside that section say where it came from — mentioning that saves a lot of guessing.

What you seeWhat it meansWhat to do
A full screen reading “Can’t load conditions”, a reason, and a Try again buttonThe app has no saved copy on this phone and its request to sunsetbeach.neuralconfig.com failed or timed out. Requests give up after 30 seconds and the whole attempt after 60.Check you have signal, then tap Try again. Once one load has succeeded the app keeps a copy on disk and shows it on the next cold start instead of this screen.
The reason is “The server sent an error (HTTP 5xx).”The backend answered with an error.Retry in a minute.
The reason begins “Couldn’t read the server’s reply: …”The backend’s payload no longer matches what this build of the app expects. A saved copy that fails to decode is deleted, so this only appears on a fresh load.Update the app from the App Store.
The web page says “Reading the instruments…” for a long time, or “Couldn’t load conditions: …”Same as the app: the page could not fetch the conditions from the backend.Reload; the browser’s own error follows the colon.
BannerWhat it meansWhat to do
”Showing saved data. …”A refresh failed after an earlier successful load. What follows is the network error. Everything on screen is as old as the Updated … time.Pull down on any tab to refresh.
”Saved … Refreshing…”The app drew the copy saved on disk while it waits for the network. It waits for connectivity rather than failing at once.Give it up to a minute or check your signal. If the request then fails, this becomes the Showing saved data banner.

Only a panel that is not live gets a badge, so a badge is information, not noise.

BadgeWhat it meansWhat to do
Cached (clock icon) on a row in Sources, or under the Plan tab’s next visible launchThat upstream could not be reached, and the backend is serving its last known good copy. The Sources row’s detail reads Showing last good reading and says when it was fetched and, under Showing cached data because, why it fell back.Nothing on the phone will fix it — the fault is upstream. The reading is real, just older than usual. See How fresh the data is.
Unavailable (warning triangle)That upstream failed and there is no fallback copy within its window, so the panel is missing or empty.Wait for the source to come back. The Sources row shows the error for that source.
The More tab’s Sources row reads N of N live · N cached · N downSome of the app’s upstream sources (on any tab) are cached or down.Open Sources for the per-row reason.
”Nothing here loaded. Sources shows what went wrong.” on Beach infoThe loaded data carried none of Beach info’s content — very unusual, because most of it is curated on the backend rather than fetched. (With no connection and no saved copy you would see Can’t load conditions instead.)Pull to refresh; if it persists, contact support.
On Sources, the launch source is named “The Space Devs Launch Library 2 (dev mirror — data may lag)“Launch Library rate-limited the backend, so it switched to The Space Devs’ mirror. It does that when the mirror has a current copy and its own copy is out of date, or when it has no copy from the last 7 days at all.Expected under load; launch times may be hours behind. If the launch row reads Cached instead, the mirror had nothing current either, so the app is keeping its own older copy on purpose.
What you seeWhat it meansWhat to do
An error from the source — for example “The source didn’t respond.” — in place of the tide card on WaterCO-OPS predictions could not be fetched and no cached copy exists. The app shows the source’s own error; “No tide predictions available.” appears only when there is no error text.Wait; predictions are cached for 6 hours once they load.
The source’s error, or “Couldn’t read the surf forecast.”, under In the surf on WaterThe NWS surf zone product could not be fetched or parsed.Wait for the next issuance.
”No tide data for this window.” on the tide chartYou are looking at a restored or stale payload whose curve no longer covers now.Pull to refresh.
The source’s error, or “No sunset forecast available.” / “No sunrise forecast available.”, on TodayOpen-Meteo’s sky data is missing.Wait; it refreshes every 15 minutes.
An error from the source under Water › Further out (or, when it gives none, “No offshore forecast right now.”, “No gauge readings right now.” or “No shellfish closures loaded.”)That upstream failed with no cached copy. The text is the source’s own error, such as “The source didn’t respond.”Check the Sources screen.
The Right whales section is not on the Nature tabOut of season and no management area is in force — the section hides itself by design.Not a fault.
Birds says “Not set up” / “Bird sightings from eBird aren’t set up on this server yet.”The deployed backend has no eBird API key. eBird is the only source that needs one.Nothing on the phone; the operator sets the key.
An error from the source in a Nature section (or, when it gives none, “No sightings available.”, “No bird data available.”, “No migration radar available.”, “No turtle data available.” or “No marine life data available.”)That upstream failed with no cached copy. The text is the source’s own error, such as “The source didn’t respond.”Check the Sources screen.
A Nature screen (map, When to go, The year, Sightings, Birds, Migration radar, Fishing) shows Not loaded — “This didn’t load. Go back and pull down to try again.”You reached it (from search, Siri or a link) while that part of the data is missing — its upstream failed, or the saved copy predates it.Go back, pull to refresh, then try again; check Sources.
The migration radar shows a sentence and no numbersNo measurable migration was recorded last night, or no night has been measured yet — the sentence says which. By day the panel still shows last night’s figures.Not a fault.
”Season totals couldn’t be read from the Turtle Watch page.” under Sea turtlesThe Sunset Beach Turtle Watch page couldn’t be read, or changed shape; the season model still shows. (Out of season it reads “Season totals aren’t posted out of season.”, which is not a fault.)If it persists, report it to support.
”Nothing scheduled in the next few weeks.” on PlanNo calendar, concert or launch entries in the next 45 days.Pull to refresh; check Sources.
Some days in Seven days show —That day has no window of the kind you picked. A chip only appears for a kind that occurs somewhere this week.Tap Anything, or another chip.
No Next visible launch cardNo upcoming launch passes the visibility test — launches are still listed as rows.Not a fault. See How the app judges things.
Fishing says “The pier is closed for the winter. This is the season’s last report, not yesterday’s.”The newest pier report is more than ten days old.Not a fault.
”The pier’s daily report couldn’t be read, so nothing here is live. The seasons below are an almanac.”The pier’s RSS feed was unreachable.Wait; check Sources.
”Couldn’t read the list of proclamations in force, so nothing here has been checked against it.”The NC DMF proclamations page was unreachable.Confirm limits against NC DMF before keeping a fish — always.
A “When to go” window reads in season rather than a scoreNothing varied for that occurrence (a turtle hatch window in peak season, for example), so there is nothing to score. Scoring is per window, so the same kind can be scored on another day.Not a fault. See When to go.
Search shows “Nothing for ”…""Nothing in the index — sections, screens, explainers, fish, species, windows, launches or sources — has a word starting with what you typed.Try a shorter word.
The keyboard does not appear when search opensAuto-focus needs iOS 18; on iOS 17 tap the field.Tap the field.

The tide, moon and launch alerts are scheduled on the phone; the “When conditions change” alerts are pushed from the backend and are off by default. The Alerts sheet opens from the bell on Today, Water and Plan, or from the Alerts row on the More tab. Full detail is on Alerts and notifications.

What you seeWhat it meansWhat to do
”Notifications for this app are off in iOS Settings, so none of these alerts can go off.” / “Nothing queued — notifications are off for this app.”You declined the permission prompt. iOS asks only once.Tap Open iOS Settings → Notifications → Sunset Beach → Allow. The app picks up the change when you switch back to it.
”Nothing queued yet. Tap Turn on notifications above.” (or “Turn an alert on and iOS will ask for permission.”)Permission has never been requested.Tap Turn on notifications.
”Nothing queued yet. The app has to load conditions once before it can schedule alerts.”Permission is granted but the app has never loaded a payload.Get online, let it load, reopen Alerts.
”Nothing queued. Every alert is off.”Every scheduled alert (tides, moon, launches) is off. Pushed alerts are never queued on the phone, so this also shows when only pushed alerts are on.Turn one on if you want scheduled alerts; pushed alerts are unaffected.
The queue count falls to zero after a couple of weeks unopenedLocal alerts are built from the last payload; tide predictions run about 15 days ahead.Open the app — every load rebuilds the queue.
Send a test notification is greyed outPermission is not granted.Allow notifications first.
No pushed alerts although the “When conditions change” toggles are onThree possibilities: registration with the push service failed (the Alerts screen then says “Couldn’t register this phone: …” under the toggles), nothing has changed since the first check (the first check after switching on records state and sends nothing), or conditions have simply stayed the same.If it says it couldn’t register, tap Try again. Otherwise remember these fire only on a change — rip risk rising to High, a new advisory, a new spill, a new NWS alert, a spectacular sunset or sunrise.
Tapping an NWS alert push opens the Alerts screen, not TodayThat is where it points.Not a fault.
What you seeWhat it meansWhat to do
A widget reads “No data” with “HTTP 5xx” or “The request timed out.”The widget’s own fetch of its summary failed. It retries in about 10 minutes.Check connectivity. Opening the app and letting it load also asks iOS to refresh the widget (at most every 15 minutes).
A widget shows a score of 88 and “Go. Best for surfing.”That is the placeholder used in the widget gallery and before the first refresh.Wait for the first refresh (up to 30 minutes).
The This week widget says “The week isn’t available yet.”The summary it fetched carried no week of days.Wait for the next refresh.
A small clock icon beside the widget scoreThe summary was built from last-known-good data.Nothing to do; see How fresh the data is.
The launch Live Activity never appearsLive Activities are disabled for the app, the app was not opened during the window (an hour before launch to 15 minutes after), or the launch is not visible from the beach.Enable Live Activities in iOS Settings and open the app inside the window. See Widgets and the launch Live Activity.
The Live Activity reads “Scrubbed — no launch tonight.” or “Holding. …”The backend pushed the provider’s new status.Informational.
What you seeWhat it meansWhat to do
A Siri phrase does nothing, or opens the Today tabThe phrase must include the app’s name; without it Siri has nothing to match.Say the phrase as listed on Siri, Spotlight and Shortcuts.
A Shortcut’s screen parameter shows as broken after an app updateThe section it pointed at no longer exists under that id.Re-pick the screen in the Shortcut.
The share button is missing on Water or PlanWater has nothing to share without a next tide extreme; Plan has nothing without a visible launch or a future event.Expected. See Sharing conditions.
Shared text says As of an hour agoThe stamp is the payload’s own time, and the payload may be last-known-good.Pull to refresh before sharing.
  • Times look off while you are travelling. Every time in the app is the beach’s own (US Eastern), whatever time zone your phone is in.
  • “Water” on Today and “Waterway temp” under Water › Further out › The sound and the ICW differ by several degrees. One is the sea buoy, the other an Intracoastal Waterway gauge about 12 miles away. The swimmer’s number is Today’s.
  • Water quality says “No swimming advisory” but a spill line is showing. Spills are reported between the weekly water samples — that line exists precisely so a clean reading is not taken at face value.
  • Beach cams don’t play inside the app. They open in Safari, and the town’s cam is a still image.
  • There is no live ship position on a map. The app names what a ship probably is from published schedules and links to trackers; it has no vessel layer.