iOS

Testing & Troubleshooting

Test and diagnose a iOS 3.x integration.

Test mode

Use an internal build after initialization, consent and notification permission:

Stay22.testing.showLogs = true
Stay22.testing.scheduleNotification(TravelContext(address: "Paris, France"))

The diagnostic request uses a five-second not-before time and sixty-second execution and action cutoffs. The OS can show it later, including while the app is open. It does not reset the normal cooldown, and it can refuse while a normal notification is in progress or its outcome is uncertain. Read await Stay22.notifications.current() on the main actor before retrying after a lost response. It uses the diagnostic notification category, so an extension registered only for the normal category does not run.

Keep force mode, test notification calls and verbose logging out of public builds.

Why did no notification appear?

  1. Confirm initialization ran with your real partner ID and the SDK is enabled.
  2. Check the OS notification permission and delegate forwarding.
  3. Register the event handler and inspect the reason. Check receipt.reason and receipt.execution?.reason on notificationChanged.
  4. Check the deadlines and timing restrictions; a submitted request is not proof that the OS has queued it.
  5. Run await Stay22.diagnostics.logReport() for an integration report.

Check your partner ID before shipping

An unknown partner ID raises partner_config_unknown_aid and makes the aid diagnostics check fail after settings load. Notifications may still run, but that does not establish booking credit. Correct the ID passed to initialization. A diagnostics run before account settings load cannot verify the ID.

Still stuck?

Reproduce the issue with logging enabled and send the logs, platform, installed SDK version and partner ID to support@stay22.com. Review logs for personal trip information before sharing them. Include whether the test notification appeared and what happened when tapped.

On this page