FolioIntent help
Support
Start with the checks below. If the problem remains, tell us what happened without sending the document itself.
Camera will not capture
- Open iOS Settings, find FolioIntent, and confirm Camera access is enabled.
- Close another app that may be using the camera, reopen FolioIntent, and choose Capture again.
- If FolioIntent says no usable camera is available, use Import and select a PDF or image.
- If recovered pages appear, finish or discard that session before starting another camera request.
A destination is pending or ambiguous
- Check the destination itself before retrying; an interrupted response does not prove the upload failed.
- Confirm the server URL, TLS certificate, account permissions, bucket or folder, and available space.
- Use Retry action only when Runs says Ready to retry. FolioIntent does not automatically resubmit that state on relaunch.
- For Accepted, Verifying, or Ambiguous, use Check Provider; it observes the existing action and cannot submit a new one.
- If authentication is required, reconnect the same destination and use Credentials are updated. That only prepares the action; Retry action or Check Provider is a separate tap.
A Shortcut stopped
Open FolioIntent once, unlock it if app lock is enabled, and inspect the result in Runs. Confirm that the result files have not passed their lease date and that the selected Workflow and destination still exist. Force-quitting stops in-progress work and does not ask iOS to relaunch the app automatically.
A completion notification did not appear
- Confirm the Workflow's completion-notification switch is enabled.
- Open iOS Settings, find FolioIntent, and allow Notifications.
- Inspect Runs. FolioIntent waits while a required action is unresolved, and denied permission must not be reported as a scheduled alert.
- Accepted for scheduling means the device accepted the request. It does not prove that iOS displayed the alert or that anyone read it.
- Notification text is intentionally generic so document details do not appear on the Lock Screen.
FolioIntent closed unexpectedly
- Reopen FolioIntent and inspect Runs before repeating the capture or destination action.
- If a camera session offers recovered pages, review or discard them explicitly instead of starting the same capture again.
- Keep the app installed and preserve its local data while an uncertain action is being investigated. A simulator or diagnostic filename may still use a legacy internal process name; the customer-facing product is FolioIntent.
Files, purchases, updates, and expired results
- If a result lease expired, run the Workflow again from the preserved source; move important outputs to durable storage before they expire.
- If a selected Files folder is unavailable, reconnect it through the system picker and verify the provider is online before retrying.
- For a missing purchase, use Restore Purchases while signed into the Apple Account that made it; local free processing and recovery remain available.
- After an update, keep the old installation and local data intact until FolioIntent opens and the migrated library is visible.
Contact
Email [email protected]. Include the FolioIntent version, iOS version, entry point used (camera, import, share, or Shortcut), destination type, and exact error text.
Protect your data. Never email documents, scans, passwords, tokens, access keys, private server URLs, or diagnostic exports containing them. We will ask for a sanitized example if one is needed.