Troubleshooting
If something is not working, start with the steps below. A feed is the list of new articles or episodes a website publishes; you may see these called RSS or Atom feeds. You usually need only the website's public address to add one.
If you cannot find the issue, check the matching feature guide or contact support. Do not delete app files, reinstall, or reset STIQRA to fix a storage warning unless support has helped you confirm that is safe.
The Feed keeps loading at launch
STIQRA shows Loading… with a spinning wheel while preparing articles, including when it needs more time to verify which articles may safely appear. You can try a different section and return later. When the current section has finished loading and all its articles have been archived or otherwise excluded, it shows its usual empty state instead of a loading spinner.
If Loading… persists, contact support. STIQRA keeps active articles hidden until Archive and other visibility checks succeed; a loading wheel does not mean your articles or Archive have been lost. Do not delete archive files or reset the app to clear a loading screen.
Subscriptions temporarily unavailable
If Source Settings → Subscriptions shows Subscription storage unavailable, STIQRA cannot safely read your saved list of websites. It has not replaced that list with an empty one. Try again when storage is available. If the message says the data came from a newer STIQRA version, update the app first. Do not delete stored subscription files manually.
Some older subscriptions may need you to choose Validate before they can refresh again.
A feed will not add
- Open Settings → Source Settings → Subscriptions and paste the site's public HTTPS website address, or its direct feed address, into Find Sources or Add Feed.
- If STIQRA finds several lists of articles, choose the one you want.
- If validation fails, check the message and try another public feed address provided by the publisher. Sites that require sign-in, private network addresses, or pages that show their feed only after running website scripts are not supported.
STIQRA follows only permitted publisher redirects and does not ask you to approve each one. A site loading in your browser does not necessarily mean STIQRA can safely add its feed.
Common messages include:
- Response too large, unsupported content, parse failure, or a parser-work limit: the feed could not be read safely. This can happen with very large podcast lists; it does not prove the feed is empty. STIQRA does not download podcast audio merely because you added the feed.
- Parser-helper runtime, helper reply size, or helper unavailable: processing could not finish. Retry later, or report the error to support if it persists.
- The publisher's feed redirect could not be approved or The destination could not be verified as public HTTPS: the feed address or a redirect did not meet STIQRA's public-website checks. A working browser link does not override those checks.
- HTTP-only item destination: the feed contains article or audio links that do not meet the required HTTPS policy.
- Secure connection: the connection failed; check your network or try later.
- Duplicate: that source is already listed. Save failure: the new subscription could not be stored.
A podcast is listed but shows no episodes
First check the source's enabled status, Feed cutoff, and other filters. A feed may legitimately have no episodes, or it may contain only older items. Turning off the cutoff can reveal older items that were already received; it cannot recover episodes the publisher did not supply.
A parser-work, parser-helper reply limit, or parser runtime limit error means STIQRA could not read the full feed. Try an explicit Refresh for a longer check. If it still fails, contact support or ask the publisher for a compatible public HTTPS feed. A feed with HTTP-only item destinations may list episodes without providing secure links STIQRA can use.
STIQRA can recognise an episode from a supported HTTPS audio link even when it has no separate article webpage. Audio is downloaded only when you ask to play or download it, not when you subscribe. A listed episode does not guarantee that the publisher's audio is still available. A private audio transfer error points to STIQRA's media-handling step; a publisher response error concerns the publisher's response. Neither message is a reason to bypass the app's security checks.
A feed is listed but cannot be enabled
Imported sources, sources from older builds, or sources that failed validation can remain visible without being allowed to refresh. Open Source Settings → Subscriptions, then the source's Security details to see its status. For a public source, choose Validate and follow the result.
An imported source does not become approved merely because it was in a backup. Older installations may require you to validate or re-add sources. If a source was saved by a very old version and is no longer listed, re-add the website or import it from a trusted OPML file. A rejected or private destination remains blocked.
An OPML import skipped or rejected entries
Review the OPML result sheet. Parsing is non-mutating and returns one result for every outline, including folders, missing/invalid URLs, feed-limit overflow, duplicate URL/identity groups, unsafe/unsupported entries, and selectable pending entries. Nothing is saved until you select entries and choose Import Selected.
Import never contacts an origin or grants authority. Selected feeds remain pending with their valid title/folder information. Bounded namespaced security metadata may be preserved and exported again, but it is inert; imported approval or redirect declarations cannot enable refresh. Use Validate to perform fresh local validation after you explicitly choose an imported source. Do not weaken URL, destination, redirect, size, MIME, or parser checks to force an import.
Why can't I add a newsletter?
Newsletter signup, adding newsletter sources, importing .eml files, and mailbox/forwarding integrations are not supported. Source Settings intentionally does not contain a Newsletters page. An email address or downloaded email message cannot be used as a subscription. When a publisher offers a separate public HTTPS RSS or Atom feed, add that feed through Source Settings → Subscriptions instead.
A feed refreshes but shows no new articles
STIQRA contacts each enabled RSS/Atom feed directly under its exact user-approved public-HTTPS capability rather than routing normal reading through an XMAKYNA fetch service. No-new-article behaviour usually comes from the publisher feed, your local settings, or shared provider infrastructure used by the publisher.
Possible causes:
- The feed has no new items.
- Articles are older than your feed cutoff.
- The source is disabled for the current section.
- Keyword, language, or NLP filters hide the items.
- The articles are already read and you are in unread-only mode.
- The feed is failing intermittently.
Check Feed Stats, Filtered, Archive, and Source Settings → Subscriptions. On iPhone and iPad, the small arrow beside the item count spins during a feed check and stays still if durable articles are still awaiting safe list publication. The status sheet separates New stored (durably added keys) from New found (a narrower filtered count); a lower visible Feed count is not necessarily a failed download. Slower sources may deliver separate batches while other feeds are still running; those batches are coalesced for smooth list updates. If several unrelated-looking sources fail together, they may share a CDN, DNS provider, hosting company, or bot-defence service.
A source is stale, rate limited, or failing
Open Feed Stats and select the source. Source availability is durable and does not require fetch audits. It shows the last success/attempt, next automatic check, publisher retry deadline, effective origin, bounded failure category, automatic/manual-only mode, and whether last-known-good local articles remain usable.
- Stale means the source has not produced a recent successful update under its current cadence.
- Temporarily failing covers a bounded current network, HTTP, policy, or first invalid/parse failure.
- Rate limited means a valid publisher 429/503 retry deadline is active. STIQRA applies it to known sibling feeds on that origin and preserves it across restart; manual refresh cannot bypass it.
- Authentication required means the publisher requires access that this release does not support. Correct the URL or disable/remove the source.
- Redirect failure means the publisher redirect chain was malformed, unsafe, or exceeded the bounded hop limit. Retry when offered or correct the saved feed URL.
- Invalid feed means repeated bounded parsing/format failures; correct the URL or disable/remove the source.
- Refresh permission mismatch means STIQRA stopped the refresh because the request did not match the saved source permission or public-HTTPS request rules. Use Retry now first. A valid public HTTPS feed should not require another approval; if the state persists, review the saved URL or report the source.
- Disabled means refresh is off for that source; re-enable it in Source Settings → Subscriptions.
Use Retry now only when it is offered. A bad response does not erase existing local articles. Image failures are separate and do not make the feed source unavailable.
An article image is missing or blank
A publisher can declare several image candidates for one article. STIQRA does not treat an explicitly declared video/audio/document Media RSS entry as an image merely because its MIME type is omitted, so a real publisher thumbnail can remain the image candidate. If an actual image candidate is permanently unusable (for example, the publisher returns HTTP 404/410 or secure image validation rejects its bytes), STIQRA can move to the next bounded feed-declared candidate. Temporary network/download failures remain retryable instead of skipping the candidate immediately. Every fallback candidate is still subject to the same public-HTTPS, size, format, quarantine, and decode checks. When a later app version changes the secure image validator, an older quarantine decision is rechecked in a bounded one-at-a-time path instead of permanently pinning that image to the old decision.
If every candidate is unavailable or rejected, the article remains readable without an image. An HTTP 404/410 for an image URL means that publisher image resource is unavailable; it does not make the feed itself unavailable.
A publisher image can also be valid but too small for crop-to-fill on a particular surface. In the compact Feed list, STIQRA keeps a usable low-resolution image by fitting it inside the existing thumbnail tile at no larger than its decoded size; the image may therefore appear smaller inside the tile instead of being stretched or replaced by a blank placeholder. Images that are intrinsically too small or invalid remain rejected. On iOS Card and Overlay, a small but valid publisher image that does not fit an already reserved photo area appears in a shorter, compact card with the headline and summary shown only once beside a safely sized thumbnail. This confirmed mismatch can shorten that card; ordinary image loading does not resize it. The publisher image is never enlarged beyond its approved quality.
An article disappeared
Look in these places:
- Clear search.
- Switch from unread-only to all items.
- Check Saved if you saved it.
- Check History if you opened it.
- Check Archive if you archived it.
- Check Filtered if filters may have hidden it.
- Turn feed cutoff Off temporarily.
Search finds too little
Clear other narrowing controls. Search combines with current section, cutoff, filters, source visibility, read state, and archive state.
Try a shorter search term or the original article title.
Search finds too much
Use more specific terms, phrases, company names, source names, or distinctive words. For recurring noise, add keyword filters instead of relying on search every time.
Track is noisy
Make the tracked term more specific. Add context words, use a distinctive phrase, or archive irrelevant matches. If one source causes most noise, adjust source visibility or filters.
Track misses articles
Check spelling, variants, filters, source visibility, feed cutoff, read state, and Archive. Search manually for the term to confirm whether the article exists locally.
A background refresh error is truncated
Use Show full error in the refresh-failure banner to expand the complete selectable message. A newly displayed background-refresh failure posts one assistive announcement; expanding, re-rendering, or leaving the same failure visible should not announce it continuously. After a hard failure, a later refresh that succeeds for at least one feed posts a recovery announcement, even when the earlier banner was dismissed. The dismiss control closes the banner without retrying; Escape or the cancel action also dismisses the current banner on macOS and supported iOS hardware-keyboard paths. Transient feedback banners have separate follow-up and dismiss controls, so activating the banner background does not silently run an action. If the full message or dismiss control is unreachable, the same failure repeats announcements, or a later distinct failure or recovery is silent, record the exact screen, OS build, keyboard model/layout, and active accessibility settings.
Images do not appear
Possible causes:
- The article has no usable image.
- The image URL is broken.
- The publisher blocks image loading.
- The image failed validation.
- Image-only layout settings are hiding articles without images.
- Network conditions are slow.
Try switching to List layout to confirm the article exists without relying on image loading. When an article declares several supported images, article detail can try the next declared candidate after a terminal failure; manually selecting a gallery image takes precedence. Unavailable-image messages identify verified HTTP, source-size or decoder-resource causes when known. In article detail, open the image failure details and choose Retry; assistive output should first say retry is in progress and then report the actual repeated failure or recovery. Repeating the same failure without a deliberate retry should not continuously announce it. STIQRA may avoid images that use an unsafe or non-public URL, redirect unsafely, connect to a private or unverifiable destination, are malformed, unsupported, oversized, repeatedly failing, or unsafe to display. A normal public image host does not need to be prelisted, and ordinary bounded baseline or progressive JPEG files should pass secure ingress. An origin-policy or decoder-policy rejection for an otherwise safe public image indicates a regression rather than an expected publisher/CDN approval step.
Publisher media is missing or was omitted
Open the article detail and look for Publisher media. The section appears only when the feed supplies a supported public HTTPS enclosure or media entry. STIQRA can omit an entry when the URL is private/local or malformed, the declared type is unsupported, the MIME type conflicts with the file extension or Media RSS medium, the entry duplicates another enclosure, or the feed exceeds bounded metadata limits. The article text remains available and the section summarises omission reasons when possible.
Supported publisher audio offers an explicit local download and native queue. A failure message distinguishes unsupported/type-mismatched media, unsafe address, size or quota limits, the two-transfer concurrency limit, low storage, authentication, publisher rate limiting, unavailable media, network restrictions, cancellation, and generic network/storage failure. Retry only after addressing the message; the app does not retry in the background. Downloaded publisher audio does not appear in the generated-audio library, but it can play through the same mini player and queue. Video and other publisher resources still open externally.
A publisher audio download will not start or play
Publisher redirects can be followed only within a limited public HTTPS route. A redirect refusal is different from an unsupported response type or an invalid audio file. An unsupported response-type message means the server did not identify its response as supported audio; it does not prove that the episode's feed declaration disagreed with downloaded audio. An HTML error page or a generic binary response is not accepted as audio. Network or helper interruption also remains separate from a content rejection.
Confirm the item is an audio episode with a supported public HTTPS address and a compatible type/file extension. Downloads can be rejected when the publisher changes MIME type, the file exceeds 512 MiB, the publisher-audio store would exceed 1 GiB or 100 files, device storage is low, authentication is required, the server is rate limiting, or the network policy cannot verify a public destination. Delete an older publisher download to free quota. A cancelled or failed download leaves no playable partial file.
If a previously downloaded item no longer plays, it may have expired after 30 days without use, been removed with its source, been deleted by Delete All, or failed local decoder validation. Download it again from article detail or invoke a publisher-audio row action, which downloads explicitly before playback or queueing. The full player may report that source metadata is unavailable when the local audio still exists but its active/archived article record does not. Remote streaming and range playback are not supported in this release. Native chapter seeking and publisher video are also not supported.
Badges look wrong
Badges count visible unread items for a specific section. Counts can change because of read state, filters, archive, source visibility, feed cutoff, search, and layout-specific image filters. Unread, filtered, source-health, playback, image-failure, and refresh-failure states also use distinct symbols or text, so a missing colour difference should not hide the state. If the symbol, label, outline, or recovery control is missing, record the exact screen and active accessibility settings.
Open the section and clear narrowing controls to compare.
Translation is unavailable
Translation can depend on platform support, installed languages, and article content. Check language settings and confirm the article has enough text. Article-card, feed-selection, primary-selection, cluster, and article-detail translation sheets should expose a labelled language picker, reachable Translate/Cancel actions, Escape dismissal, and vertical reflow at large accessibility text sizes. On iOS, article-detail translation should expand to a large sheet instead of clipping. Report the exact surface, device orientation, keyboard behaviour, and text size if any contract fails.
Audio generation is unavailable
Audio features can depend on platform, build configuration, selected voices, and local speech capabilities. Confirm that Audio appears in your build and that articles are selected. The mini-player and transcript expose visible play, seek, speed, transcript, and dismiss controls and should reflow at accessibility text sizes; no dismissal should require only a swipe gesture.
AI actions are missing
AI features are feature-gated. Standard builds may not include ChatGPT, local analysis, or report-related actions.
ChatGPT does not open after copying
Open ChatGPT manually and paste the copied prompt. STIQRA keeps the prompt on the clipboard and shows a recovery notice when it cannot open ChatGPT after trying the supported app targets. On macOS, this can also appear when ChatGPT for Mac is not installed.
If STIQRA says it couldn’t copy the prompt, try the action again before opening ChatGPT. STIQRA does not try to open ChatGPT when the prompt was not copied.
A .stiqrareport file does not import
Select the report file again and retry the import. STIQRA checks the file you selected before importing it; existing reports already stored in the app are unaffected.
XMAKYNA support asks for an error code
Open Settings → Security & Privacy → Diagnostics. Diagnostics is off by default, so enable it only when you want STIQRA to keep the bounded local app-health evidence needed to reproduce or inspect a problem. Reproduce the failure, return to Diagnostics, and use Refresh Console.
The console is user-inspectable and records only fixed support codes, fixed summaries, app version/build, and aggregate counts. It does not include timestamps, feed addresses, article identifiers/content, URLs, CloudKit account/record/zone identifiers, credentials, request/response bodies, arbitrary error text, or device/user identifiers. Nothing is sent automatically. Your reading stays private. Diagnostics does not include your feeds, article content, reading history, or reading habits. If XMAKYNA support asks for it, use Copy Diagnostics to copy the complete report, review the copied text, and send it using your normal communication method. Turn Diagnostics off afterwards if you no longer need it; doing so removes the local diagnostics log.
How to read a Diagnostics line
A copied line has this shape:
[STIQRA] STQ-NET-DNS | app=1.2.3 (456) | count=2 | A network host name could not be resolved.
| Part | Meaning |
|---|---|
[STIQRA] | The component that produced the bounded support code. The console can also show secure-ingress or cloud-sync component labels. |
STQ-NET-DNS | The stable support code. This is the most useful value to quote to XMAKYNA support. |
app=1.2.3 (456) | The STIQRA release and build that recorded the failure. It helps distinguish a regression in one release from a failure that persists across releases. |
count=2 | How many times the same component/code/summary combination was recorded for that release/build. It is an aggregate count, not an activity timeline. |
| Final text | A fixed, package-owned summary. It is not the publisher response body, a system error description, or arbitrary error text. |
The prefix identifies the likely boundary before support inspects anything else:
| Prefix | Likely boundary | What it tells you |
|---|---|---|
STQ-PUBLISHER-* | Publisher/feed | The publisher returned a client-side HTTP response, deferred a retry, rate-limited access, or supplied feed data STIQRA could not safely accept. |
STQ-SERVER-* | Publisher server | The remote server returned an HTTP 5xx response. |
STQ-NET-* | Network/TLS/DNS | The request failed before STIQRA obtained an acceptable publisher response. |
STQ-CLIENT-* | STIQRA/client input | STIQRA encountered invalid local request input or an otherwise unclassified client-side failure. |
STQ-STORAGE-* | Local storage | A critical app-owned local-storage operation failed. |
STQ-DIAG-* | Diagnostics store | The optional local Diagnostics store itself could not be opened, validated, read, or written safely. |
XSIO-* | External-content validation | STIQRA rejected unsafe, invalid, unsupported, or oversized external input. |
XCS-* | iCloud/cloud sync | The cloud-sync layer reported a bounded failure category and the operation in which it occurred. |
STIQRA feed, network, client, and storage codes
These are the STIQRA-owned codes currently written by the Diagnostics implementation. HTTP codes include the actual bounded status number returned by the HTTP layer.
| Code | Meaning | Likely interpretation |
|---|---|---|
STQ-PUBLISHER-HTTP-<400...499> | The publisher returned an HTTP 4xx response. | The request reached the publisher, but the publisher rejected it or the requested feed resource is unavailable under that HTTP status. |
STQ-SERVER-HTTP-<500...599> | The publisher server returned an HTTP 5xx response. | The request reached the remote service, but the server or gateway failed while handling it. |
STQ-HTTP-<status> | An unexpected HTTP status did not fit the normal 4xx/5xx failure groups. | Support should inspect the numeric HTTP status and app version. STQ-HTTP-0 means the status supplied to the classifier was outside the accepted 100...599 range. |
STQ-PUBLISHER-RATE-LIMIT | Feed processing reported publisher rate limiting. | The publisher is asking clients to slow down; this is not evidence of a local database or parser crash. |
STQ-PUBLISHER-RETRY-DEFERRED | STIQRA already has a bounded publisher retry deferral in force. | The feed is being deliberately held until its retry policy permits another normal attempt. The deadline itself is not stored in Diagnostics. |
STQ-PUBLISHER-FEED-PARSE | The returned feed could not be accepted by the bounded RSS/Atom parser. | The document was invalid, unsupported, too large/complex, or otherwise failed safe feed parsing. |
STQ-PUBLISHER-FEED-RESPONSE | The HTTP response was unsuitable before normal feed parsing. | Examples include an empty or oversized body, unsupported content encoding/MIME type, an unrecognised feed document, or inconsistent not-modified semantics. |
STQ-CLIENT-FEED-URL | A feed URL supplied to the feed parser was invalid. | The local/client request could not form a valid feed destination. |
STQ-CLIENT-FEED-LIMIT | A configured feed-response byte limit was invalid. | This indicates a local configuration/programming boundary rather than publisher content. |
STQ-NET-OFFLINE | The operating system reported no usable network path for the request. | The device was offline, data was unavailable, or roaming policy prevented data use. |
STQ-NET-TIMEOUT | The network request timed out. | The destination did not complete the request within the allowed time. |
STQ-NET-DNS | The host name could not be resolved. | DNS lookup or host discovery failed before a connection was established. |
STQ-NET-CONNECT | A connection could not be established or was lost. | The host could not be reached or an established network connection dropped. |
STQ-NET-TLS | The secure connection or certificate check failed. | TLS negotiation, trust, certificate validity, or client-certificate handling prevented a secure connection. |
STQ-NET-REDIRECT | The network stack could not safely complete a redirect. | The redirect chain was invalid, excessive, or pointed to a destination that could not be followed. |
STQ-NET-OTHER | Another bounded network error occurred. | The failure was network-related but did not fit the more specific offline, timeout, DNS, connection, TLS, or redirect groups. |
STQ-CLIENT-URL | The network layer rejected a bad or unsupported URL. | The client-side destination was invalid before a useful publisher response was obtained. |
STQ-CLIENT-UNCLASSIFIED | The feed request failed with an error outside the known bounded groups. | Quote the code and app version/build to support; Diagnostics deliberately does not copy the arbitrary underlying error string. |
STQ-STORAGE-BOOTSTRAP | STIQRA could not complete critical local-store bootstrap. | A local persistence store failed during app composition/startup. This is not a publisher or network failure. |
STQ-DIAG-PATH | The Diagnostics directory failed its local safety check. | The local Diagnostics path was not a safe ordinary app-owned directory, so the store refused to load it. |
STQ-DIAG-SCHEMA | The Diagnostics file did not match the accepted bounded schema. | The saved file had an unsupported schema, too many entries, or an invalid entry and was rejected rather than trusted. |
STQ-DIAG-READ | The Diagnostics file could not be read or decoded safely. | The optional diagnostics file was unavailable, unreadable, oversized, or malformed. |
STQ-DIAG-WRITE | The Diagnostics file could not be persisted safely. | Recording stopped rather than pretending the diagnostic was durably saved. |
For HTTP codes, the number is meaningful. For example, STQ-PUBLISHER-HTTP-404 means the publisher returned 404 Not Found for that request; STQ-PUBLISHER-HTTP-410 means 410 Gone; STQ-PUBLISHER-HTTP-429 means 429 Too Many Requests; and STQ-SERVER-HTTP-503 means 503 Service Unavailable. The code identifies the failure boundary and response status; it does not identify which feed produced it.
XSIO-* secure-ingress codes
XSIO-* codes identify a category of external-content validation failure, such as an invalid URL, file, or image. They do not include the rejected content, its URL, or its local file path. Some codes add a more specific reason, such as XSIO-INVALID-IMAGE-JPEG-EOI-PREMATURE, without disclosing the image itself.
| Code or family | Meaning |
|---|---|
XSIO-DENIED | Secure ingress denied the requested operation under its policy. |
XSIO-FILE-TOO-LARGE, XSIO-REMOTE-TRANSPORT-TOO-LARGE | Input exceeded the configured byte budget. |
XSIO-NOT-REGULAR-FILE, XSIO-SYMBOLIC-LINK-REJECTED, XSIO-HARD-LINK-REJECTED, XSIO-DIRECTORY-REJECTED, XSIO-HIDDEN-FILE-REJECTED, XSIO-EXTENSION-REJECTED | The selected filesystem object was not acceptable for the secure file-ingress policy. |
XSIO-INVALID-TEXT, XSIO-INVALID-UTF8 | Text input was invalid or was not valid UTF-8. |
XSIO-INVALID-URL | The secure URL boundary rejected the destination. |
XSIO-MALFORMED-JSON, XSIO-MALFORMED-XML, XSIO-XML-RESOURCE-LIMIT-EXCEEDED | Structured data was malformed or exceeded the bounded XML resource policy. |
XSIO-REMOTE-RESPONSE-REJECTED | A remote response failed secure-ingress response validation. |
XSIO-UNSUPPORTED-MEDIA-TYPE[-<detail>] | Media type/signature/format policy rejected the input. A fixed detail suffix can further identify the package-owned reason. |
XSIO-INVALID-IMAGE[-<detail>] | Image structure or canonicalisation failed safe validation. A fixed detail suffix can identify the rejected structural stage, format, or parser condition. |
XSIO-IMAGE-PIXEL-BUDGET-EXCEEDED, XSIO-IMAGE-DIMENSION-EXCEEDED | Image dimensions exceeded the configured safety budget. |
XSIO-QUARANTINED | Secure ingress blocked a source that is temporarily quarantined after a prior qualifying failure. |
XSIO-CLIPBOARD-DENIED, XSIO-CLIPBOARD-VALUE-TOO-LARGE, XSIO-CLIPBOARD-EXPIRED | The secure clipboard policy rejected, bounded, or expired the value. These are framework classifications and are not currently emitted by the feed-fetch bridge. |
XSIO-HANDOFF-REJECTED, XSIO-EXPIRED, XSIO-INVALID-REQUEST-ID, XSIO-APP-GROUP-UNAVAILABLE | A secure handoff could not be validated or completed. These are framework classifications and are not currently emitted by the feed-fetch bridge. |
XSIO-FILESYSTEM-RACE-SAFETY-UNAVAILABLE | The secure file boundary could not establish the required race-safe filesystem binding. |
XSIO-IO-FAILURE | Secure ingress encountered a bounded local input/output failure. |
XSIO-PLATFORM-UNSUPPORTED | The requested secure operation is unavailable on the current platform. |
The framework has more specific fixed image/media detail suffixes than are practical to list as separate user actions. They all preserve the same interpretation: the secure-ingress boundary rejected the content at a named validation stage without embedding the content, path, URL, or decoder-provided text in the support code.
XCS-* cloud-sync codes
Cloud-sync failure codes use this shape:
XCS-<CATEGORY>-<OPERATION>[-CK<number>]
The first token says why the sync operation failed, the second says which sync operation was active, and the optional CK<number> suffix is the bounded numeric CloudKit error classification supplied by Apple's framework. It is not an account, record, zone, or device identifier.
| Category | Meaning |
|---|---|
XCS-RETRY-* | Temporary network/service condition; normal retry policy owns the next attempt. |
XCS-CONFLICT-* | A record conflict occurred and is handled by sync policy. |
XCS-ACCOUNT-* | The current iCloud account state could not be used. |
XCS-PERMISSION-* | iCloud permission or account policy blocked the operation. |
XCS-QUOTA-* | iCloud storage quota blocked the operation. |
XCS-ZONE-* | The private sync zone was unavailable, changed, missing, or otherwise required zone handling. |
XCS-RESET-* | CloudKit reported an encrypted-data reset that requires recovery. |
XCS-STATE-* | Sync state became invalid and needs reconciliation or recovery. |
XCS-LOCAL-* | The sync layer could not durably update local sync state. |
XCS-TERMINAL-* | A non-retryable transport failure occurred. |
| Operation token | Operation |
|---|---|
START | Sync startup. |
RECON | Reconciliation. |
STATE | Sync-state persistence. |
FETCH | Fetching cloud changes. |
SEND | Sending pending changes. |
APPLY | Applying fetched records to app-owned state. |
RESULT | Handling sent-record results. |
RSAVE | Saving a cloud record. |
RDEL | Deleting a cloud record. |
ZSAVE | Saving/creating the private sync zone. |
ZDEL | Deleting the private sync zone. |
For example, XCS-RETRY-FETCH-CK3 means the cloud-sync layer classified a fetch failure as temporary/retryable and retained CloudKit error classification 3 for support. XCS-PERMISSION-SEND-CK<number> means the send operation was blocked by the bounded CloudKit classification carried with a permission failure. The numeric suffix is diagnostic classification only; the console never stores CloudKit record, zone, or account identity.
What a code does not prove
A support code identifies the boundary and bounded failure class; it is not a complete root-cause verdict. STQ-NET-DNS, for example, tells support that host-name resolution failed for a request, but intentionally does not record the host. STQ-PUBLISHER-HTTP-404 proves that the request received HTTP 404, but intentionally does not record the feed address. XSIO-* tells support which secure-ingress policy rejected work without retaining the rejected content. XCS-* identifies sync category and operation without retaining cloud identity.
That trade-off is deliberate: the console is intended to answer “publisher, server, client, network, secure ingress, cloud sync, or local storage?” while keeping the diagnostic record unsuitable for reconstructing what the user was reading or when they were active.
Feed Stats is empty
Feed Stats can list your sources even when detailed fetch records are off. If no sources appear, check Source Settings → Subscriptions. If sources appear but their connection details are empty, turn on Enable fetch audits and refresh normally. Only future refreshes are recorded; STIQRA does not contact websites just to fill in the statistics. Disabled or blocked sources can still be listed even though they are not being refreshed.
If an image, report, or feed is rejected, treat that as a boundary decision rather than a prompt to bypass validation. Use an official public HTTPS feed URL, review image quarantine diagnostics before sharing them, and import reports only from trusted sources.
The app feels cluttered
Try this reset-free cleanup sequence:
- Set a shorter feed cutoff.
- Disable low-value feeds.
- Add a few keyword filters.
- Use Track for must-follow topics.
- Archive old or irrelevant articles.
- Use For You for focused reading.
Use Delete All Data only when you intentionally want to remove app-owned data. When an iCloud sync copy exists, choose Delete From This Device to leave that cloud copy intact or Delete Everywhere to request deletion of both local data and STIQRA's private iCloud sync zone. The app reports incomplete local deletion or a pending cloud deletion instead of claiming success early; platform backups and copies you exported elsewhere remain outside the reset.
iCloud Sync status and recovery
Open Settings → Security & Privacy → iCloud Sync and check the status shown there:
- Sign in to iCloud: sign in to the account you want to use for syncing.
- Waiting for iCloud: STIQRA is waiting for account confirmation or the service. Leave sync on while it completes setup.
- Temporary iCloud delay: iCloud has asked STIQRA to retry later. You do not need to toggle sync or reset your data.
- Restart STIQRA: quit and reopen the app before enabling sync again. This does not delete your iCloud copy.
- Account review required: the iCloud account has changed. Keep sync off or review the choice to use the current account with your local data; STIQRA does not merge cloud accounts automatically.
- Recovery required: choose Keep Local Data & Turn Sync Off to preserve the copy on this device. If offered, Retry Local Sync Metadata checks local records without erasing the cloud copy. Reset Cloud From This Device replaces that cloud copy and can lose changes that exist only on another device or in iCloud; use it only after reviewing your data.
- Cloud Deletion Pending: a requested cloud deletion is not yet complete. Keep the matching iCloud account signed in when possible. STIQRA blocks ordinary cloud restoration while the deletion is pending.
For account restrictions, insufficient iCloud storage, or permission errors, resolve the account issue before retrying. Temporary network or service failures do not require a data reset. See iCloud Sync for what syncs, account changes, and deletion choices.
Source order looks unexpected
Check the active Source order mode at the top of the Sources list. Pins remain first in every mode. Unread uses visible unread articles, Attention needed prioritises durable source-health warnings, and Signal-to-noise is a local visible-versus-hidden estimate. Choose Alphabetical to return to name order or Manual order to use your saved arrangement.
If selecting a source opens the wrong website after sorting, report it as a bug. Changing the sort order should not change which source opens.
Clusters show fewer articles than the main list
Check Timeframe at the top of Clusters. Yesterday means the previous calendar day; Last 24 hours is a rolling 24-hour period. The displayed scope count reflects the chosen date range and current visibility/Archive exclusions, not the entire chronological feed. The Only >1 version, Track and Top Keywords choices can narrow the visible groups further. Choose All time to remove the date filter and Recompute clusters to recalculate relationships. Opening Clusters alone does not mark articles read; article and group commands remain explicit.
A cluster is wrong
Refresh Clusters to recompute relationships from the current article scope. Same-event coverage is limited to reports no more than seven days apart, but distinct developments and shared themes can connect older stories when several informative subject terms recur. Generic categories alone do not qualify. Look under Themes & developing stories as well as Same-event coverage; use the displayed scope count to check whether feeds or filters restricted input. Only >1 version hides individual articles, not threads or themes. Track, keyword, search, and archive rules still affect visibility. There is no manual cluster-editing workflow.
Clusters are still computing or show no stories
Check the selected timeframe and any active filters, then choose Recompute clusters. Building relationships may take a moment. Clusters use the article text supplied by each publisher, not text extracted from linked webpages. If no stories appear, check your filters, Archive, and selected dates instead of deleting articles. Clusters do not automatically send article content to an external AI service.
The reader says no readable text was supplied
The publisher may have supplied only a title, metadata, or media in its RSS/Atom item. No readable text supplied is a source limitation, not a failed webpage extraction. Open the canonical article link when you choose to leave STIQRA; the app does not render or silently scrape the remote page in the native feed reader.
An article image or gallery failed
Open the image failure details to see what happened. If Retry image is available, try it after checking your connection. Some images are blocked because the file or its website does not meet STIQRA's safety rules; retrying cannot override those rules. You can still read the article text and see its source, or turn images off in Image Settings.
An old article opens after relaunch
Current STIQRA builds do not persist or restore the last-open article or its reading position. Killing or relaunching the app must not reopen an article merely because it was open previously. Explicit incoming links or app activations can still open a named item. Retired reading-continuity snapshots from older builds are removed during startup, and there is no Reset reading positions control in current builds.
A feed will not enable
A free account can keep up to 5 active refreshable sources you add. If Source Settings → Subscriptions reports 5 of 5 refreshable feeds enabled, enabling another refreshable source requires Premium or an available slot. Disable or remove an active source, then try again. Pending, failed, non-refreshable, and already-disabled records do not consume the allowance.
If a downgrade leaves more than 5 active sources, STIQRA preserves the complete list. You can still disable or remove sources to reduce usage; the app does not silently delete grandfathered subscriptions.
A login-protected feed will not validate or refresh
STIQRA does not support authenticated RSS/Atom feeds. There is no feed Authentication editor or a way to save a feed username/password or bearer token. A response with HTTP 401, sign-in required, or credentials required means the publisher's feed cannot be used in STIQRA as-is. HTTP 403 means the publisher denied public access. Use a publisher-provided public HTTPS RSS/Atom URL instead; re-adding the same login-only URL or retrying refresh cannot bypass the publisher's access rules.
This applies even if an older STIQRA build stored feed or article-page credentials: current builds ignore those credentials for network access. Delete All Data also clears obsolete Keychain credentials.
The article is shorter than the publisher webpage
Sometimes a publisher provides only a short summary in its list of new articles (called an RSS or Atom feed). STIQRA shows the text the publisher supplies; it does not fetch the full article from the publisher's webpage. To read more, choose to open the original article in your browser. There is no article-text extraction setting to turn on.
A feed fails behind a proxy, VPN, filter, or captive portal
If you are on a network that requires a browser sign-in, finish that sign-in outside STIQRA. If you use a VPN or network filter, try a trusted connection that allows the publisher's public HTTPS website, or ask your network administrator to check access.
After a normal refresh, Feed Stats → Connection may show Proxy reported, Direct reported, or Route unknown when fetch audits are enabled. These labels are clues, not proof of how every request travelled. STIQRA has no proxy editor and does not bypass network restrictions. Private or local-network source addresses are not supported.
A portable backup may contain a private feed URL
Portable backups exclude known credential fields and Keychain secrets, but they preserve exact feed locators. Some publishers place opaque access tokens in unusual paths or query fields that cannot be safely identified without breaking the subscription. Treat the backup as sensitive, review exact URLs during import preview, and revoke or replace a publisher-issued locator when exposure is suspected.
Custom Backup imported subscriptions or keywords are missing
In Settings → Data Management → Custom Backup, check that Filters and Track settings was selected in Additional data when exporting, and was still selected in the import review. The review shows the total number of archived keywords. The default Merge selected archive values adds the selected backup keywords alongside local keywords; Keep existing local values deliberately skips an archived list when its local list is already nonempty. Track keyword entitlements can limit what is restored.
Newly imported sources can be enabled during import by leaving Validate and enable all newly imported subscriptions selected. Sources that fail security validation or exceed the active-source allowance remain disabled. After an earlier or interrupted restore, use Validate and enable all pending subscriptions in Custom Backup to retry pending sources in a bounded batch; no backup carries network permission.
Custom Backup import did not complete
Open Settings → Data Management → Custom Backup. If STIQRA could not read the selected backup, choose Import Custom Backup… again and select the file. If STIQRA reports an interrupted import, choose Resume interrupted import. Keep the original backup file and do not edit STIQRA's application data. If the problem continues, contact support before trying a reset.
Images are temporarily unavailable
An image may stay blank temporarily while STIQRA prepares or checks it. Wait a moment, then try Retry image if that option is available. If the problem continues, check your connection and Image Settings. STIQRA will not load an image that fails its safety checks, but you can still read the article without it.
STIQRA stops during local storage checks
STIQRA checks its private storage before opening local stores. If a diagnostic directory cannot be checked safely or its maintenance limit is exceeded, startup stops instead of continuing with uncertain storage. Keep any existing custom backup safe, including older Full Recovery Archive files, and report the startup failure to support. Avoid manually deleting application data or changing folder permissions as a first troubleshooting step.
Several transfers fail while other work is running
If many network or media transfers are already running, STIQRA can temporarily refuse another request. Wait for existing work to finish, then retry the transfer. This protects the app from accumulating more waiting work than it can handle.
Premium plans do not load or a purchase is pending
Open Settings → STIQRA Premium and use Retry if monthly/yearly plans are not currently available. Product names and prices come from the App Store, so STIQRA does not substitute a guessed price when the storefront cannot be reached or a configured product is unavailable.
If a purchase is pending, wait for the App Store account approval or payment process to complete and reopen the Premium page later. Cancelling a new purchase or receiving a purchase error does not by itself remove an existing active Premium entitlement. If you previously subscribed with the current App Store account but Premium is not active, use Restore Purchases. Use Manage Apple Subscriptions for individual-plan changes or cancellation. If your access was assigned by an organisation, contact its administrator about assignment changes instead of purchasing a second seat.
A billing grace period can keep Premium active until its verified grace end. A non-grace billing-retry state pauses paid actions until the App Store reports an entitled subscription again. If STIQRA cannot verify StoreKit temporarily, any offline Premium access is limited to a short last-verified window rather than being granted indefinitely.
A single article's image shows a specific reason
If the image container says Publisher image not found (HTTP 404) or (HTTP 410), the selected image link returned that status; a later publisher correction or declared alternate image may succeed. Image exceeds allowed dimensions and Image exceeds decoder resources mean the original exceeds an image policy or current safe decode resources; the app may use an explicitly supplied smaller rendition, but it never overrides the isolated helper memory limit to force the original. Image temporarily unavailable typically points to a network, timeout or helper problem; use the available retry affordance when appropriate. Image destination blocked indicates an unsupported or unsafe image destination. The article text should still be accessible.
Under Feed Stats → the affected feed → Image hygiene, inspect the distinct-article image availability counts, cause breakdown and score contribution for the last 30 days. A missing image in one feed does not lower the score of another; scrolling repeatedly over the same article is not a new incident. Detailed image-attempt figures, when enabled, may be larger because they describe network work rather than distinct affected articles.
