Flutter

Testing & Troubleshooting

Test Flutter 1.x notifications without waiting for the normal account delay.

Test mode

Use an internal build with the SDK initialized, enabled and permitted to notify:

await Stay22.testing.setShowLogs(true);
await Stay22.testing.setForce(true);
await Stay22.clearTravelContext();
await Stay22.setTravelContext(TravelContext(address: 'Paris, France'));

Background the app. Force mode requests a short delay and bypasses local relevance and cooldown gates. The operating system can still delay display. Tap the notification and verify that the booking experience opens with your partner attribution.

Never ship force mode or diagnostic logging enabled. Restore normal behavior with await Stay22.testing.setForce(false) and await Stay22.testing.setShowLogs(false), or use a build that excludes those calls.

Diagnose the integration

In the 1.6.0 package:

final report = await Stay22.diagnostics.logReport();
for (final check in report.failures) {
  print('${check.name}: ${check.detail}');
}

This reports integration state without scheduling a test notification. Listen to events for reasons normal scheduling is held back.

SymptomCheck
not_initializedDeclare the partner ID natively, or await runtime initialization before calling the SDK.
Android cannot resolve com.stay22:sdkDeclare Stay22's Maven repository in the host app.
Nothing schedulesCheck the enabled state, notification permission, destination and whether account settings loaded.
app_foregroundBackground the app for normal automatic scheduling.
home_destinationUse a destination away from the IP-derived home city while testing normal behavior.
Guest counts do not changeClear the context and resend the complete trip.
An iOS cold-start tap opens nothingUse native partner-ID declaration and check notification-delegate forwarding.

Verify attribution before shipping

Use the partner ID Stay22 issued you. Flutter 1.6.0 wraps native 1.6.0 and does not include the newer unknown-partner-ID warning. An absent warning does not establish that bookings will be credited correctly. Check the ID with Stay22 if uncertain.

If a valid ID containing capital letters produces partner_config_aid_mismatch, this package predates the native fix in 1.6.5; contact support@stay22.com for the appropriate upgrade.

Send reproducible steps, package/native versions, your aid, and internal-build logs to support. Do not treat a successful scheduling call as proof that the operating system displayed the notification.

On this page